Arcana Auth SDK

There is no way to selectively turn off the Arcana wallet features. However, if the application does not perform any blockchain transactions, the wallet feature can be disabled by setting the wallet visibility mode to false while integrating the app with the Arcana Auth SDK. In this case, the Arcana wallet will not be visible to the authenticated user as long as no blockchain transaction is triggered.

If you need to completely disable the Arcana wallet feature in the app, you can request a private build of the Arcana wallet by contacting Arcana with the use case details.

No, Arcana's ADKG algorithm can still generate the key using the key shares from the other nodes that are accessible. The algorithm is designed to tolerate a certain number of nodes being inaccessible, depending on the total number of participating nodes. For more details, see Arcana's Technical Whitepaper.

Yes. This is made possible by the aggregate login feature of the Arcana Auth SDK.

For this feature to work, the user must have the same email ID registered with the different authentication providers.

Arcana Auth SDK uses the email ID to uniquely identify the user even if the user uses different social providers or a passwordless email option to log in to a Web3 app. It associates a single key for such a user which results in the user seeing the same wallet address. If the user has different email IDs associated with different social providers then each login is treated as a unique, different user and the same user will see a different wallet address when logging into the same Web3 app.

Arcana Auth SDK allows Web3 app developers to tailor the wallet address experience for their users. It provides two 'Keyspace' options at the time of application registration:

• App-Specific Keys
• Global Keys

If a developer selects the Global Keys option, then the user gets assigned the same key across all applications that integrate with the Arcana Auth SDK and chooses the same Global Keys option. The same key means the wallet address of the user is the same across different Web3 apps that integrate with the Arcana Auth SDK. This is true across apps that use EVM-compatible chains. If two apps use global keys but one of them is on an EVM-compatible chain and the other is not, then the keys will be different across such apps. The Arcana's ADKG subsystem will assign the user different sets of keys for such apps resulting in different wallet addresses across such apps.

For more details, see app-specific vs. global keys

No.

The global keys feature enables an authenticated user to have the same wallet address across different Web3 apps in the Arcana ecosystem.

However, an authenticated user will see **different wallet addresses across two chains configured in a single Web3 app if one of them is EVM-compatible whereas the other is not. Also, in the case of two Web3 apps, one of which uses an EVM-compatible chain and the other that uses chains that are not EVM-compatible, the authenticated user's wallet address will be different for each app.

Yes.

The Arcana wallet supports Chrome browser Incognito Window as well as Private Window in case of Safari browsers. Earlier, if third-party cookies were disabled, the built-in, plug-and-play login pop-up modal did not show up in some cases. These use cases are now addressed by the SDK.

Developers can use the canReconnect and reconnect functions of the AuthProvider to check before allowing users to reconnect whereby users do not need to re-login if they refresh the page or close the tab and re-open it again within a 30-minute window.

Yes. See Arcana JWT Token for details.

Apps can integrate with the Arcana Auth SDK to enable an embedded, non-custodial Web3 Arcana wallet for every authenticated app user.

To integrate an app, developers must register and configure the app with the Arcana network, and then install the auth package and create a new AuthProvider. While instantiating the AuthProvider developers can manage the user experience for signing blockchain transactions through the input parameter alwaysVisible. This parameter controls whether the Arcana wallet UI is automatically displayed in the application's context right after a user authenticates or it shows up only when the app triggers a blockchain transaction that requires the user's approval.

For details, see Arcana wallet visibility modes.

By default, Arcana wallet does not set the window.ethereum value in the app's context. To explicitly set this value, during the integration of the app with the Arcana wallet, when AuthProvider is instantiated, developers must specify the setWindowParameter=true. For details, see the Arcana wallet Usage Guide.

Arcana wallet is a non-custodial wallet. Here is how it differs from the self-custodial wallets: