Merge branch 'master' into add-guide-multiple-chains

Author: rtomas

docs/sdk/core-kit/sfa-react-native/initialize.mdx

@@ -2,7 +2,8 @@
 title: "Initializing Core Kit SFA React Native SDK"
 sidebar_label: "Initialize"
 displayed_sidebar: sdk
-description: "Web3Auth Core Kit Single Factor Auth React Native SDK - Initialize | Documentation - Web3Auth"
+description:
+  "Web3Auth Core Kit Single Factor Auth React Native SDK - Initialize | Documentation - Web3Auth"
 ---
 
 import ChainConfig from "@site/src/common/sdk/pnp/web/_chain-config.mdx";
@@ -11,7 +12,8 @@ import InstantiatingProvider from "@site/src/common/sdk/core-kit/sfa/_instantiat
 import TabItem from "@theme/TabItem";
 import Tabs from "@theme/Tabs";
 
-After Installation, the next step to use Web3Auth Single Factor Auth Web SDK is to Initialize the SDK.
+After Installation, the next step to use Web3Auth Single Factor Auth Web SDK is to Initialize the
+SDK.
 
 However, the Initialization is a two-step process, ie.
 
@@ -23,7 +25,7 @@ However, the Initialization is a two-step process, ie.
 #### Import the `Web3Auth` class from `@web3auth/single-factor-auth-react-native` package.
 
 ```js
-import { Web3Auth } from "@web3auth/single-factor-auth-react-native";
+import Web3Auth from "@web3auth/single-factor-auth-react-native";
 ```
 
 #### Assign the `Web3Auth` class to a variable
@@ -40,25 +42,27 @@ import { Web3Auth } from "@web3auth/single-factor-auth-react-native";
 
 ```javascript
 import * as SecureStore from "expo-secure-store";
-import { Web3Auth } from "@web3auth/single-factor-auth-react-native";
+import Web3Auth from "@web3auth/single-factor-auth-react-native";
 
 const web3auth = new Web3Auth(SecureStore, SdkInitOptions);
 ```
 
-The react native SFA Web3Auth constructor takes `SecureStore` and an object with `SdkInitOptions` as parameters for the expo-managed workflow.
+The react native SFA Web3Auth constructor takes `SecureStore` and an object with `SdkInitOptions` as
+parameters for the expo-managed workflow.
 
 </TabItem>
 
 <TabItem value="bare">
 
 ```javascript
 import EncryptedStorage from "react-native-encrypted-storage";
-import { Web3Auth } from "@web3auth/single-factor-auth-react-native";
+import Web3Auth from "@web3auth/single-factor-auth-react-native";
 
 const web3auth = new Web3Auth(EncryptedStorage, SdkInitOptions);
 ```
 
-The react native SFA Web3Auth constructor takes `EncryptedStorage` and an object with `SdkInitOptions` as parameters for the bare workflow.
+The react native SFA Web3Auth constructor takes `EncryptedStorage` and an object with
+`SdkInitOptions` as parameters for the bare workflow.
 
 </TabItem>
 </Tabs>
