The dApp end users are required to have their own secret private keys in order to interact with any blockchain and crypto based systems. Generating and managing private keys is cumbersome and makes for a very different user experience than the Web2 applications.
Arcana lowers this barrier to entry and simplifies how dApp end users onboard the Arcana Network Platform and blockchain powered smart contracts driven dApps by allowing various authentication mechanisms. You can enable different authentication mechanism to onboard the application users. The end users have the flexibility to choose the authentication method that best suits their comfort levels and sensitivity to data privacy, security and user experience.
Supported Authentication mechanisms
Arcana allows user authentication through the following mechanisms:
In case of BYOK, the keys are either managed by the users themselves or through third party wallet providers.
You can also use Arcana Auth SDK whereby a standard Ethereum provider interface can be accessed by the dApp. This provider encapsulates user assigned distributed private key generated by DKG. Once authenticated using social or passwordless mechanisms, the dApp can use this provider to enable users to securely sign blockchain powered storage operations.
Here is a relative comparison for various user authentication mechanims that can be deployed by dApps in the context of Arcana Network platform:
|Authentication Type||Privacy||Security||User Experience|
|Social authentication||Managed by social OAuth provider||Managed by social OAuth provider||Familiar/Easy|
|Passwordless||No password shared with any provider||No password shared so relatively secure||Seamless, no need to remember passwords|
|BYOK||Full privacy as keys not shared with any provider||High security as keys are not shared with anyone||Painful as losing key results in loss of access to any blockchain enabled assets|