Multi-wallet sign-in · SIWE and SIWX

Wallet sign-in

One wallet click and users are in — no sign-up. Browser wallets, mobile wallets, and QR codes all connect. Sign-in follows SIWE / SIWX, checking the domain, chain, and nonce individually. Any session can be revoked at any time.

ChainBridge will never ask for your private key or recovery phrase. Any page that does is not us.

Wallets supported today

  • MetaMask
  • WalletConnect
  • Coinbase Wallet
  • Phantom
  • OKX Wallet
  • Trust Wallet
  • Rabby
  • imToken

Wallet names we support, not customer logos. Which wallets work in your browser is decided by the wallet itself, not by us.

What the connection layer handles

What you get out of the box

No per-wallet adapters. Connection, authentication, sessions, network switching, and analytics in one SDK.

Multi-wallet support

Injected wallets, WalletConnect, mobile deep links, and QR codes share one connection flow. After connecting, account and chain changes are handled through a unified event interface, with no separate adapter needed for each wallet.

SIWE / SIWX authentication

Supports both SIWE (EIP-4361) for EVM and SIWX for Solana. The domain, origin, chain ID, nonce, validity period, and signature are each checked. Any mismatch is rejected.

Session management

Inspect, revoke, or expire any session. Nonces are single-use, so replays fail. Every connection is logged separately, and revocation is instant.

Network switching

Provides switch-network and add-network calls, with Chinese-language error messages. Whether to stop signing on a chain mismatch is your app's call — we will not make it for you or your users.

Connection analytics

Track success rate, latency samples, wallet mix, and redacted failure reasons for your account.

Browser and mobile SDKs

The TypeScript SDK covers browsers, mobile deep links, QR pairing and return-link parsing. Browsers need no bundling: the WalletConnect adapter is a ready-made <script> build artifact that works as-is.

Live metrics

Connection quality and success rates

Track connection performance over the last 24 hours.

Multi-wallet
Connection and authentication built in
Observability
Auth API status
Low latency
Connect time target
Multiple chains
Availability follows the network catalog.

How billing works

ChainBridge Connect is a monthly platform fee plus a per-connection charge. Failed auth and reused nonces are not billed.

Monthly platform fee
Priced per project and environment; includes console, keys, and logs
Connections
Per successful session, with volume tiers
Not billed
Failed signature checks, reused nonces, revoked sessions
Enterprise terms
Dedicated SLAs, private deployment, and white-label, quoted per contract
Prices and quotas are on the pricing page. View pricing

Security and trust

We verify signatures. We never sign for you.

No asset custodyWe never hold, move, or take custody of user assets.
No private keys, everConnection and authentication use wallet signatures only. We never touch private keys or recovery phrases.
AuditableEvery session created, verified, and revoked is written to requestId the audit trail.
No recovery guaranteesIf a user leaks a private key on another site, recovery of lost assets isn't guaranteed.
FAQ

Before you integrate

No. Connection and authentication use only the signature the wallet returns. We verify the signature, domain, origin, chain ID, nonce, and validity period. We never access private keys or recovery phrases, and we never request permissions beyond signing.

SIWE is the EIP-4361 sign-in standard for EVM. SIWX is its Solana counterpart. ChainBridge Connect supports both under one session model in the console, so you only pick a chain.

No. Only sessions that are successfully established count toward connection usage. Failed signature checks, reused nonces, and revoked or expired sessions are not billed. Your invoice breaks it down line by line.

Yes. The SDK is headless, so you own the dialog and button styles. Enterprise adds white-label auth pages and custom domains.

Sessions are bound to a domain, origin and chain ID, and every nonce is single-use. The console can revoke every matching session in one action, by user, domain or time. Any request on an old session fails globally within 30 seconds.

Start building today

Create an API key and run one end-to-end test. For private deployment and SLAs, see enterprise terms.