ZecBus STATION

Zcash pool departures

--:--:--

Non-custodial mixing rendezvous. Cross a pool boundary alongside others at the same blend-in amount & short window — so on-chain you're one of many look-alike moves, not a lone fingerprint. How it works →

Destination Blend-in Seats Status Action

Reading the board…

● Boarding ● Ready ○ Scheduled — be the first

Pick what you're doing and a round blend-in amount. You get a one-time seat token — no account, nothing stored about you.

    Have a seat token from before?

    Why blend in?

    A shielded hop only buys privacy if your amount doesn't fingerprint you. People routinely shield an odd amount and then unshield a near-identical amount days later — a self-defeating round-trip that lets an observer link the transparent endpoints straight across the pool. zecstats.com's Wall of Shame ↗ catalogues hundreds of these real self-dox round-trips.

    A bus fixes the amount side: everyone leaves with the same round denomination, so your exit is one of N identical swaps instead of a unique tell. For picking safe amounts and seeing your cover, the zecstats tools are excellent — Privacy Suggestions ↗ and the Orchard anonymity set ↗.

    ZecBus's blend-in amounts were inspired by zecstats's amount-suggest — half its idea, honestly, so: hat tip and a link back to zecstats.com ↗.

    What this does — and doesn't — do

      How it works

      1. 1

        Pick a service & blend-in amount

        Choose swap out (ZEC→BTC, ETH, RUNE…), unshield (z→t) or shield (t→z), plus a common denomination others also use. Odd amounts fingerprint you — ride a round one.

      2. 2

        Reserve a seat

        You join, or start, a bus for that exact amount + route. ZecBus hands you a one-time seat token. No account, no email, nothing stored about you.

      3. 3

        Wait for it to fill

        When enough riders board, the bus turns ready and a short departure window opens.

      4. 4

        Broadcast your own move

        During the window, everyone broadcasts their own swap, unshield or shield from their own wallet, to a fresh destination. N identical moves land together — one anonymity set.

      No funds, keys or destinations ever touch ZecBus — it only matches amount, route and timing, and you broadcast your own move. For the full design — including the anonymous anti-sybil proofs that stop one actor hogging a bus — read the write-up on GitHub ↗.

      For agents (MCP)

      ZecBus is also a set of Model Context Protocol tools on the winbit32 gateway, so an AI agent can ride a bus on your behalf. Point your client at:

      e.g. zec_bus_join({ to: "BTC.BTC", amount: 1, minPassengers: 5 }) to swap out, or zec_bus_join({ kind: "unshield", amount: 1 }) to deshield with a crowd. Same free REST surface: GET /v1/zec/bus?kind=unshield.

      Agents can auto-discover ZecBus via its Gopher-over-HTTPS card (/.well-known/agent.gopher), which cross-links the WINBIT32 wallet and sister projects like Secresea, the privacy NFT marketplace.

      Coming to WINBIT32

      ZecBus is being built into WINBIT32's Privacy Suite and Money Manager. There the bus is wallet-connected: when your bus is ready, one click prefills the built-in Exchange to broadcast your own ZEC exit swap — no copy-pasting amounts, no leaving the app.

      You don't have to wait: when a bus is ready, your ticket has an optional “do it in your browser” button that opens WINBIT32 prefilled, so you can connect your own wallet and broadcast right there (a small affiliate fee applies to swaps). It's entirely optional — broadcasting from your own wallet stays the default, and ZecBus never holds funds or keys either way.

      Anonymous sybil-resistance is built. A Semaphore-style membership / nullifier proof — a scarce per-wallet identity, in-browser proving, and an opt-in coordinator gate that reveals only a per-bus nullifier — stops one actor quietly taking most seats and shrinking everyone's set, without deanonymising anyone or holding keys. It switches on once a multi-party trusted-setup ceremony has run; until then the board stays open and anonymous. How the proofs work ↗