Private payments on Sei · testnet
Money with an inner side.
Batin is a private payments vault on Sei. You hold SEI and USDC in one shielded pool and pay people with an address or a link. The chain sees money go in and money come out. Who paid whom, and how much, stays on your phone.
Unaudited. Single-operator test setup. Use test funds only.
On the chain
Only in your phone
The name
Bātin is Arabic for the hidden, inner side of a thing. Its opposite is zāhir, the outward side. Every Batin payment has both: an outside the chain can check, and an inside only the people involved can read.
How it works
Five steps, two layers.
Each step has a public part that Sei records and checks, and a hidden part that stays encrypted on your device. The top half of each column is what an observer gets. The hatched half is what they don't.
- 01
Deposit
Send SEI or USDC into the pool from any Sei address. The deposit waits as a pending record until the approval service admits it. If it never does, only you can take it back.
Sei seesYour address, the asset, the exact amount, the time.HiddenWhich note you now own. - 02
Hidden balance
Once approved, your money is a set of notes. On-chain, each note is a 32-byte hash. The amount, the asset and the owner are sealed inside it.
Sei seesTwo new hashes in the note tree.HiddenAmounts, asset, owner, your total. - 03
Pay
Your phone proves the payment balances without revealing it, and a relayer submits the proof. Pay a batin1 address, pay a request someone sent you, or pay into a link.
Sei seesTwo spent-note tags, two new hashes, two ciphertexts, the time.HiddenSender, recipient, amount and whether it was SEI or USDC. - 04
Claim
Whoever opens a payment link claims the money into their own wallet. The secret sits in the part of the URL a browser never sends to a server.
Sei seesThe same as a payment: tags, hashes, ciphertexts.HiddenWho opened the link, and what it held. - 05
Withdraw
Leave the pool to any Sei address. The withdrawal is public by nature. Which deposit, payment or link it came from is not.
Sei seesRecipient, asset, exact amount, relayer fee, the time.HiddenWhich notes paid for it.
Private, public, trusted
The whole picture, including the weak parts.
A privacy tool is only as honest as its list of limits. This is the short version. The threat model has the long one.
Stays private
- The amount and the asset of every payment inside the pool.
- Who paid whom.
- Your balance and how many notes make it up.
- Which deposit funded which withdrawal.
Is public
- Deposits: address, asset, exact amount, time.
- Withdrawals: recipient, asset, exact amount, fee, time.
- That a private payment happened, and when.
- Matching amounts. 37.12 in and 37.12 out is easy to link. Use round amounts and wait between steps.
You trust
- The test setup. One operator ran it, and that operator could forge proofs. Mainnet needs a public ceremony.
- The approval service. It can refuse or delay a deposit. It can't move funds or block your refund.
- The relayer. It sees your IP and timing and can refuse to submit. It can't change where money goes.
- Circle, which can freeze USDC held by the pool. SEI is not affected.
- Your phone. Malware on an unlocked phone can spend.
Nobody holds an admin key. The contracts have no owner and no upgrade path.
Built for a phone
Everything happens in one hand.
No extension, no desktop step, no QR codes. The app is a web page you can add to your home screen.
Passkey unlock
Your wallet seed is 32 random bytes made on the phone. Where the browser supports it, a passkey wraps the seed so Face ID or a fingerprint opens it. Keys are never derived from a signature.
A backup you hold
The seed is also sealed with your passphrase (scrypt, then AES-GCM) into a small file you save through the share sheet: Files, Drive, or a message to yourself.
Proofs made on the device
The zero-knowledge proof for every payment is computed in your browser, in a background worker. No server sees your keys or your notes.
Links that act like cash
A payment link carries its secret after the #, which browsers never send to a server. The app wipes it from history the moment it opens. A request link is the opposite: it holds no money, only the address to pay.
Recovery from the chain
Lose the phone and your backup is enough. The app rescans the pool, tries every ciphertext with your view key, and rebuilds your balance.
Gas you don't think about
On testnet, private payments and claims are submitted by a sponsor, so a new recipient needs no SEI to receive. Withdrawals pay a small fee from the amount.
Where it stands
Testnet, verified, unaudited.
Batin runs on Sei Atlantic-2. The contracts are deployed, verified on Sourcify and visible on Seiscan. Nothing is on mainnet, and nothing will be before an audit and a public setup ceremony.
| Part | State | Evidence |
|---|---|---|
| Protocol spec v2.1 | Draft | Read the spec |
| Join-split circuit | Passing | 22,292 constraints, Groth16 on BN254, 12 public inputs |
| Vault contract | On testnet | BatinPool · verified |
| SDK and relayer | On testnet | Note encryption, links, scan recovery, sponsored claims |
| Phone web app | On testnet | Open it |
| Independent audit | Not started | Required before mainnet |
| Public setup ceremony | Not started | Required before mainnet |
| Mainnet | Not planned | Not until the two rows above are done |
Cost today: a private payment uses about 1.26M gas, roughly 0.07 testnet SEI at 55 gwei. Most of it is Merkle-tree hashing, and reducing it is open work.