Skip to main content

Regular and Web3 modes

A workflow can run in Regular (Web2) or Web3 mode. Web3 mode is the preferred mode for dApps.

Regular mode​

Regular mode allows customers to verify their identity without a Web3 wallet. This is used when your customers do not need a self-custodial web3 wallet to interact with your application. This requires less development, but it means customers cannot prove the ownership of their wallet during onboarding. However, your application can push the wallet via the ComPilot API, or add it as custom data using one of the ComPilot SDKs during onboarding.

Web3 mode​

Web3 mode requires customers to authenticate using their Web3 wallet. This has three benefits:

  • You can link your customers' real-world identity with their Web3 wallets.
  • Customers' wallets can automatically screened with an onchain screening tool connected to ComPilot.
  • At the end of verification, customers are issued reusable KYC reports that can be controlled using their Web3 wallets.

The following blockchains are supported for Web3.

  • All EVM chains (such as Ethereum, and Base)
  • Aptos
  • Cardano
  • Cosmos
  • Polkadot
  • Solana
  • Starknet
  • Tezos

See Web3 authentication for more information.

Selecting modes​

The mode that a workflow uses is determined by how it is called in the app. See Integration for more detail.