Proofs
Verification stories only — what you can check yourself, and what we refuse to invent. No fake social proof. If a claim is not on this page, assume we have not earned it yet.
What we never claim
There are no monthly active users, growth charts, or adoption figures on this site. Page views exist in a first-party analytics dashboard; funnels, retention cohorts, and campaign attribution do not — and none may be claimed.
There are no testimonials, press quotes, case studies, funding rounds, or partnership badges. The site is young. Inventing scale or social proof would be a lie.
We never say “gas free.” Network fees still go to the chain (or, when you opt in, are paid in USDC through Circle’s on-chain paymaster). The permanent promise is a 0% site fee — we do not take a cut — not that the network works for nothing.
Fee-in-USDC (Circle Paymaster)
On supported networks you can pay the network fee in USDC instead of the native gas token. That is Circle’s permissionless Paymaster: your wallet signs an EIP-2612 permit and an account-abstraction user operation; the paymaster pulls USDC on-chain and refunds leftovers. This site never sponsors gas, never holds the USDC, and never sits between your wallet and Circle’s contract.
Paymaster v0.8 (same CREATE2 address on every chain Circle lists for v0.8):
0x0578cFB241215b77442a541325d6A4E6dFE700Ec
Live for Send, Swap (same-chain), and Bridge when the from network is in the list below. Bridge covers origin gas only; destination fees stay separate and are never claimed as USDC-covered.
| Network | Circle surcharge |
|---|---|
| Ethereum | 0% |
| Base | 10% |
| Arbitrum | 10% |
| Optimism | 0% |
| Polygon | 0% |
| Avalanche | 0% |
| Unichain | 0% |
The 10% on Base and Arbitrum is Circle’s documented surcharge, shown as a number — not “free.” Ethereum, Optimism, Polygon, Avalanche, and Unichain are 0%. Our site fee stays 0% on every path.
Addresses and events: Circle Paymaster docs. How this product uses them (plain language, no API keys, no custody): RESEARCH-PAYMASTER.md.
Signing safety / privacy
Object pages keep the subject in the URL fragment after # — the address on /a#…, the transaction hash on /tx#…, and the token contract on /t#…. Browsers do not send the fragment to any server, including ours. That is structural privacy, not a privacy policy promise.
Before you sign, tools exist to decode what a wallet is asking for and, on networks that support it, to simulate balance deltas:
- Signature decoder — typed data and signature payloads in plain fields
- Calldata decoder — what a call actually encodes
- Transaction simulator — balance deltas when the network can simulate them
- EIP-712 hasher — domain separator and struct hash from typed data
Fuller disclosure of who sees an address when a tool makes a network request lives on Privacy.
Constants / verification
Signing-related paths were checked against published external constants rather than only against this site’s own code — for example ERC-721 interface ids, Safe typehashes, CoW’s on-chain domain separator, and Sablier’s published deployments. That work caught a real bug; it is not a third-party audit badge.
Safe transaction hashes can be recomputed locally and compared to what a device or service shows:
- Safe tx hash verify — recompute a Safe transaction hash offline
- Safe inspector — inspect a Safe and verify queued transaction hashes
Network capability claims (which chains can read balances, price tokens, or sign) are measured on Network coverage, not asserted as marketing counts.
Strategy label: proofs not hype. Prefer a public address, a docs link, or a tool you can run yourself over any number we cannot show.