Shieldbolt
1 sat
…
Lightning ready
…
ZEC ready
…

Spend shielded ZEC anywhere Lightning works.
Get paid over Lightning, straight into the shielded pool.

No transparent addresses on the way through. The Zcash side is a shielded transaction and the Bitcoin side never touches a blockchain, so there is nothing for a chain observer to link.

Used only if the Lightning payment fails. Transparent addresses are refused.

Your swap will appear here, with every step it goes through.

A Lightning address that lands in the shielded pool

Anyone with a Lightning wallet can pay you@this gateway, and it arrives as shielded ZEC. Payer comments ride along as encrypted memos.

@…

Who sees what

Privacy claims should be checkable. This is the full list.

PartyLearnsNever learns
Zcash chain observersThat a shielded transaction happenedSender, recipient, amount, memo, that Lightning was involved
Bitcoin chain observersNothing. Lightning payments are off-chainEverything about the payment
Lightning routing nodesThe amount passing through themWho paid, and who was paid (onion routing)
The payeeThat Shieldbolt's node paid their invoiceYour Zcash address, your wallet, your balance
The lightwalletd serverThat the gateway downloads every blockWhich outputs are the gateway's. It never asks for a transaction by ID
This gatewayThe invoice it pays or issues, the ZEC amount, your refund or payout address, your IP unless you use TorYour other transactions or balance. Linking data is erased 24 hours after a swap finishes

The gateway holds funds for the seconds between the two legs, like any swap service. Amounts are capped to keep that exposure small. Run your own: the code is open source.