Using Web3 Wallet vs. Key
In the Web3 ecosystem, an application user can establish a uniquely identifiable 1:1 connection to the blockchain using secrets called keys. These are private keys and they are not supposed to be shared. All user assets backed on the blockchain are linked to this private key and its loss means the loss of blockchain assets owned by the user.
Crypto wallets or Web3 wallets are an abstraction for keeping private keys secure. The Arcana wallet is similar in functionality to a typical Crypto wallet that is meant to keep crypto assets safe and accessible. Web3 wallet is a much more secure mechanism than using a key for blockchain access. Wallets expose the secure EIP-1193 standard Ethereum Provider interface.
The Arcana wallet allows application users to securely sign blockchain transactions without having to create, manage and secure their keys by offering them a non-custodial wallet.
It uses a state-of-the-art asynchronous, distributed key generation algorithm, (DKG), to generate and manage the private keys associated with each application user. The DKG subsystem of Arcana Auth cannot access the user's keys on its own. It does not store any local copy of the user keys and no single node in the subsystem has access to the keys. The Arcana wallet never exposes the private key associated with any app user unless the user asks to export their key.
The Arcana wallet uses distributed keys generated and managed using robust cryptographic primitives. Each application user is associated with a key pair. This key is never exposed to the app developer or any entity within the Arcana Auth ecosystem. Working with user keys directly in an application is not recommended as they are visible to the application and could pose a security risk. Arcana wallet uses the standard EIP-1193 Ethereum provider interface for signing blockchain transactions. This wallet provider is used by applications for performing JSON RPC interactions with the blockchain network.