Supported Blockchains

Supported blockchains for wallet verification flows

Cryptographic signature proofs and micro-transactions (Satoshi Test) are blockchain-dependent, because they rely on wallet connectivity, signing standards, or transaction monitoring on specific networks. Wallet screenshots and self-declaration are blockchain-agnostic, because they do not depend on direct blockchain integration.

The supported blockchains are also available via our API. Use the API to always retrieve the latest supported blockchain list for the selected verification methods.

Query support through the API

Call GET /blockchains for the known blockchain list. Filter by one or more verification flows by repeating supportedVerificationFlow. Multiple values use OR semantics, so this example returns blockchains supporting either Signature Proof or Satoshi Test:

curl --get 'https://api-dev.cryptoswift.eu/blockchains' \
  --header "X-Api-Key: $API_KEY" \
  --data-urlencode 'supportedVerificationFlow=SIGNATURE_PROOF' \
  --data-urlencode 'supportedVerificationFlow=SATOSHI_TEST'

Every item contains name and can contain an EVM chainId. When the flow filter is present, each item also contains supportedVerificationFlow. Available filter values are SIGNATURE_PROOF, SATOSHI_TEST, VISUAL_PROOF, and SELF_DECLARED. The X-Total-Count response header contains the number of returned blockchains.

Use the returned name in API requests that require a blockchain. Do not rely on this page's examples as a permanent allowlist.

Cryptographic Signature Proofs

For connected cryptographic signature proofs, CryptoSwift uses AppKit. Users can also sign the supplied message manually in a compatible wallet and paste the signature into the widget. Both paths use the same server-side signature verification.

EVM

AppKit supports all EVM-compatible blockchains. As long as the blockchain is included in Viem’s chain definitions, AppKit will support it. This includes Ethereum, Polygon, Arbitrum, Optimism, Base, Avalanche, BNB Smart Chain, and many more.

When submitting EVM proof through the direct API, use an EIP-191 plain-message signature. See the EVM signature scheme and examples.

Bitcoin

AppKit supports Bitcoin wallet connections through WBIPs and the Bitcoin Wallet Standard. Supported wallets include Xverse, OKX, Leather, and Phantom.

CryptoSwift accepts supported legacy Bitcoin message signatures and BIP-322 simple signatures. Taproot (bc1p) addresses are currently not supported by signature verification. Wallet connection support does not guarantee support for every signing format or address type.

Solana

AppKit supports Solana. You can connect Solana wallets and interact with the Solana blockchain.

TRON

AppKit supports TRON on web frameworks. You can connect TRON wallets and interact with the TRON blockchain.

Other Chains via WalletConnect Protocol

Blockchains not listed above can still work with WalletConnect at the protocol level for dApp-wallet communication. The WalletConnect Cloud Supported Chains page lists all chains available through the protocol, including Cosmos, Sui, Stacks, Near, Stellar, and more.

You can also find a list of supported dApp-wallets here.

Micro Transactions (Satoshi Test)

Blockchain	Networks	Native Asset	Additional Supported Assets
Bitcoin	Mainnet, Testnet	BTC
Bitcoin Cash	Mainnet	BCH
Dogecoin	Mainnet, Testnet	DOGE
Litecoin	Mainnet	LTC
Dash	Mainnet	DASH
Ethereum	Mainnet, Sepolia	ETH	USDC
Optimism	Mainnet	ETH
Tron	Mainnet	TRX
XRPL	Mainnet	XRP

For Satoshi Test, most supported asset and blockchain combinations use the blockchain's native asset, such as BTC for Bitcoin or ETH for Ethereum. Some blockchains also support additional tokens: Ethereum supports USDC. We are open to adding support for more tokens based on customer requests. Feel free to reach out to us.

Support in the table above means CryptoSwift can monitor these blockchains for Satoshi Test verification. Mainnet entries are intended for production use, while testnets are intended for sandbox and development use only.

Supported Blockchains