@@ -15,18 +15,18 @@ blockchain. Providers take JSON-RPC requests and return the response. This is no
1515submitting the request to an HTTP or IPC socket-based server. With Web3Auth, you get two types of
1616providers, depending on the product you use:
1717
18- 1 . [ Shamir Secret Sharing based Private Key Providers] ( #private-key-providers-non-mpc )
19- 2 . [ Threshold Signature Scheme based MPC Providers] ( #mpc-providers )
18+ 1 . [ Shamir Secret Sharing based Private Key Providers] ( #private-key-providers-pnp--sfa )
19+ 2 . [ Threshold Signature Scheme based MPC Providers] ( #mpc-core-kit- providers )
2020
2121## Web3Auth is Chain Agnostic
2222
2323By default, Web3Auth supports the ` secp256k1 ` and ` ed25519 ` key curves. While these key curves serve
2424the majority of blockchains out there, certain blockchains have different curve implementations of
25- their own. While for our MPC products , you need dedicated providers to interact with certain
26- blockchains, with ** Web3Auth non-MPC products you can interact with any blockchain of your choice** .
25+ their own. While for MPC Core Kit , you need dedicated providers to interact with certain
26+ blockchains, with ** Web3Auth PnP & SFA you can interact with any blockchain of your choice** .
2727
28- In Web3Auth non-MPC Products , the ability to export the user's private key comes in handy. This
29- private key can be utilized by the dApp to interact with the chain.
28+ In Web3Auth PnP & SFA , the ability to export the user's private key comes in handy. This private key
29+ can be utilized by the dApp to interact with the chain.
3030
3131You can read more about this in our [ Connect with Other Blockchains] ( ./other/ ) section.
3232
@@ -39,7 +39,7 @@ transactions, smart contract wallets, different elliptic curve pairs and even RS
3939
4040:::
4141
42- ## Private Key Providers (non-MPC )
42+ ## Private Key Providers (PnP & SFA )
4343
4444The Private Key Providers work with the majority of Web3Auth products, including Plug and Play SDKs,
4545Single Factor Auth SDKs, and tKey SSS (v1) SDKs. As the name suggests these providers are a wrapper
@@ -56,16 +56,16 @@ Web3Auth supports the following private key providers for Web SDKs:
5656- [ XRPL Private Key Provider] ( /sdk/pnp/web/providers/xrpl ) : For connecting with XRPL Blockchain
5757- [ Common Private Key Provider] ( /sdk/pnp/web/providers/common ) : For connecting with any blockchain.
5858
59- ## MPC Providers
59+ ## MPC Core Kit Providers
6060
6161The Threshold Signature Scheme-based MPC Providers work with our MPC Core Kit SDK. These providers
6262generate a signature of the particular key curve the provider is configured for and accordingly
6363gives you the interface to initialize with the blockchain it is configured for. Currently, Web3Auth
6464MPC Core Kit supports the following providers:
6565
66- - EIP1193 MPC Provider: For connecting with EVM-based chains [ Available by default within the SDK ]
67- - Bitcoin MPC Provider (coming soon)
68- - Solana MPC Provider (coming soon)
66+ - EIP1193 MPC Provider: For connecting with EVM-based chains
67+ - EDDSA MPC Provider: For connecting with Solana and other chains that support the ` ed25519 ` curve.
68+ - Bitcoin MPC Provider
6969
7070## Reference Guides for Blockchain Connections
7171
0 commit comments