Merge branch 'master' into mpc-core-kit-swift

Author: shahbaz17

docs/auth-provider-setup/social-providers/twitter.mdx

@@ -11,24 +11,27 @@ import TabItem from "@theme/TabItem";
 
 :::note
 
-Twitter login can be performed in various ways, depending on the use case. We have demonstrated this with Auth0 & Firebase, but this can be done with
-any other Federated/JWT providers.
+Twitter login can be performed in various ways, depending on the use case. We have demonstrated this
+with Auth0 & Firebase, but this can be done with any other Federated/JWT providers.
 
 :::
 
 ## Set up [Twitter via Auth0](https://auth0.com/blog/how-to-add-a-twitter-social-connection-in-auth0/#Setup-Twitter-connection)
 
-1. Create an Auth0 verifier for your application by selecting `Auth0` as the Login provider from this modal.
+1. Create an Auth0 verifier for your application by selecting `Auth0` as the Login provider from
+   this modal.
    ![Twitter - Login Providers list on Web3Auth Dashboard](/images/dashboard/create-verifier-auth0.png)
 2. Select `Twitter` as the **Authentication Type** based on the dropdown.
    ![Twitter - Auth0 Authentication Type list on Web3Auth Dashboard](/images/dashboard/create-verifier-google.png)
-3. 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/).
+3. 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/).
 
    ![Twitter - Domain and Client ID from Auth0 Dashboard](/images/dashboard/create-verifier-auth0-filled-common.png)
    ![Twitter - Auth0 Client ID and Auth0 Domain on Web3Auth Dashboard](/images/dashboard/create-verifier-auth0-unfilled.png)
 
-4. Add the [Twitter Social Connection](https://marketplace.auth0.com/integrations/twitter-social-connection) to your Auth0 application.
+4. Add the
+   [Twitter Social Connection](https://marketplace.auth0.com/integrations/twitter-social-connection)
+   to your Auth0 application.
 5. Click on the `Create` button to create `Twitter` Custom Authentication via Auth0 verifier.
 
 ### Example
@@ -38,7 +41,8 @@ import { Web3AuthNoModal } from "@web3auth/no-modal";
 import { OpenloginAdapter } from "@web3auth/openlogin-adapter";
 import { EthereumPrivateKeyProvider } from "@web3auth/ethereum-provider";
 
-const clientId = "BPi5PB_UiIZ-cPz1GtV5i1I2iOSOHuimiXBI0e-Oe_u6X3oVAbCiAZOTEBtTXw4tsluTITPqA8zMsfxIKMjiqNQ";
+const clientId =
+  "BPi5PB_UiIZ-cPz1GtV5i1I2iOSOHuimiXBI0e-Oe_u6X3oVAbCiAZOTEBtTXw4tsluTITPqA8zMsfxIKMjiqNQ";
 // get it from https://dashboard.web3auth.io by creating a project.
 
 const chainConfig = {
@@ -214,7 +218,8 @@ import { ADAPTER_EVENTS, CHAIN_NAMESPACES, IProvider } from "@web3auth/base";
 import { EthereumPrivateKeyProvider } from "@web3auth/ethereum-provider";
 import { TwitterAuthProvider, getAuth, signInWithPopup, UserCredential } from "firebase/auth";
 
-const clientId = "BPi5PB_UiIZ-cPz1GtV5i1I2iOSOHuimiXBI0e-Oe_u6X3oVAbCiAZOTEBtTXw4tsluTITPqA8zMsfxIKMjiqNQ"; // get from https://dashboard.web3auth.io
+const clientId =
+  "BPi5PB_UiIZ-cPz1GtV5i1I2iOSOHuimiXBI0e-Oe_u6X3oVAbCiAZOTEBtTXw4tsluTITPqA8zMsfxIKMjiqNQ"; // get from https://dashboard.web3auth.io
 
 const verifier = "w3a-firebase-demo";
 
@@ -223,7 +228,7 @@ const chainConfig = {
   chainId: "0x1", // Please use 0x1 for Mainnet
   rpcTarget: "https://rpc.ankr.com/eth",
   displayName: "Ethereum Mainnet",
-  blockExplorer: "https://etherscan.io/",
+  blockExplorerUrl: "https://etherscan.io/",
   ticker: "ETH",
   tickerName: "Ethereum",
 };
@@ -283,7 +288,8 @@ import { EthereumPrivateKeyProvider } from "@web3auth/ethereum-provider";
 import { IProvider } from "@web3auth/base";
 import { TwitterAuthProvider, getAuth, signInWithPopup, UserCredential } from "firebase/auth";
 
-const clientId = "BPi5PB_UiIZ-cPz1GtV5i1I2iOSOHuimiXBI0e-Oe_u6X3oVAbCiAZOTEBtTXw4tsluTITPqA8zMsfxIKMjiqNQ"; // get from https://dashboard.web3auth.io
+const clientId =
+  "BPi5PB_UiIZ-cPz1GtV5i1I2iOSOHuimiXBI0e-Oe_u6X3oVAbCiAZOTEBtTXw4tsluTITPqA8zMsfxIKMjiqNQ"; // get from https://dashboard.web3auth.io
 
 const verifier = "w3a-firebase-demo";
 

docs/connect-blockchain/connect-blockchain.mdx

@@ -9,40 +9,46 @@ image: "images/docs-meta-cards/documentation-card.png"
 import EVMChains from "@site/src/common/docs/_evm-chains.mdx";
 import OtherChains from "@site/src/common/docs/_other-chains.mdx";
 
-Web3Auth is the frontend authentication system for your dApp. Once the user is authenticated, the Web3Auth SDK returns a provider. A provider is how
-libraries like web3.js & ethers.js talk to the blockchain. Providers take JSON-RPC requests and return the response. This is normally done by
-submitting the request to an HTTP or IPC socket-based server. With Web3Auth, you get two types of providers, depending on the product you use:
+Web3Auth is the frontend authentication system for your dApp. Once the user is authenticated, the
+Web3Auth SDK returns a provider. A provider is how libraries like web3.js & ethers.js talk to the
+blockchain. Providers take JSON-RPC requests and return the response. This is normally done by
+submitting the request to an HTTP or IPC socket-based server. With Web3Auth, you get two types of
+providers, depending on the product you use:
 
 1. [Shamir Secret Sharing based Private Key Providers](#private-key-providers-non-mpc)
 2. [Threshold Signature Scheme based MPC Providers](#mpc-providers)
 
 ## Web3Auth is Chain Agnostic
 
-By default, Web3Auth supports the `secp256k1` and `ed25519` key curves. While these key curves serve the majority of blockchains out there, certain
-blockchains have different curve implementations of their own. While for our MPC products, you need dedicated providers to interact with certain
+By default, Web3Auth supports the `secp256k1` and `ed25519` key curves. While these key curves serve
+the majority of blockchains out there, certain blockchains have different curve implementations of
+their own. While for our MPC products, you need dedicated providers to interact with certain
 blockchains, with **Web3Auth non-MPC products you can interact with any blockchain of your choice**.
 
-In Web3Auth non-MPC Products, the ability to export the user's private key comes in handy. This private key can be utilized by the dApp to interact
-with the chain.
+In Web3Auth non-MPC Products, the ability to export the user's private key comes in handy. This
+private key can be utilized by the dApp to interact with the chain.
 
 You can read more about this in our [Connect with Other Blockchains](./other/) section.
 
 :::info
 
-Web3Auth is composable - you can combine it with meta-transaction flows, multisigs, and other cryptographic protocols. It is easy to build on top of,
-and generally fits in with most other technology stacks, including but not limited to; your favorite scalability solutions, meta transactions, smart
-contract wallets, different elliptic curve pairs and even RSA.
+Web3Auth is composable - you can combine it with meta-transaction flows, multisigs, and other
+cryptographic protocols. It is easy to build on top of, and generally fits in with most other
+technology stacks, including but not limited to; your favorite scalability solutions, meta
+transactions, smart contract wallets, different elliptic curve pairs and even RSA.
 
 :::
 
 ## Private Key Providers (non-MPC)
 
-The Private Key Providers work with the majority of Web3Auth products, including Plug and Play SDKs, Single Factor Auth SDKs, and tKey SSS (v1) SDKs.
-As the name suggests these providers are a wrapper around the user's private key, which is dynamically reconstructed with Shamir's Secret Sharing and
+The Private Key Providers work with the majority of Web3Auth products, including Plug and Play SDKs,
+Single Factor Auth SDKs, and tKey SSS (v1) SDKs. As the name suggests these providers are a wrapper
+around the user's private key, which is dynamically reconstructed with Shamir's Secret Sharing and
 is present in the user's frontend.
 
-Once the authentication happens, the returned result from the Web3Auth network is taken up by the provider to give a common interface to interact with
-the blockchain of your choice. Currently, Web3Auth supports the following private key providers for Web SDKs:
+Once the authentication happens, the returned result from the Web3Auth network is taken up by the
+provider to give a common interface to interact with the blockchain of your choice. Currently,
+Web3Auth supports the following private key providers for Web SDKs:
 
 - [EIP1193 Private Key Provider](/sdk/providers/evm): For connecting to EVM based chains
 - [Solana Private Key Provider](/sdk/providers/solana): For connecting with Solana Blockchain
@@ -51,18 +57,19 @@ the blockchain of your choice. Currently, Web3Auth supports the following privat
 
 ## MPC Providers
 
-The Threshold Signature Scheme-based MPC Providers work with our MPC Core Kit SDK. These providers generate a signature of the particular key curve
-the provider is configured for and accordingly gives you the interface to initialize with the blockchain it is configured for. Currently, Web3Auth MPC
-Core Kit supports the following providers:
+The Threshold Signature Scheme-based MPC Providers work with our MPC Core Kit SDK. These providers
+generate a signature of the particular key curve the provider is configured for and accordingly
+gives you the interface to initialize with the blockchain it is configured for. Currently, Web3Auth
+MPC Core Kit supports the following providers:
 
 - EIP1193 MPC Provider: For connecting with EVM-based chains [Available by default within the SDK]
 - Bitcoin MPC Provider (coming soon)
 - Solana MPC Provider (coming soon)
 
 ## Reference Guides for Blockchain Connections
 
-You can check out the following guides we've written for certain blockchains. We have covered a wide variety of EVM and EVM Chains, supported by
-multiple web3auth providers.
+You can check out the following guides we've written for certain blockchains. We have covered a wide
+variety of EVM and EVM Chains, supported by multiple web3auth providers.
 
 ### EVM Chain Guides
 
@@ -73,28 +80,67 @@ multiple web3auth providers.
 
 ## Adding JSON RPC APIs
 
-Web3Auth providers give you a standard way of interacting with the blockchain. However, alongside that, it is recommended to use JSON RPC APIs, which
-help you connect to the blockchain without the need to run your own instance/ nodes. There are many services which offer a web API for accessing
+Web3Auth providers give you a standard way of interacting with the blockchain. However, alongside
+that, it is recommended to use JSON RPC APIs, which help you connect to the blockchain without the
+need to run your own instance/ nodes. There are many services which offer a web API for accessing
 different blockchains:
 
 #### Infura
 
-[Infura](https://infura.io) is the leading platform for Ethereum infrastructure. It provides a gateway to the Ethereum network, allowing developers to
-build and scale decentralized applications without having to run their own infrastructure. Most of the Web3Auth backend infrastructure runs on Infura
-APIs.
+[Infura](https://infura.io) is the leading platform for Ethereum infrastructure. It provides a
+gateway to the Ethereum network, allowing developers to build and scale decentralized applications
+without having to run their own infrastructure. Most of the Web3Auth backend infrastructure runs on
+Infura APIs.
 
 #### Quicknode
 
-[Quicknode](https://www.quicknode.com/) is a managed blockchain node service that provides high-performance access to 15+ blockchains, including
-Ethereum, Gnosis (xDAI), Polygon, Binance Smart Chain, Avalanche, Fantom, Solana, Optimism, Arbitrum (+Nova), Algorand, Harmony, Celo, Terra and
-Bitcoin networks. They're the biggest node providers for the Solana Ecosystem, and our major partners for Solana infrastructure.
+[Quicknode](https://www.quicknode.com/) is a managed blockchain node service that provides
+high-performance access to 15+ blockchains, including Ethereum, Gnosis (xDAI), Polygon, Binance
+
+Smart Chain, Avalanche, Fantom, Solana, Optimism, Arbitrum (+Nova), Algorand, Harmony, Celo, Neon,
+Terra and Bitcoin networks. They're the biggest node providers for the Solana Ecosystem, and our
+major partners for Solana infrastructure.
 
 #### Alchemy
 
-As a developer platform, [Alchemy](https://www.alchemy.com/) provides a suite of developer toolings and abstractions including JSON RPC APIs across
-all major chains, an ethers.js SDK, and a library of [enhanced APIs](https://docs.alchemy.com/reference/enhanced-apis-overview) like their NFT APIs.
+As a developer platform, [Alchemy](https://www.alchemy.com/) provides a suite of developer toolings
+and abstractions including JSON RPC APIs across all major chains, an ethers.js SDK, and a library of
+[enhanced APIs](https://docs.alchemy.com/reference/enhanced-apis-overview) like their NFT APIs.
 
 #### Ankr
 
-[Ankr](https://www.ankr.com/) is a decentralized cloud computing platform that provides a full suite of infrastructure services for blockchain
-developers. Most of the examples in our documentation use Ankr's Public JSON RPC APIs, to help you kickstart.
+[Ankr](https://www.ankr.com/) is a decentralized cloud computing platform that provides a full suite
+of infrastructure services for blockchain developers. Most of the examples in our documentation use
+Ankr's Public JSON RPC APIs, to help you kickstart.
+
+## Faucets for Different Blockchains
+
+Faucets are services that provide users with a small amount of cryptocurrency for free. These are
+often used for testing purposes or to onboard new users to a blockchain network. Here are some
+popular faucet services for different test blockchains:
+
+- Amoy Polygon faucet
+  - https://faucet.polygon.technology/
+  - https://www.alchemy.com/faucets/polygon-amoy
+  - https://faucet.quicknode.com/polygon/amoy
+- Avalanche
+  - https://faucet.avax.network/
+- Base Sepolia Faucet
+  - https://www.alchemy.com/faucets/base-sepolia
+- Binance Smart Chain Faucet
+  - https://www.bnbchain.org/en/testnet-faucet
+- Cosmos
+  - https://stakely.io/en/faucet/cosmos-atom
+- Optimism
+  - https://app.optimism.io/faucet
+- Polkadot Rococo / Westend / Paseo
+  - https://faucet.polkadot.io/
+- Sepolia Ethereum Faucet
+  - https://www.infura.io/faucet/sepolia
+  - https://www.alchemy.com/faucets/ethereum-sepolia
+  - (Sepolia PoW Faucet)[https://sepolia-faucet.pk910.de/]
+  - https://faucet.quicknode.com/ethereum/sepolia
+  - https://faucets.chain.link/
+- Solana
+  - https://faucet.solana.com/
+

docs/connect-blockchain/evm/ethereum/web.mdx

@@ -4,7 +4,8 @@ sidebar_label: Web
 image: "guides/banners/ethereum.png"
 displayed_sidebar: resources
 keywords: [ethereum, web3auth, authentication, blockchain]
-description: "Integrate Web3Auth with the Ethereum Blockchain in JavaScript | Documentation - Web3Auth"
+description:
+  "Integrate Web3Auth with the Ethereum Blockchain in JavaScript | Documentation - Web3Auth"
 ---
 
 import InstallationSnippet from "@site/src/common/docs/web-connect-blockchain/_evm-installation.mdx";
@@ -33,11 +34,14 @@ import SEO from "@site/src/components/SEO";
   slug="/connect-blockchain/evm/ethereum/web"
 />
 
-While using the Web3Auth Web SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the
-[Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like
-[`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make
-[Ethereum](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`,
-`read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Web SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193)
+provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html).
+This provider can be used with libraries like
+[`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html),
+[`ethers.js`](https://docs.ethers.io/v5/getting-started/), [`viem`](https://viem.sh/) etc. to make
+[Ethereum](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching
+`balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract,
+etc. We have highlighted a few here to get you started quickly on that.
 
 ## Installation
 
@@ -47,8 +51,9 @@ To interact with the Ethereum blockchain, you can use either library with Web3Au
 
 ## Initializing Provider
 
-Using `eip155` as `chainNamespace` while initializing `web3auth` will provide an [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) compatible
-provider as **`web3auth.provider`** after successful authentication.
+Using `eip155` as `chainNamespace` while initializing `web3auth` will provide an
+[`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) compatible provider as **`web3auth.provider`**
+after successful authentication.
 
 ### Getting the `chainConfig`
 

docs/connect-blockchain/evm/neon/android.mdx

@@ -0,0 +1,98 @@
+---
+title: Integrate Web3Auth with the Neon Blockchain in Android
+sidebar_label: Android
+image: "guides/banners/neon.png"
+displayed_sidebar: resources
+keywords: [android, neon, web3auth, authentication, blockchain]
+description: "Integrate Web3Auth with the Neon Blockchain in Android | Documentation - Web3Auth"
+---
+
+import InstallationSnippet from "@site/src/common/docs/android-connect-blockchain/_evm-installation.mdx";
+import GetAccountSnippet from "@site/src/common/docs/android-connect-blockchain/_evm-get-account.mdx";
+import UserInfoSnippet from "@site/src/common/docs/android-connect-blockchain/_evm-user-info.mdx";
+import GetBalanceSnippet from "@site/src/common/docs/android-connect-blockchain/_evm-get-balance.mdx";
+import InitialisationSnippet from "@site/src/common/docs/android-connect-blockchain/_evm-initialisation.mdx";
+import SignMessageSnippet from "@site/src/common/docs/android-connect-blockchain/_evm-sign-message.mdx";
+import SendTransactionSnippet from "@site/src/common/docs/android-connect-blockchain/_evm-send-transaction.mdx";
+import Tabs from "@theme/Tabs";
+import TabItem from "@theme/TabItem";
+import SEO from "@site/src/components/SEO";
+
+<SEO
+  title="Integrate Web3Auth with the Neon Blockchain in Android"
+  description="Integrate Web3Auth with the Neon Blockchain in Android | Documentation - Web3Auth"
+  image="https://web3auth.io/docs/guides/banners/neon.png"
+  slug="/connect-blockchain/evm/neon/android"
+/>
+
+While using the Web3Auth Android SDK, you get the private key and sessionId within the user scope.
+This private key can interact with [Neon](https://neonevm.org/) to make any blockchain calls, like
+getting the user's `account`, fetch `balance`, `sign transaction`, `send transaction`, `read` from
+and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on
+that.
+
+## Installation
+
+<InstallationSnippet />
+
+## Chain Details for Neon
+
+<Tabs
+ defaultValue="mainnet"
+  values={[
+    { label: "Mainnet", value: "mainnet", },
+    { label: "Testnet", value: "testnet", },
+  ]}
+>
+<TabItem
+  value="mainnet"
+>
+
+- Chain ID: 0xe9ac0d6
+- Public RPC URL: https://neon-proxy-mainnet.solana.p2p.org (Avoid using public rpcTarget in
+  production, use services like Infura, Quicknode etc)
+- Display Name: Neon Mainnet
+- Block Explorer Link: https://neonscan.org/
+- Ticker: NEON
+- Ticker Name: NEON
+
+</TabItem>
+
+<TabItem
+  value="testnet"
+>
+
+- Chain ID: 0xe9ac0d6
+- Public RPC URL: https://devnet.neonevm.org (Avoid using public rpcTarget in production, use
+  services like Infura, Quicknode etc)
+- Display Name: Neon Testnet
+- Block Explorer Link: https://devnet.neonscan.org/
+- Ticker: NEON
+- Ticker Name: NEON
+
+</TabItem>
+</Tabs>
+
+## Initialize
+
+<InitialisationSnippet />
+
+## Get User Info
+
+<UserInfoSnippet />
+
+## Get Account
+
+<GetAccountSnippet />
+
+## Get Balance
+
+<GetBalanceSnippet />
+
+## Send Transaction
+
+<SendTransactionSnippet />
+
+## Sign a message
+
+<SignMessageSnippet />