update mpc core kit swift docs

Author: AyushBherwani1998

.gitignore

@@ -22,3 +22,4 @@ yarn-error.log*
 .integrationBuilderCache
 
 yarn.lock
+.idea

.vscode/settings.json

@@ -17,7 +17,6 @@
     "Metamask's",
     "metastring",
     "nodir",
-    "openlogin",
     "palenight",
     "passwordless",
     "solana",
@@ -55,10 +54,10 @@
     "editor.defaultFormatter": "DotJoshJohnson.xml"
   },
   "[javascript]": {
-    "editor.defaultFormatter": "vscode.typescript-language-features"
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
   },
   "[typescriptreact]": {
-    "editor.defaultFormatter": "vscode.typescript-language-features"
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
   },
   "[typescript]": {
     "editor.defaultFormatter": "esbenp.prettier-vscode"

docs/README.mdx

@@ -3,7 +3,7 @@ title: Introduction
 slug: /
 hide_table_of_contents: true
 hide_title: true
-displayed_sidebar: docs
+
 image: "images/docs-meta-cards/documentation-card.png"
 description: "Introduction | Documentation - Web3Auth"
 ---
@@ -19,24 +19,14 @@ import SEO from "@site/src/components/SEO";
 
 # Web3Auth Documentation
 
-#### Simplifying User Onboarding with Scalable, Secure, Non-Custodial Wallet Management
-
-<HomeQuickStartBanner />
-
-# Discover Our Solutions
-
-Our extensive product suite covers everything from pre-onboarding to post-onboarding and authentication, enabling you to craft a seamless end-to-end
-experience for your Web3 dApp.
+#### Effortless Social Logins, Beautiful UX, and Secure Onboarding for Web3
 
 <ProductCards />
 
-# Resources
+## Resources
 
-Our comprehensive array of guides, reference materials, and examples is designed to assist you at every step of your Web3Auth integration. Explore the
-nuances of web3 authentication and craft a tailored integration that meets your specific needs.
+Our comprehensive array of guides, reference materials, and examples is designed to assist you at
+every step of your Web3Auth integration. Explore the nuances of web3 authentication and craft a
+tailored integration that meets your specific needs.
 
 <ResourcesCards />
-
-# Need Help?
-
-<HelpCards />

docs/auth-provider-setup/aggregate-verifier.mdx

@@ -1,67 +1,178 @@
 ---
-title: Creating Aggregate Verifier on the Web3Auth Dashboard
-sidebar_label: Aggregate Verifier
-displayed_sidebar: resources
-description: "Creating Aggregate Verifier on the Web3Auth Dashboard | Documentation - Web3Auth"
+title: Creating Aggregate Verifier on Web3Auth Dashboard
+sidebar_label: Aggregate Multiple Logins
+description:
+  "Creating Aggregate Verifier on the Web3Auth Dashboard | Auth Provider Setup | Documentation -
+  Web3Auth"
 image: "images/docs-meta-cards/documentation-card.png"
 ---
 
-Developers can create `Aggregate Multiple Provider` from the Web3Auth Dashboard by combining multiple login methods to create a verifier to get the
-same address for their user regardless of their login providers. For example, combining a `Google` and `Email Passwordless` login or `Google` and
-`GitHub` via Auth0 to access the same address for your user. These login methods should share the same Verifier ID, e.g., `email`; Such verifiers are
-called `Single ID Verifiers`.
+import CreateVerifierFirstStep from "@site/src/common/docs/_create-verifier-first-step.mdx";
 
-### Set up an Aggregate Verifier
+Developers can create an `Aggregate Multiple Provider` verifier from the Web3Auth Dashboard by
+combining multiple login methods. This enables them to create a verifier that retrieves the same
+address for their user, regardless of the login providers used. For example, developers can combine
+a `Google` and `Email Passwordless` login, or a `Google` and `GitHub` login via Auth0, to access the
+same address for their user.
 
-1. Create an aggregate verifier for your application by selecting `Aggregate Multiple Providers` as the Login provider from the login providers.
+:::note
+
+Access to creating a verifier is gated. Therefore, creating an aggregate verifier
+[**requires a minimum Growth Plan**](https://web3auth.io/pricing.html).
+
+You can utilize this feature for projects on `sapphire_devnet` network for free.
+
+:::
+
+## Understanding Login Combinations
+
+Before setting up an aggregate verifier, it's important to understand which login methods can be
+combined. The following table shows all possible combinations of login providers.
+
+:::tip Understanding the Table
+
+- **Rows**: First sub-verifier chosen during aggregate verifier creation
+- **Columns**: Available options for the second sub-verifier
+- ✅ = Supported combination
+- ❌ = Unsupported combination
+
+:::
+
+| First Sub-Verifier | Google | Facebook | Twitch | Discord | Auth0 | Email Passwordless | SMS Passwordless |
+| :----------------- | :----: | :------: | :----: | :-----: | :---: | :----------------: | :--------------: |
+| **Google**         |   ✅   |    ❌    |   ❌   |   ❌    |  ✅   |         ✅         |        ❌        |
+| **Facebook**       |   ❌   |    ❌    |   ❌   |   ❌    |  ✅   |         ❌         |        ❌        |
+| **Twitch**         |   ❌   |    ❌    |   ✅   |   ❌    |  ❌   |         ❌         |        ❌        |
+| **Discord**        |   ❌   |    ❌    |   ❌   |   ✅    |  ❌   |         ❌         |        ❌        |
+| **Email P'less**   |   ✅   |    ❌    |   ❌   |   ❌    |  ✅   |         ✅         |        ❌        |
+| **SMS P'less**     |   ❌   |    ❌    |   ❌   |   ❌    |  ✅   |         ❌         |        ✅        |
+| **Auth0**          |   ✅   |    ✅    |   ❌   |   ❌    |  ✅   |         ✅         |        ✅        |
+
+:::info Important
+
+Some login methods (like Twitch and Discord) cannot be combined with others because they lack a
+**common identifier**, such as an email. This identifier is crucial for connecting user accounts
+across different authentication methods and ensuring reliable user recognition when switching
+between login methods.
+
+:::
+
+### Auth0 Special Capabilities
+
+When using Auth0 as a verifier, you have access to a wide range of authentication methods. After
+selecting Auth0, you can choose from the following **Authentication Types**:
+
+<div className="auth0-options-grid">
+<div>
+
+#### Social Logins
+
+- Google
+- Twitter
+- Reddit
+- Apple
+- GitHub
+- LinkedIn
+
+</div>
+<div>
+
+#### Regional Options
+
+- WeChat
+- Weibo
+- Kakao
+- Line
+
+</div>
+<div>
+
+#### Other Methods
+
+- Email Passwordless
+- Email Password
+- Custom Authentication
+- Additional Options
+
+</div>
+</div>
+
+## Setting up an Aggregate Verifier
+
+<CreateVerifierFirstStep />
+
+1. Give a unique name to your verifier in the `Verifier Identifier` field. e.g.,
+   `web3auth-aggregate-verifier`.
+
+1. Select `Aggregate Multiple Providers` as the Login provider.
    ![Login Providers list on Web3Auth Dashboard](/images/dashboard/create-verifier-aggregate.png)
-2. Click on `Add Sub Verifiers` to add a new sub-verifier.
+
+1. Click on `Add Sub Verifiers` to add a new sub-verifier.
    ![Add first sub-verifier on Web3Auth Dashboard](/images/dashboard/create-verifier-aggregate-add-sub.png)
-3. Select any social login provider from the list to start with. Here we're selecting `Google`. Paste the **Client ID** from the Google App to the
-   `Client ID` field and click on `Add Sub Verifiers`.
+
+1. Select any social login provider from the list to start with. Here we're selecting `Google`.
+
+   Paste the **Client ID** from the Google App to the `Client ID` field and click on
+   `Add Sub Verifiers`.
    ![Select Google from Login Providers list on Web3Auth Dashboard](/images/dashboard/create-verifier-aggregate-google.png)
-4. Next, create the second sub-verifier. Click on `Add Sub Verifiers` to add a new sub-verifier.
-5. Select `Auth0` on the dropdown or choose `Custom Providers` from the radio buttons. We're selecting `Auth0` in this example.
+
+1. Next, create the second sub-verifier by clicking on the `Add Sub Verifiers` button.
+
+1. This time, you can select Social Login Providers like `Auth0` or `Google`, or `Custom Providers`
+   from the dropdown list. We're selecting `Auth0` in this example.
    ![Auth0 as sub verifier on Web3Auth Dashboard](/images/dashboard/create-verifier-aggregate-add-second-sub.png)
-6. Select the `Authentication Type` based on your application need on the dropdown. We're selecting `GitHub` in this example.
+
+   :::note You can combine two or more Google logins as needed for web and mobile apps. :::
+
+1. Select the `Authentication Type` based on your application need from the dropdown. We're
+   selecting `GitHub` in this example.
    ![Create Aggregate Verifiier on Web3Auth Dashboard](/images/dashboard/create-verifier-aggregate-auth0-github.png)
-7. Select `Email` as the **JWT Verifier ID** and enter the `Auth0 Client ID` and `Auth0 Domain` from your Auth0 application. See how to create a new
-   Auth0 application [here](https://auth0.com/docs/quickstart/webapp/).
 
+1. Next, select `Email` as the **JWT Verifier ID** and enter the `Auth0 Client ID` and
+   `Auth0 Domain` from your Auth0 application. See how to create a new Auth0 application
+   [here](https://auth0.com/docs/quickstart/webapp/).
    ![Create GitHub Sub Verifiier on Web3Auth Dashboard](/images/dashboard/create-verifier-aggregate-auth0-github-filled.png)
    ![Domain and Client ID from Auth0 Dashboard](/dashboard/verifiers/aggregate-verifier/av-a0-github.png)
 
    :::info NOTE
 
-   1. Add the [GitHub Social Connection](https://marketplace.auth0.com/integrations/github-social-connection) to your Auth0 application.
-   2. One has to request an email from the user while setting up the GitHub Social Connection on the Auth0 Dashboard.
+   1. Add the
+      [GitHub Social Connection](https://marketplace.auth0.com/integrations/github-social-connection)
+      to your Auth0 application.
+   2. One has to request an email from the user while setting up the GitHub Social Connection on the
+      Auth0 Dashboard.
       ![Request Email address for GitHub Social connection](/dashboard/verifiers/aggregate-verifier/av-a0-github-email.png)
 
    :::
 
-8. Similarly, create a third sub-verifier for `Email Passwordless` via Auth0. Follow the above steps from 5 to 8, and select `Email Passwordless` in
-   place of `GitHub`.
-   ![Create Email Passwordless Sub Verifiier on Web3Auth Dashboard](/images/dashboard/create-verifier-aggregate-auth0-email-passwordless-filled.png)
-9. Finally, click on `Create` to deploy the verifier.
+1. Similarly, create a third sub-verifier for `Email Passwordless`. Click on `Social Login Provider`
+   and then select `Email Passwordless` as the Login provider from the dropdown list
+   ![Create Email Passwordless Sub Verifiier on Web3Auth Dashboard](/images/dashboard/create-verifier-aggregate-email-passwordless.png)
 
-:::note NOTE
+1. Finally, click on `Create` to deploy the verifier.
+
+   It typically takes 5-10 minutes for the verifier to go live. Once deployed & live, you'll receive
+   an email and the dashboard will display the 'Live' status for the verifier.
+
+:::note
 
 You can aggregate two or more verifiers.
 
 :::
 
-### Example
+## Implementation Example
 
 ```tsx
 import { Web3AuthNoModal } from "@web3auth/no-modal";
-import { OpenloginAdapter } from "@web3auth/openlogin-adapter";
+import { AuthAdapter } from "@web3auth/auth-adapter";
 import { EthereumPrivateKeyProvider } from "@web3auth/ethereum-provider";
+import { CHAIN_NAMESPACES } from "@web3auth/base";
 
-const clientId = "BPi5PB_UiIZ-cPz1GtV5i1I2iOSOHuimiXBI0e-Oe_u6X3oVAbCiAZOTEBtTXw4tsluTITPqA8zMsfxIKMjiqNQ";
-// get it from https://dashboard.web3auth.io by creating a Plug n Play project.
+const clientId =
+  "BPi5PB_UiIZ-cPz1GtV5i1I2iOSOHuimiXBI0e-Oe_u6X3oVAbCiAZOTEBtTXw4tsluTITPqA8zMsfxIKMjiqNQ"; // get it from https://dashboard.web3auth.io by creating a Plug n Play project.
 
 const chainConfig = {
-  chainNamespace: "eip155",
+  chainNamespace: CHAIN_NAMESPACES.EIP155,
   chainId: "0x1",
   rpcTarget: "https://rpc.ankr.com/eth",
   displayName: "Ethereum Mainnet",
@@ -79,58 +190,55 @@ const web3auth = new Web3AuthNoModal({
   privateKeyProvider: privateKeyProvider,
 });
 
-const openloginAdapter = new OpenloginAdapter({
+const authAdapter = new AuthAdapter({
   adapterSettings: {
     loginConfig: {
       // Google login
       google: {
-        verifier: "aggregate-sapphire", // Pass the Verifier name here. eg. w3a-agg-example
+        verifier: "aggregate-sapphire", // Pass the Verifier name here. eg. aggregate-sapphire
         verifierSubIdentifier: "w3a-google", // Pass the Sub-Verifier here. eg w3a-google
         typeOfLogin: "google", // Pass the type of login provider.
         clientId: "519228911939-cri01h55lsjbsia1k7ll6qpalrus75ps.apps.googleusercontent.com", // Pass the Google `Client ID` here.
       },
       // GitHub Login via Auth0
       github: {
-        verifier: "aggregate-sapphire", // Pass the Verifier name here. eg. w3a-agg-example
+        verifier: "aggregate-sapphire", // Pass the Verifier name here. eg. aggregate-sapphire
         verifierSubIdentifier: "w3a-a0-github", // Pass the Sub-Verifier here. eg w3a-a0-github
         typeOfLogin: "jwt", // Pass the type of login provider. For Auth0, it's jwt and not Auth0.
         clientId: "hiLqaop0amgzCC0AXo4w0rrG9abuJTdu", // Pass the Auth0 `Client ID` here.
       },
       // Email Password Login via Auth0
-      emailpasswordless: {
-        verifier: "aggregate-sapphire", // Pass the Verifier name here. eg. w3a-agg-example
-        verifierSubIdentifier: "w3a-a0-email-passwordless", // Pass the Sub-Verifier here. eg w3a-a0-email-passwordless
-        typeOfLogin: "jwt", // Pass the type of login provider. For Auth0, it's jwt and not Auth0.
-        clientId: "QiEf8qZ9IoasbZsbHvjKZku4LdnRC1Ct", // Pass the `Client ID` of your Auth0 Application.
+      email_passwordless: {
+        verifier: "aggregate-sapphire", // Pass the Verifier name here. eg. aggregate-sapphire
+        verifierSubIdentifier: "w3a-email-passwordless", // Pass the Sub-Verifier here. eg w3a-email-passwordless
+        typeOfLogin: "email_passwordless", // Pass the type of login provider.
+        clientId, // Pass the Web3Auth `Client ID` here.
       },
     },
   },
   privateKeyProvider,
 });
 
-web3auth.configureAdapter(openloginAdapter);
+web3auth.configureAdapter(authAdapter);
 
 // Initialize
 await web3auth.init();
 
 // When user clicks Google button, use this to Login with Google
-const web3authProvider = await web3auth.connectTo("openlogin", {
+const web3authProvider = await web3auth.connectTo("auth", {
   loginProvider: "google",
 });
 
 // When user clicks Email Passwordless button, use this to Login with Email Passwordless via Auth0
-const web3authProvider = await web3auth.connectTo("openlogin", {
-  loginProvider: "emailpasswordless",
+const web3authProvider = await web3auth.connectTo("auth", {
+  loginProvider: "email_passwordless",
   extraLoginOptions: {
-    domain: "https://web3auth.au.auth0.com", // Pass the Auth0 Domain here, eg. https://web3auth.au.auth0.com
-    // This corresponds to the field inside jwt which must be used to uniquely identify the user.
-    verifierIdField: "email", // This is mapped b/w google and github logins.
-    isVerifierIdCaseSensitive: false,
+    login_hint: email.trim(),
   },
 });
 
 // When user clicks GitHub button, use this to Login with GitHub via Auth0
-const web3authProvider = await web3auth.connectTo("openlogin", {
+const web3authProvider = await web3auth.connectTo("auth", {
   loginProvider: "github",
   extraLoginOptions: {
     domain: "https://web3auth.au.auth0.com", // Pass the Auth0 Domain here, eg. https://web3auth.au.auth0.com
@@ -147,3 +255,39 @@ Check out the
 [**full example on GitHub**](https://github.com/Web3Auth/web3auth-pnp-examples/tree/main/web-no-modal-sdk/custom-authentication/aggregate-verifier-examples/auth0-google-aggregate-no-modal-example).
 
 :::
+
+<style>
+  {`
+  .auth0-options-grid {
+    display: grid;
+    grid-template-columns: repeat(auto-fit, minmax(200px, 1fr));
+    gap: 20px;
+    margin: 20px 0;
+  }
+
+  table {
+    display: table;
+    width: 100%;
+    margin: 1em 0;
+    overflow-x: auto;
+  }
+
+  th {
+    background: var(--ifm-color-primary);
+    color: white;
+    font-weight: 600;
+    padding: 12px;
+    text-align: center;
+  }
+
+  td {
+    padding: 12px;
+    text-align: center;
+    border: 1px solid var(--ifm-color-gray-300);
+  }
+
+  tr:nth-child(even) {
+    background: var(--ifm-color-gray-100);
+  }
+`}
+</style>