Skip to content

Non-EVM Chains

Arcana Auth supports both EVM-compatible chains as well as non-EVM chains such as Solana and MultiversX. Other non-EVM chains will be added in the future.

The Arcana Auth SDK offers a selection of EVM as well as non-EVM chains as the pre-configured blockchain networks. Once users log into an app integrated with the Arcana Auth SDK, these pre-configured chains are available out of the box to the Arcana wallet users.

Non-EVM Chains

When registering an app through Arcana Developer Dashboard, the choice of chain type (EVM, MultiversX, or Solana) is final. App developers can't change it later. They can switch the default chain within the same type. For example, a Solana app on Testnet can switch to Solana Mainnet or Solana Dev but not to MultiversX or an EVM chain.

Web3 Wallet Operations

The built-in, embedded, non-custodial wallet offered by the Arcana Auth SDK, the Arcana wallet supports JSON/RPC calls. For non-EVM chains, the list of supported calls may vary.

Solana

  • signMessage
  • signTransaction
  • signAllTransactions
  • signAndSendTransaction

MultiversX

  • mvx_signMessage
  • mvx_signTransaction
  • mvx_signTransactions
  • getAccounts
  • getPublicKey

Adding Chains

When a non-EVM chain is selected for an app, developers and users cannot arbitrarily add any other supported chain types (other non-EVM chains, EVM chains) in the Arcana wallet. This is because there is no uniform standard for wallet addresses across non-EVM chains and switching chain type may cause the wallet address to change.

For details refer to the 'Non-EVM chains' section in the Arcana Developer Dashboard User's Guide.

Keyspace User Experience

Developers can tailor the user's wallet experience by using the default app-specific keys or configure global keys for the app via the Arcana Developer Dashboard.

In the case of app-specific keyspace configuration, users will have unique keys assigned for every app irrespective of whether the app is registered for an EVM or non-EVM chain type.

For global keyspace configuration, app users will see the same wallet address across the apps that are configured to use global keys and an EVM-compatible chain.

However, apps that are configured for global keyspace and a non-EVM chain type will have a different user experience. Users will not see the same wallet address across such apps. Each non-EVM chain type will result in a different wallet address for the same user. The reason for this is the difference in the non-EVM chains cryptography algorithms.

Non-EVM Key Cryptography

For EVM chains, authenticated user keys are based on the secp256k1 curve. If developers enable the global keys option, users will have the same wallet address. This is true only across all global keys-enabled apps that are using any supported EVM-compatible chain with Arcana Auth SDK.

Non-EVM chains use different cryptographic algorithms. Solana uses ED 25519 curve. MultiversX uses BLS multi-signatures. Therefore, if two apps are configured for global keys, one of them using an EVM chain and the other using a non-EVM chain, or two different non-EVM chains, then users will see different wallet addresses across such apps.


Last update: February 14, 2024 by shaloo, shalz