@@ -144,7 +148,7 @@ export interface SdkInitOptions {
 ```ts
 const web3auth = new Web3Auth(SecureStore, {
   clientId: "WEB3AUTH_CLIENT_ID", // Get your Client ID from the Web3Auth Dashboard
-  web3AuthNetwork: "sapphire_mainnet",
+  web3AuthNetwork: WEB3AUTH_NETWORK.SAPPHIRE_MAINNET,
   usePnPKey: false, // By default, this sdk returns CoreKitKey
 });
 ```
@@ -156,7 +160,7 @@ const web3auth = new Web3Auth(SecureStore, {
 ```ts
 const web3auth = new Web3Auth(EncryptedStorage, {
   clientId: "WEB3AUTH_CLIENT_ID", // Get your Client ID from the Web3Auth Dashboard
-  web3AuthNetwork: "sapphire_mainnet",
+  web3AuthNetwork: WEB3AUTH_NETWORK.SAPPHIRE_MAINNET,
   usePnPKey: false, // By default, this sdk returns CoreKitKey
 });
 ```
@@ -172,8 +176,9 @@ const web3auth = new Web3Auth(EncryptedStorage, {
 
 #### `init()`
 
-To complete the initialization process, we need to initialize the `Web3Auth` instance, which we named `web3auth`. This is achieved by calling the
-`init()` function of the previously created `web3auth` instance, using a **private key provider**.
+To complete the initialization process, we need to initialize the `Web3Auth` instance, which we
+named `web3auth`. This is achieved by calling the `init()` function of the previously created
+`web3auth` instance, using a **private key provider**.
 
 ```ts
 await web3auth.init(privateKeyProvider);
@@ -193,9 +198,9 @@ await web3auth.init(privateKeyProvider);
 
 ```ts
 import * as SecureStore from "expo-secure-store";
-import { Web3Auth } from "@web3auth/single-factor-auth-react-native";
+import Web3Auth from "@web3auth/single-factor-auth-react-native";
 import { EthereumPrivateKeyProvider } from "@web3auth/ethereum-provider";
-import { CHAIN_NAMESPACES } from "@web3auth/base";
+import { CHAIN_NAMESPACES, WEB3AUTH_NETWORK } from "@web3auth/base";
 
 // Swap with a different provider if you want to use a different blockchain
 const privateKeyProvider = new EthereumPrivateKeyProvider({
@@ -214,7 +219,7 @@ const privateKeyProvider = new EthereumPrivateKeyProvider({
 
 const web3auth = new Web3Auth(SecureStore, {
   clientId: "WEB3AUTH_CLIENT_ID", // Get your Client ID from the Web3Auth Dashboard
-  web3AuthNetwork: "sapphire_mainnet",
+  web3AuthNetwork: WEB3AUTH_NETWORK.SAPPHIRE_MAINNET,
   usePnPKey: false, // By default, this sdk returns CoreKitKey
 });
 
@@ -227,9 +232,9 @@ await web3auth.init(privateKeyProvider);
 
 ```ts
 import EncryptedStorage from "react-native-encrypted-storage";
-import { Web3Auth } from "@web3auth/single-factor-auth-react-native";
+import Web3Auth from "@web3auth/single-factor-auth-react-native";
 import { EthereumPrivateKeyProvider } from "@web3auth/ethereum-provider";
-import { CHAIN_NAMESPACES } from "@web3auth/base";
+import { CHAIN_NAMESPACES, WEB3AUTH_NETWORK } from "@web3auth/base";
 
 // Swap with a different provider if you want to use a different blockchain
 const privateKeyProvider = new EthereumPrivateKeyProvider({
@@ -248,7 +253,7 @@ const privateKeyProvider = new EthereumPrivateKeyProvider({
 
 const web3auth = new Web3Auth(EncryptedStorage, {
   clientId: "WEB3AUTH_CLIENT_ID", // Get your Client ID from the Web3Auth Dashboard
-  web3AuthNetwork: "sapphire_mainnet",
+  web3AuthNetwork: WEB3AUTH_NETWORK.SAPPHIRE_MAINNET,
   usePnPKey: false, // By default, this sdk returns CoreKitKey
 });
 

docs/sdk/core-kit/sfa-react-native/install.mdx

@@ -2,7 +2,8 @@
 title: "Installing Core Kit SFA React Native SDK"
 sidebar_label: "Install"
 displayed_sidebar: sdk
-description: "Web3Auth Core Kit Single Factor Auth React Native SDK - Install | Documentation - Web3Auth"
+description:
+  "Web3Auth Core Kit Single Factor Auth React Native SDK - Install | Documentation - Web3Auth"
 ---
 
 import TabItem from "@theme/TabItem";
@@ -15,22 +16,25 @@ In React Native, you have the choice to use one of the following workflows:
 
 ### Expo Managed Workflow
 
-Your Expo app is built on your Expo's cloud, so you don't have control over the native modules used in the app. Developers build managed workflow apps
-using `expo-cli` on their computers and a development client on their mobile devices. Managed workflow apps typically use one or more Expo services,
-such as push notifications, builds, and updates.
+Your Expo app is built on your Expo's cloud, so you don't have control over the native modules used
+in the app. Developers build managed workflow apps using `expo-cli` on their computers and a
+development client on their mobile devices. Managed workflow apps typically use one or more Expo
+services, such as push notifications, builds, and updates.
 
 <ExpoWarning />
 
 ### Bare React Native Workflow
 
-Your Bare React Native app is entirely built on your machine. In this workflow, the developer has complete control, along with the complexity that
-comes with that. Configuration with `app.json` / `app.config.js` is mostly not supported in this context; instead, you will need to configure each
-native project directly with Swift/Kotlin native modules. Check out the [troubleshooting section](/sdk/pnp/react-native/install#troubleshooting) for
-fixing common issues.
+Your Bare React Native app is entirely built on your machine. In this workflow, the developer has
+complete control, along with the complexity that comes with that. Configuration with `app.json` /
+`app.config.js` is mostly not supported in this context; instead, you will need to configure each
+native project directly with Swift/Kotlin native modules. Check out the
+[troubleshooting section](/sdk/pnp/react-native/install#troubleshooting) for fixing common issues.
 
 :::tip
 
-You can read more about different workflows in the [Expo documentation](https://docs.expo.dev/archive/managed-vs-bare/).
+You can read more about different workflows in the
+[Expo documentation](https://docs.expo.dev/archive/managed-vs-bare/).
 
 :::
 
@@ -44,8 +48,8 @@ npm install --save @web3auth/single-factor-auth-react-native
 
 ### Adding a `Storage` Module
 
-Now with v4, we need to pass a `Storage` parameter to the SDK, which will be used for session management without storing the private keys of the user
-in the device.
+Now with v4, we need to pass a `Storage` parameter to the SDK, which will be used for session
+management without storing the private keys of the user in the device.
 
 <Tabs
   defaultValue="bare"
@@ -59,11 +63,11 @@ in the device.
 
 #### Expo Secure Store
 
-When using our SDK with an Expo-based React Native app (aka managed workflow), you have to install the `expo-secure-store` package as a `Storage`
-implementation.
+When using our SDK with an Expo-based React Native app (aka managed workflow), you have to install
+the `expo-secure-store` package as a `Storage` implementation.
 
 ```shell
-expo install expo-secure-store
+npx expo install expo-secure-store
 ```
 
 </TabItem>
@@ -72,7 +76,8 @@ expo install expo-secure-store
 
 #### React Native Encrypted Storage
 
-When using our SDK with a bare workflow React Native app, you have to install a `Storage` implementation provided by react-native.
+When using our SDK with a bare workflow React Native app, you have to install a `Storage`
+implementation provided by react-native.
 
 ```bash npm2yarn
 npm install --save react-native-encrypted-storage
@@ -83,14 +88,15 @@ npm install --save react-native-encrypted-storage
 
 ## Configuration
 
-After you have installed the files needed for your workflow, you'll have to configure the SDK with some additional steps to be able to use the SDK
-properly.
+After you have installed the files needed for your workflow, you'll have to configure the SDK with
+some additional steps to be able to use the SDK properly.
 
 ### Expo Managed Workflow
 
 - Adding URL scheme to `app.json`
 
-To allow the Expo-based SDK to work with exported Expo Android apps, you need to add the designated scheme into `app.json`
+To allow the Expo-based SDK to work with exported Expo Android apps, you need to add the designated
+scheme into `app.json`
 
 ```json title="app.json"
 {
@@ -102,13 +108,16 @@ To allow the Expo-based SDK to work with exported Expo Android apps, you need to
 
 :::tip
 
-You may refer to [these example apps](/examples?product=Core+Kit&sdk=Single+Factor+Auth+React+Native+SDK) and try it out yourself.
+You may refer to
+[these example apps](/examples?product=Core+Kit&sdk=Single+Factor+Auth+React+Native+SDK) and try it
+out yourself.
 
 :::
 
 ### Bare React Native Workflow
 
-For the bare workflow, you need to perform additional installation steps, alongside specific configurations for Android and iOS separately.
+For the bare workflow, you need to perform additional installation steps, alongside specific
+configurations for Android and iOS separately.
 
 #### Android
 
@@ -136,7 +145,8 @@ targetSdkVersion = 31
 </intent-filter>
 ```
 
-- SDK version 31 requires you to explicitly define `android:exported="true"` in `AndroidManifest.xml`, check whether it is correctly present or not.
+- SDK version 31 requires you to explicitly define `android:exported="true"` in
+  `AndroidManifest.xml`, check whether it is correctly present or not.
 
 ```xml title="android/app/src/main/AndroidManifest.xml"
 <activity
@@ -166,14 +176,18 @@ pod install
 
 :::tip
 
-You may refer to **[these example apps](/examples?product=Core+Kit&sdk=Single+Factor+Auth+React+Native+SDK)** and try it out yourself.
+You may refer to
+**[these example apps](/examples?product=Core+Kit&sdk=Single+Factor+Auth+React+Native+SDK)** and try
+it out yourself.
 
 :::
 
 ## Troubleshooting
 
 ### Bundler Issues: Missing Dependencies
 
-You might face issues mentioning that certain dependencies are missing within the React Native environment. These are node dependencies that need to
-be polyfilled in your application, to enable Web3Auth functionalities. Furthermore, your bundler needs to be reconfigured to use them while building
-the app. Please check out our **[React Native Troubleshooting Guide](/troubleshooting/metro-issues)**
+You might face issues mentioning that certain dependencies are missing within the React Native
+environment. These are node dependencies that need to be polyfilled in your application, to enable
+Web3Auth functionalities. Furthermore, your bundler needs to be reconfigured to use them while
+building the app. Please check out our
+**[React Native Troubleshooting Guide](/troubleshooting/metro-issues)**

docs/sdk/pnp/android/android.mdx

@@ -13,7 +13,7 @@ generated in a non-custodial way on successful user authentication. This authent
 achieved by using any social login options that Web3Auth supports or custom authentication flow of
 your choice.
 
-#### This Documentation is based on the `7.1.1` SDK Version.
+#### This Documentation is based on the `7.3.0` SDK Version.
 
 ## Requirements
 

docs/sdk/pnp/android/custom-authentication.mdx

@@ -7,37 +7,36 @@ description: "Web3Auth PnP Android SDK - Using Custom Authentication | Documenta
 
 import TabItem from "@theme/TabItem";
 import Tabs from "@theme/Tabs";
+import GrowthPlanNote from "@site/src/common/docs/_growth_plan_note.mdx";
 
-To use custom authentication (Using Social providers or Login providers like Auth0, AWS Cognito, Firebase etc. or even your own custom JWT login) you
-can add the configuration to the `loginConfig` parameter of the `Web3AuthOptions` object during the initialization.
+To use custom authentication (Using Social providers or Login providers like Auth0, AWS Cognito,
+Firebase etc. or even your own custom JWT login) you can add the configuration to the `loginConfig`
+parameter of the `Web3AuthOptions` object during the initialization.
 
-The `loginConfig` parameter is a key value map. The key should be one of the `Web3AuthProvider` in its string form, and the value should be a
-`LoginConfigItem` instance.
+The `loginConfig` parameter is a key value map. The key should be one of the `Web3AuthProvider` in
+its string form, and the value should be a `LoginConfigItem` instance.
 
 First, configure your own verifier in the Web3Auth Dashboard to use custom authentication.
 
-:::note
-
-This is a paid feature and the minimum [pricing plan](https://web3auth.io/pricing.html) to use this SDK in a production environment is the **Growth
-Plan**. You can use this feature in the development environment for free.
-
-:::
+<GrowthPlanNote />
 
 :::tip Create Custom Verifier
 
-Check out how to create a **[Custom Verifier](/auth-provider-setup/verifiers)** on the Web3Auth Dashboard.
+Check out how to create a **[Custom Verifier](/auth-provider-setup/verifiers)** on the Web3Auth
+Dashboard.
 
 :::
 
 :::info using dapp share
 
 - dApp Share is only returned for the Custom verifiers.
-- Also, 2FA should be enabled for the account using it. Use `mfaLevel = MFALevel.MANDATORY` in the `LoginParams` during login. See
-  **[MFA](/sdk/pnp/android/mfa)** for more details.
+- Also, 2FA should be enabled for the account using it. Use `mfaLevel = MFALevel.MANDATORY` in the
+  `LoginParams` during login. See **[MFA](/sdk/pnp/android/mfa)** for more details.
 
 :::
 
-Then, you should specify the details of your verifier in the `LoginConfigItem` struct, the details of this struct are as follows:
+Then, you should specify the details of your verifier in the `LoginConfigItem` struct, the details
+of this struct are as follows:
 
 ## `LoginConfigItem`
 
@@ -241,8 +240,9 @@ web3Auth = Web3Auth (
 
 ## `ExtraLoginOptions` for special login methods
 
-Additional to the `LoginConfig` you can pass extra options to the `login` function to configure the login flow for cases requiring additional info for
-enabling login. The `ExtraLoginOptions` accepts the following parameters:
+Additional to the `LoginConfig` you can pass extra options to the `login` function to configure the
+login flow for cases requiring additional info for enabling login. The `ExtraLoginOptions` accepts
+the following parameters:
 
 <Tabs
   defaultValue="table"
@@ -314,8 +314,9 @@ data class ExtraLoginOptions(
 
 ### Using Auth0 Login
 
-Auth0 has a special login flow, called the SPA flow. This flow requires a `client_id` and `domain` to be passed, and Web3Auth will get the JWT
-`id_token` from Auth0 directly. You can pass these configurations in the `ExtraLoginOptions` object in the login function.
+Auth0 has a special login flow, called the SPA flow. This flow requires a `client_id` and `domain`
+to be passed, and Web3Auth will get the JWT `id_token` from Auth0 directly. You can pass these
+configurations in the `ExtraLoginOptions` object in the login function.
 
 ```tsx
 web3Auth = Web3Auth (
@@ -348,9 +349,10 @@ val loginCompletableFuture: CompletableFuture<Web3AuthResponse> =
 
 ### Custom JWT Login
 
-If you're using any other provider like Firebase/ AWS Cognito or deploying your own Custom JWT server, you need to put the jwt token into the
-`id_token` field of the `extraLoginOptions`, additionally, you need to pass over the `domain` field as well, which is mandatory. If you don't have a
-domain, just passover a string in that field.
+If you're using any other provider like Firebase/ AWS Cognito or deploying your own Custom JWT
+server, you need to put the jwt token into the `id_token` field of the `extraLoginOptions`,
+additionally, you need to pass over the `domain` field as well, which is mandatory. If you don't
+have a domain, just passover a string in that field.
 
 ```tsx
 web3Auth = Web3Auth (
@@ -381,7 +383,8 @@ val loginCompletableFuture: CompletableFuture<Web3AuthResponse> =
 
 ### Email Passwordless
 
-To use the `EMAIL_PASSWORDLESS` login, you need to put the email into the `login_hint` field of the `extraLoginOptions`.
+To use the `EMAIL_PASSWORDLESS` login, you need to put the email into the `login_hint` field of the
+`extraLoginOptions`.
 
 ```kotlin
 val loginCompletableFuture: CompletableFuture<Web3AuthResponse> = web3Auth.login(