Skip to main content


FAQ regarding Arcana Network SDK usage and how dApps can integrate and use the features.


Can a dApp integrate with only one of the Arcana Network SDKs?

Yes. It depends on the application use case.

If the dApp needs to onboard users via social authentication, passwordless login, or if the dApp requires a Web3 wallet provider to sign blockchain transactions on any EVM-compatible blockchain network, then it must integrate with Arcana Auth SDK.

If the dApp requires to enable user data privacy and access control, then in addition to the Auth SDK, the dApp must also obtain a Web3 wallet provider by first integrating with the Arcana Auth SDK. Instead of the Auth SDK, the dApp can choose to use one of the supported third-party wallet to sign Arcana Store file access storage operations.

For details see how to use a third-party wallet with Storage SDK.

How do I enable the Web2 social authentication experience in my dApp to onboard new users?

You can enable one or more social authentication mechanisms in your dApp by configuring Auth settings using the dashboard and integrating with Arcana Auth SDK. For details, see how to enable Google authentication Guide.

How do I enable passwordless login in my dApp to easily onboard new users?

You can enable a passwordless login mechanism to onboard dApp users by simply calling the loginWithLink API in your dApp after integrating with the Arcana Auth SDK. For details, see how to enable passwordless authentication Guide.

Can a dApp developer use Arcana the Storage SDK with a HDWallet Provider or with a user-provided private key?

The Arcana Storage SDK expects a standard EIP 1193 provider during initialization.

Arcana wallet, MetaMask, and every other existing web wallet support EIP 1193 providers. As long as you provide an EIP 1193 provider to the Storage SDK, it should work.

For HD wallet usage, you will need a wrapper from the HD wallet provider to EIP 1193 provider and then use it with the Storage SDK.


For security reasons, Arcana Storage SDK does not allow integration with dApp using a private key approach.