Zero-knowledge privacy Built
A private transfer is a proof made on your device. The chain sees no amounts, no addresses, not your wallet.
Private balance · offline payments · devnet beta
A private balance on Solana that your phone can spend with no internet, by one SMS or a QR code. A beta on Solana devnet, with test money.
Press the switch
A private transfer is a proof made on your device. The chain sees no amounts, no addresses, not your wallet.
The phone signs a payment and turns it into one SMS or a QR code.
Made on your device. Neither our server nor the relayer holds a key that can move your money.
Coming: private exits to other chains. Built and tested against a stand-in, not switched on yet.
Offline payments Built
No data, no Wi-Fi. The phone holds its own key, and the key never leaves the phone.
Once, online, you move part of your private balance into this phone's allowance. Offline, the phone signs inside it.
115 bytes. Change one character and it is refused. Two copies move money once.
Text it to the gateway, or show the QR to any phone with internet. That phone can read the payment but can't change it.
The paying phone needs no internet. SMS needs a cell signal. The gateway and the chain need internet. In the beta, texts stay in a local test outbox; a live SMS number is Coming.
With no allowance at all, the phone proves the payment itself with no internet: one QR code, or three or four texts. Tested in a browser with the network cut, not yet on a phone in flight mode.
If the number published a private address, it is an ordinary private transfer. If not, a claim link carries the money, and you can take it back while it is unclaimed.
Look-alikes can't both exist: @a1ice is refused next to @alice. Before a first payment the app shows the whole address and a 16-character check code to compare with the receiver.
The Emergency lane Built
Power out, internet out, batteries gone. A basic phone with no apps still pays: a printed card of 20 one-time codes, and plain texts. The gateway asks for one numbered code, and each code works once.
Hidden from the public chain, but our gateway sees these payments. Kept small on purpose: at most 1 SOL and 100 USDC in a lane, 0.5 SOL and 50 USDC a day by text. The text needs a cell signal; the gateway and the chain need internet. In the beta, texts stay in a local test outbox. Everyone else uses the private pool. What the gateway sees
The pool Built
Your wallet and the amount are public, one time. After that the chain sees the relayer and the pool, not your wallet.
Only your keys can spend it. A private transfer shows a proof and two sealed notes: no amounts, no addresses, not your wallet.
Spending reveals a one-time tag. Nothing on chain says which note it was, and a note can't be spent twice.
To any Solana address, fast or with the next wave: held and sent with others, in random order.
Private swaps Live on devnet
SOL to USDC and back, without leaving the pool. Your notes go into an escrow in the pool. Your phone sets the guaranteed minimum, not the relayer. The pool checks it and makes your new sealed note from what came out.
If the minimum can't be met, the amount comes back as a note. After the deadline anyone can trigger the refund: the app has a Refund button, and so does the exit page.
On devnet the swap runs through a small test exchange; on mainnet, through Jupiter. Public in a swap: the amount the pool swapped and what came out. Not who.
Privacy by default Built
A private pool only hides you among others who moved the same amount. So the app steers you into the crowd, and shows you how big it is before you confirm.
Deposits and withdrawals default to amounts many others use.
1.67 SOL becomes 1, 0.5 and 0.1, in random order, each with its own wave. The 0.07 stays in your private balance.
"Next wave or later" is the default. "Now" is one tap, labelled less private: sent alone, right away.
Withdrawing to the wallet you deposited from gets a plain warning and needs a second press.
Your choice of servers Built
By default the app uses our relayer and our RPC. The choice is yours: add another relayer or run your own, and read the chain from this site's RPC, the network's public RPC, or your own. Then no single server has to see everything.
Right now one server, ours, sees both your address reading the pool and your address sending spends. Deposits, the offline gateway and exits to other chains always go through this site's relayer. No other relayer is listed yet; the web app reaches only hosts its policy lists, and your own copy of the app can list yours.
Said plainly
Nobody sees who pays whom in the private pool, us included. Our server only helps your payment reach the chain. Here is the short version; the full page shows the shape of everything it stores.
Read the full pageTrust
The first pass found no way for an outsider to forge money or double-spend in the pool; the third found nothing that lets an outsider steal funds. Most findings are fixed. Not all: the trusted setup is still a local test one, one key can still upgrade the program, and some findings are fixed in part and written up.
An AI audit is not a professional audit. No outside professional audit has been done yet.
One page takes your notes out with your own wallet and any Solana RPC. No relayer and no BLACKOUT server. It runs straight from a file on disk, and it refunds waiting swaps first. An exit is public.
Deposits are checked against sanctions lists. The check can refuse a deposit and nothing else: it never touches money already in the pool. The relayer can refuse to send to a blocked address; the exit page needs no relayer.
Built and tested against a stand-in for the providers. Not switched on yet.
Sends payment texts itself. An early build exists; it is not released.
Today texts stay in a local test outbox.
Not yet. Today this is a devnet beta with test money.