Open-source privacy protocol

Privacy at the level you need.

Galeon keeps payments on public blockchains private with stealth addresses, privacy pools, and zero-knowledge proofs. Use only what you need.

On a public chain

One address. Your whole history.

Anyone who pays you, or gets paid by you, can read every payment you have ever made.

How it works

Three levels of privacy.

Start with the first level. Add the other two when you need them.

  1. Hidden in plain sight

    One-⁠time addresses · EIP-⁠5564

    one Port link0x4f2c…91a00xb81e…07d30x2a9d…e5c4youpayersone-time addresses

    Each payment lands at its own one-⁠time address.

    A Port is a payment link you share. Every payment through it gets a fresh address that only your keys can spend from. The Port itself is public, with the wallet that created it, so create it from a wallet that does not name you. Payers use the wallet they already have.

  2. Out of reach

    Approval-⁠gated pool · Privacy Pools model

    proofapproved setshared pool

    Funds pass through an approval-⁠gated pool, and the chain stops showing which deposit paid which withdrawal.

    Only money that came through a Port can enter. Your browser proves your deposit is in the approved set without saying which one, and the contract checks that proof on-⁠chain. Who approves deposits is up to whoever runs it: the reference deployment approves every one.

  3. Yours to tell

    Selective disclosure · PDF reports

    ReportJan to Mar 2026Port: alldateamountfromsent by youauditor

    When someone needs the record, you choose what they see.

    Make a report for a period, for one Port or all of them, and send it yourself. Nothing is published.

Privacy is a right. Compliance is a responsibility.

So the pool asks for both. A withdrawal can stay private only if its deposit was approved.

Who sees what

It depends on who is looking.

What each party can learn, including whoever runs Galeon.

WhoSeesDoes not see

Anyone reading the chain

Each payment, its Port and the wallet that created the Port. Every pool deposit and withdrawal.

Which deposit paid which withdrawal, though a small pool can still hint.

Whoever pays you

What they paid, and the Port's other payments.

Your keys, or where funds go after a private withdrawal.

Whoever runs Galeon

Payments to the Ports whose viewing keys it holds, and which of your deposits became which withdrawals.

Your spending keys, so its viewing keys alone cannot spend.

An auditor you choose

The report you hand over.

Anything else the chain does not already show.

Holds by design

  • Spending keys stay on your device
  • Proofs are verified on-⁠chain
  • Only money that came through a Port enters the pool
  • Any deposit can be taken back, in public
  • Open source: MIT, Apache-⁠2.0 and GPL-⁠3.0

Set by whoever runs it

  • Who holds viewing keys
  • Screening: the reference deployment approves every deposit
  • Which relayers send withdrawals
  • Who runs the proving setup
  • Who can upgrade or pause the contracts

The first list holds while the contracts run as deployed: whoever can upgrade them can change it.

Trust model and known limitations (opens in a new tab)

Who it is for

For anyone on the receiving end.

  • Programmes

    Aid and cash-⁠transfer programmes that pay people on a public chain, without each payment landing in a wallet that names the person.

  • Organisations

    Teams that pay staff or suppliers on a public chain, without every payment landing in someone's everyday wallet.

  • People

    Anyone paid on a public chain who would rather their payments did not pile up in one wallet anyone can read.

Developers can read and fork the contracts and the stealth address library on GitHub.

Yours to tell.

If you pay people on a public chain, write to us. We would like to run Galeon with you, under your own policy.