Wallet sign-in, RPC, and approval security

No. The SDK handles EIP-6963 multi-wallet discovery, injected-wallet differences, mobile deep links, and QR pairing. The frontend uses the same small set of methods. Manage sessions, revocation, and connection analytics in one console.

A monthly platform fee, plus a charge for each session that is successfully established. Failed signature checks, replayed nonces, revoked or expired sessions are never billed, and every invoice line can be checked.

ChainBridge Nodes. Fully managed RPC, metered in compute units, live on activation — nothing to deploy.

Yes. Deploy the self-hosted gateway in your environment and use the same routing, authentication, rate-limit and observability rules. We provide the gateway and control policies and never access your assets.

Customers use one company endpoint and key; upstream nodes are never exposed. We handle routing, scoring, billing, SLAs and incidents. Health scores and circuit breakers trigger failover when a provider has an issue. Each switch is recorded for audit.

Never. ChainBridge only reads public onchain data. Revocation transactions are signed and sent by your wallet. Any page asking for your private key or seed phrase is not ours. Close it and report it immediately.

Revoking sets the spender's allowance for that asset to 0, so the dApp can no longer move it; if you still need the dApp, approve again. For dApps you are actively using we show the impact before you revoke.

Our "revoked" state comes from an onchain read-back: after confirmation we re-read the allowance and only report success when it is really 0. If the allowance did not change we mark it failed, explain why, and link the block explorer for an independent check.

Automatic execution delegates signing authority and carries more risk than manual revocation. We enable it only when the permission scope is provable, failures are recoverable, and the wallet and network pass security checks. It always carries a budget cap, an expiry, a pause switch, and a full audit trail. Until then, revocation stays manual.

No. Requests the upstream answers with an error are not billed to customers, and our internal retries for resilience never charge your request twice (we absorb and reconcile real upstream cost). Batch requests are metered per array item; the rule is published in the docs.

Yes. Compute unit weights and prices keep both a version and an effective date. Any historical bill can be recomputed under the rules that applied at the time. Issued billing periods are not edited directly. Adjustments use a separate record to preserve the audit trail.