Private balance · offline payments · devnet beta

When the world goes dark, your money doesn't.

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

Zero-knowledge privacy Built

A private transfer is a proof made on your device. The chain sees no amounts, no addresses, not your wallet.

Pays with no internet Built

The phone signs a payment and turns it into one SMS or a QR code.

Keys stay with you Built

Made on your device. Neither our server nor the relayer holds a key that can move your money.

Cross-chain Coming

Coming: private exits to other chains. Built and tested against a stand-in, not switched on yet.

Offline payments Built

Privacy
that works
anywhere.

  1. 01

    Flight mode

    No data, no Wi-Fi. The phone holds its own key, and the key never leaves the phone.

  2. 02

    Signed on the phone

    Once, online, you move part of your private balance into this phone's allowance. Offline, the phone signs inside it.

  3. 03

    One code, 156 characters

    115 bytes. Change one character and it is refused. Two copies move money once.

  4. 04

    One SMS or a QR code

    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.

The whole proof, offline Built

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.

Pay a phone number Built

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.

Pay a @name Built

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

When the
smartphones
are dead.

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

How a
payment
gets hidden.

  1. Deposit: seen once

    Your wallet and the amount are public, one time. After that the chain sees the relayer and the pool, not your wallet.

  2. Sealed note

    Only your keys can spend it. A private transfer shows a proof and two sealed notes: no amounts, no addresses, not your wallet.

  3. Spent tag

    Spending reveals a one-time tag. Nothing on chain says which note it was, and a note can't be spent twice.

  4. Withdrawal: public

    To any Solana address, fast or with the next wave: held and sent with others, in random order.

Private swaps Live on devnet

Swap
inside
the pool.

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

Hard to
pick out.

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.

  • Standard amounts

    Deposits and withdrawals default to amounts many others use.

    0.10.51510SOL
    10501005001,000USDC
  • Odd amounts leave in parts

    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.

  • Delayed by default

    "Next wave or later" is the default. "Now" is one tap, labelled less private: sent alone, right away.

  • Same wallet? A warning.

    Withdrawing to the wallet you deposited from gets a plain warning and needs a second press.

Your choice of servers Built

Who sees
what.

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.

Relayer
RPC
Run by this site

This site

  • The app's files, so your IP address when you open it.
  • Your wallet's address when you deposit (the deposit check).
  • Names or numbers you look up.
  • Your address sending spends: it runs the relayer.
  • Your address reading the pool: it runs the chain reader.
Run by this site

The relayer

  • Your IP address and when you spend.
  • What goes on chain anyway.
  • Not whose notes you spend.
Run by this site

The chain reader

  • Your IP address reading the pool's transactions.
  • Not which notes are yours.
Everyone

The public chain

  • Deposits: your wallet and the amount.
  • Withdrawals: the address and the amount.
  • Swaps: the amounts.
  • Not who spends.

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

What our
server
knows.

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 page

Can't see

  • Who sent a private payment to whom
  • How much was sent
  • Your balance and your history
  • Your keys
  • It can delay a payment or refuse it. It can't send it somewhere else.

Can see

  • What is public on Solana: deposits, withdrawals, and that a private payment happened
  • What your device asks it: your IP address and the time, the wallet you deposit from, who you look up
  • What you chose to publish: a private receiving address, a @name, a linked phone number
  • More where you let it help: the offline allowance, texts, and the Emergency lane

Trust

Checked,
and honest
about the rest.

Three AI audit passes

  1. 1Seven AI auditors on the whole system
  2. 2Five on the merged code
  3. 3Two checking that the fixes are real

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.

The emergency exit Built

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.

Screening that can't freeze Built

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.

Still to come Coming

  • The public setup ceremony: not run yet; today's setup is a local test one.
  • Upgrades behind a multisig with a 72-hour delay: tooling rehearsed, not on chain yet.
  • Open code with a verified build: prepared, not published yet.
  • An outside professional audit: not done yet.
  • Coming

    Cross-chain exits

    Built and tested against a stand-in for the providers. Not switched on yet.

  • Coming

    Android app

    Sends payment texts itself. An early build exists; it is not released.

  • Coming

    Live SMS number

    Today texts stay in a local test outbox.

  • Coming

    Mainnet

    Not yet. Today this is a devnet beta with test money.

Beta on Solana devnet · test money

Enter

Launch App