Private · Offline · on Solana
A private balance in SOL and USDC that your phone can spend with no internet. It signs the payment and sends it as one SMS, or as a QR code another phone carries.
- 156characters: a whole payment in one SMS
- 0amounts or addresses on chain in a private transfer
- 1key per phone, and it never leaves the phone
- Beta on Solana devnet. Test money. Figures on the phone are demo values.
How the phone pays with no internet
-
01 / 06
Flight mode on.
No Wi-Fi, no mobile data. Earlier, online, you gave this phone an allowance from your private balance, with a daily limit. That allowance is what it can spend now.
-
02 / 06
Signed on the phone.
The phone signs the payment with its own key. The key was created so that it can't be exported: it never leaves the phone, and our server never holds it.
-
03 / 06
One SMS. 156 characters.
The signed payment packs into 115 bytes: 156 characters, with an expiry and a sequence number inside. The code on screen is a real one from the app's test run.
-
04 / 06 · Way out A
Text it.
A cell signal carries the text to the gateway. The gateway checks the signature and the phone's daily limit, and the payment settles on Solana once. A second copy moves nothing.
Coming the live SMS number. The SMS webhook is built and tested; today texts stay in a local test outbox.
-
05 / 06 · Way out B
Show the QR.
The same code as a QR. Any phone with internet scans it and carries it to the gateway. It can read the payment but can't change it.
Or just wait: the queue sends every signed code when this phone is back online.
-
06 / 06 · A basic phone
Paid by text.
It texts the payment in plain words. The gateway asks for one numbered code from a card of 20 one-time codes; the code goes back; paid. Too many wrong codes lock the card.
Beta code-card payments run on the server's ledger, not the zero-knowledge pool.
What "no internet" means here
The paying phone needs no internet.SMS needs a cell signal.The gateway and the chain need internet.
The private side
Sealed on chain.
- 01
A private balance
SOL and USDC go into a zero-knowledge pool on Solana and become sealed notes. Only your keys can spend them: neither our server nor the relayer holds a key that can move them.
- 02
Proved on your device
A private transfer is a Groth16 zero-knowledge proof made on your own device, in seconds, and sent by a relayer.
- 03
What the chain sees
A proof, two one-time "spent" tags and two sealed notes. No amounts, no addresses, not your wallet. A note can't be spent twice.
The honest limits. A deposit is public: your wallet and the amount, and deposits are screened against sanctions lists (screening can refuse a deposit; it never freezes money already in the pool). A withdrawal's amount and recipient are public too. Round amounts help it blend in; timing can link a deposit and a withdrawal unless you wait, and sending with the next wave helps. Privacy grows with the pool's use.
The gateway
What it
refuses.
A payment code is signed by the phone. Change anything and the signature breaks.
Scroll
A code with one character changed
RefusedAn expired code
RefusedA code signed for another network
RefusedA code over the phone's daily limit
RefusedA code from a phone whose permission was taken back
RefusedThe tech, with its status
Built. Tested. On devnet.
Every item marked Built runs on Solana devnet today, with test money. Nothing here is on mainnet, and nothing is audited yet.
- 01
Private balance on Solana
Sealed notes in the pool's Merkle tree: depth 26, room for 67 million. The program computes each commitment itself, so a deposit can't claim more than it paid.
Built - 02
Keys from one signature
One wallet signature, made on your device. A backup line restores everything; a viewing key shows everything and spends nothing.
Built - 03
A key that stays on the phone
A WebCrypto Ed25519 key, created non-extractable. The phone signs with it and never hands it out.
Built - 04
One-SMS payment codes
115 bytes, 156 characters. Each carries an expiry and a sequence number and is checked against the phone's daily limit.
Built - 05
The phone's allowance
Once, online, you move part of the private balance into this phone's allowance. The gateway can spend at most the allowance; you take the rest back any time.
Built - 06
Full proof offline, no allowance
The phone proves the whole payment itself with no internet. One measured run: 447 bytes, 4 SMS parts, proved in 3.6 s. Tested in a browser with the network cut, not yet on a phone in flight mode.
Built · browser test - 07
Pay a phone number
If the number published a private address, it is an ordinary private transfer. If not, a claim link carries a one-time key after the #, never sent to a server; the sender can take it back while it's unclaimed.
Built - 08
Withdraw fast, or with the next wave
To any Solana address: at once, or held and sent together with others in random order. The amount and the recipient of a withdrawal are public; round amounts and waiting help it blend in.
Built - 09
Emergency exit
Anyone can take their notes out with their own wallet and any Solana RPC. No BLACKOUT server needed.
Built - 10
The code card
20 one-time codes for paying by text from a basic phone. In the beta these payments run on the server's ledger, not the zero-knowledge pool.
Built · server ledger - 11
The agent
Plain words become a proposed payment that your wallet confirms. Fixed commands work today; free-form reading switches on with a live model key.
Built - 12
Locked program, outside audit
Today the devnet program can still be upgraded and its trusted setup is a local test one. A public ceremony, open code with a verified build and an audit come first.
Coming
Roadmap
What comes next.
- Now
Devnet beta
The whole app on Solana devnet, open to try with test money.
- Coming
Private swaps
SOL and USDC swapped inside the pool through Jupiter. The output comes back as a new sealed note, with a guaranteed minimum or an instant refund. Public: the asset and the amounts. Not who.
- Coming
Private cross-chain
Exits to other chains through intent networks, NEAR Intents first, including Bitcoin. Then pool to pool between Solana and Base, private on both ends.
- Coming
Live SMS number
Real texts. Today they stay in a local test outbox.
- Coming
Android app
Sends the payment texts itself, and passes payments phone to phone with no internet.
- Coming
Public ceremony and audit
A public trusted-setup ceremony, open code with a verified build, upgrades only after a public delay and then locked, and an outside audit.
- Coming
@names
Usernames for receiving. Being built; not live.
- Coming
Mainnet
After the audit and the ceremony. Then other chains and more tokens.