Web3 application developers can easily provide instant, non-custodial wallets to their users by integrating with the Arcana Auth SDK. This removes the need for users to install a separate wallet, back up their keys, or navigate the process of buying cryptocurrency. Instead, users can sign blockchain transactions directly within the application using the embedded web wallet widget, without the need for any browser extensions.
The Arcana wallet offers a user-friendly, secure, and customizable interface that can be branded to match your application. Users do not need to generate or manage their cryptographic keys or remember any passphrases. The wallet is built using the state-of-the-art asynchronous, distributed key generation protocol which allows users to have full control over their wallets and abstracts the complexity of cryptography. With Arcana wallet, Web3 application users can experience true self-sovereign decentralized identity.
Supported Web3 Wallet Operations
- Check account balance
- Sign blockchain transactions
- Add, and modify the network configuration
- Switch to a different network
- Deploy smart contract to a specific network
- Add, send, and receive custom tokens (ERC-20) and NFTs (ERC-721 and ERC-1155)
- View account transaction activity such as how many native, custom tokens or NFTs were transacted or contracts deployed
- Use the provider interface to call any standard Ethereum JSON RPC specification methods
- Export private key and use it to import Arcana wallet account to a third-party Web3 provider
In the future, the Arcana wallet may also allow application users to permit application developers and see their profile data such as email ID, profile picture, and user name.
The Arcana wallet does not allow an application user to import any blockchain account created using a third-party wallet provider.
Wallet Usage Configuration
Arcana wallet can be configured at the time of integrating the application with the Auth SDK. While instantiating a new
AuthProvider, the developer can choose one of the available wallet user experiences for signing blockchain transactions through the
alwaysVisible input parameter. See Arcana wallet visibility mode and the Arcana wallet configuration guide for details.
Network Switching Behavior
Depending upon the Arcana wallet visibility mode setting configured by the developer, the network switching behavior may vary.
The Arcana wallet comes pre-configured with some of the popular blockchain networks such as Ethereum and Polygon. Other EVM-compatible blockchain network configurations can be added programmatically to the wallet by application developers.
These additional network settings are stored and retained across user login sessions. If the developer has configured the Arcana wallet visibility mode to
alwaysVisible=true, then the wallet is always visible in the applications' context. Users can use the wallet UI to add new network configurations and switch to a different network than the one that the developer has provided by default. This is not possible if the
alwaysVisible=false setting is used during Auth SDK integration. In this case, the wallet shows up only when a user has to approve a blockchain transaction and disappears after a user action. For more details, see Arcana wallet visibility modes and network switching behavior.
Custom Network Added by Users
Only the list of networks configured by the developer programmatically is persisted across the user login sessions. Any additional blockchain network configurations added by the application users are only stored locally. Users have to add those custom network configuration settings every time they log in.