Sigillo How it works Verify a disclosure Launch app→
Application-layer private transfers

Send ETH without publishing who you are

Pay privately from the wallet you already have, and prove a single transfer to a single person when you need to.

What the chain shows real tx 0x013a…c722 ↗
From
0x6938…ab49 relayer
To
0xbbac…9b01 pool
Value
0 ETH
Sender
not in the data
Recipient
not in the data
Amount
encrypted
What you see in the app · example
Sent privately
0.1 ETH
to 0x71c2…9e04
Prove it to one person Issue receipt →

Prove one transfer, to one person

Hand an accountant or an exchange a receipt or a disclosure key. They check it on the verify page — no wallet, no account. Nobody else learns anything.

Your keys stay in your wallet

Everything derives from one signature, and proofs are built on your device. This site holds nothing to steal.

A relayer you do not have to trust

It submits the transaction so your address is not the sender. It cannot take or redirect money, and your browser recomputes its fee.

Recipients need nothing

Pay a one-time stealth address from their public receive code, or any wallet by public withdrawal. No account, no gas, no setup on their side.

Private transfers

Neither your address nor the recipient's appears in the public data of the transfer, and neither does the amount.

Records written into Ethereum

Encrypted disclosure records go into L1 calldata via Facet — readable by whoever holds the key, editable by no one, us included.

No custody. No admin keys on the pool. No chain of our own. Proofs built in your browser. The pool is the reference deployment of the application-layer private transfer ERC draft — immutable, ownerless, and not ours. We cannot pause it, upgrade it, or move what is in it. What it is built on →

Sepolia testnet only· Not independently audited· A small crowd so far What it does not do yet →