Skip to main content

PnP Modal SDK - v5 to v6

General​

web3auth.connected is introduced​

Manage session using web3auth.connected instead of web3auth.provider​

With V6, users can manage their session using web3auth.connected instead of web3auth.provider.

// With V6
if (web3auth.connected) {
  setLoggedIn(true)
}

provider is now always available​

In V5, we used to add a check for setting the provider only if the web3auth.provider was present. But now with V6 we always have a provider available even if the user is not logged in.

// With V5
if (web3auth.provider) {
  setProvider(web3auth.provider)
}
// With V6
setProvider(web3auth.provider) // before the connect() or connectTo(), provider is available.

rpcTarget and chainId is now a mandatory parameter​

Previously, the Web Modal SDK required chainConfig as a parameter which had rpcTarget & chainId as the optional parameter. But with V6, it's mandatory to add rpcTarget & chainId in the chainConfig object.

const web3auth = new Web3Auth({
  clientId,
  chainConfig: {
    chainNamespace: CHAIN_NAMESPACES.EIP155,
    chainId: '0x1',
    rpcTarget: 'https://rpc.ethereum.org', // This is the public RPC we have added, please pass on your own custom endpoint while creating an app
  },
  web3AuthNetwork: 'sapphire_mainnet',
})
On this page