Skip to main content

How do I use it?

It is really simple to integrate your dApp with Arcana Network SDKs.

Just two steps.

That's it!

Step 1: Register & Configure dApp

Log in to Arcana Network Dashboard:

Register and configure your dApp as per the use case.

As part of the dApp registration, your dApp is associated with a unique appID. This appID is required during the next step.

Use the dashboard configuration settings to select what kind of user onboarding options need to be supported in your dApp. Optionally, you can set up dApp branding and logos, location or region where user data will be physically stored, storage and bandwidth limits etc.

Step 2a: Authenticate Users with Auth SDK

To enable popular social authentication or passwordless login in your dApp, use the dashboard assigned appID and integrate your dApp with Arcana Auth SDK. For data privacy and security, you can use data encryption functions offered by the Auth SDK. The standard Ethereum provider is exposed by the Auth SDK. This provider can only be used to sign Arcana blockchain transactions.

In future, other blockchain transaction support will be added in the Auth SDK.

Step 2b: Enable User Data Privacy with Storage SDK

To begin storing user data in the distributed Arcana Store, use the dashboard assigned appID and integrate your dApp with Arcana Storage SDK . You can allow dApp users to upload, download, access their data with full privacy and security. Your dApp users control who they share their data with, for how long or when to transfer data ownership to another user.


You can choose to integrate with both Arcana Auth and Storage SDK or only use one of them depending upon your dApp use case.

Arcana Storage SDK works seamlessly with Arcana Auth SDK. If you wish to use Arcana Storage SDK and do not wish to integrate with Auth SDK, you have the following options:

  • Use BYOK option In this case, the dApp developer will be required to manage the keys for dApp users or ask end users to manage their own keys. These keys are required for signing Arcana blockchain transactions for storage operations. The dApp developer must use the authenticated user keys to obtain a standard Ethereum provider using ethers.js or an equivalent library. This provider must be specified at the time of initializing the Storage SDK.

  • Use a third party wallet Once the dApp user logs into a wallet using a browser, the window.ethereum value is set to the Ethereum provider. When the dApp is invoked, it initializes the Storage SDK. In this case, when the user is already logged into a third party wallet, if the developer does not explicitly provide the Ethereum provider during SDK initialization, the SDK will use the window.ethereum setting by default. Otherwise, the provider specified by the dApp will be used by the Storage SDK to enable Arcana blockchain transaction signing and approval.

Figure below shows typical interactions with Arcana Network components at a very high level.

Getting Started with Arcana in 3 steps Getting Started with Arcana in 3 steps

Refer to our Quick Start Guide for details.

See Also