Five steps to a tier badge.
From “connect wallet” to badge. Each step notes exactly who can see what.
You sign. Nothing moves.
Connect the wallets you want to enroll and sign one plain message per wallet. It says “I control this address” and nothing else. It is a signature, not a transaction: no gas, no spending, no approvals. The signing request can never touch your funds.
Visible to others: nothingYour browser vets the enclave first
Before anything is sent, the enclave must prove what it is. Google issues a signed certificate (an attestation) stating the exact sealed-enclave code image that is running, that it runs on real memory-encrypted hardware, and that debugging is off. Your browser checks that certificate against the image fingerprint 6figs publishes, before releasing anything.
Google attests
signs: "this exact image,
on real sealed hardware"
Certificate (JWT)
image fingerprint, GCP project
not debuggable, fresh nonce
Your browser checks
signature, the fingerprint we pinned
anything wrong, refuse to send
The fingerprint is public. If 6figs ever changed what the enclave runs, every browser would notice.
Addresses travel encrypted, to the enclave only
Your signatures and addresses are encrypted to the enclave's key before they leave your browser. Even a network attacker or a hostile proxy sees ciphertext. The enclave decrypts, verifies your signatures, then reads balances from public blockchains and prices from market APIs, all inside the sealed box.
Visible to others: only that a request happenedTier computed, addresses forgotten
The enclave totals your portfolio, assigns the highest tier you qualify for, and replaces your wallets with one-way pseudonyms (nullifiers), a kind of hash that can't be turned back into an address. It signs the result with its key and issues a fresh attestation bound to the exact result bytes. Then the plaintext addresses exist nowhere. Not in memory, not in storage.
Visible to others: nothing (signed, not sent yet)Server verifies, stores almost nothing
Your browser checks the signed result first, then forwards it. The 6figs server independently verifies the signature and the attestation (same image fingerprint, fresh nonce, no debug mode), and stores: your tier, a coarse band, your top three token symbols (disclosed automatically, symbols only, never amounts), and the wallet pseudonyms. There is no column anywhere for an address or an amount; the database schema makes storing one impossible.
Visible to others: your tier badge (if visible)STAYING FRESH
Markets move, so verification isn't frozen in time. The server holds your wallet list as a sealed envelope it cannot open. Only the enclave can. On a schedule (and when you press “refresh”), the envelope is replayed to the enclave, which re-reads balances and re-signs a fresh tier. You sign nothing.