Erebuz
Privacy router for payments. Best pool, compliance, and bridge in one SDK call. No custom crypto.
Demo
About
Erebuz is a privacy router for payments. Any app or wallet plugs in with about 10 lines of code and gets private, compliant transactions without building any crypto themselves. One SDK call finds the best privacy pool, runs a compliance check, and bridges funds to any chain. Right now the router supports two privacy options: our own pool, deployed natively on Arc, and Railgun's pool, which has stronger anonymity today simply because it has more volume. The router isn't locked into one tool, it picks whichever fits the transaction based on fees, speed, and privacy strength. For bridging, we use Circle's CCTP to move USDC natively across chains, no wrapped assets, no added bridge risk. Our demo shows a real use case: privately topping up a payment card. A user holds USDC on Arc testnet, wants to fund a card that settles on Base Sepolia. Erebuz shields the transfer, routes it through our pool, bridges it via CCTP, and it lands clean, with no way to trace the deposit back through the user's full transaction history. The bigger idea: privacy shouldn't be something every app builds from scratch. It should be a route any app can plug into.
How it's made
Erebuz is built as an SDK plus a routing engine. The app calls one function, findRoute(), and the SDK handles everything underneath: comparing privacy pools, running a compliance check, and picking the best bridge for the destination chain. For this build, we deployed our own privacy pool as a smart contract on Arc, so the router has a real, live option beyond just wrapping an existing privacy protocol. Alongside that, we integrated Railgun's pool as the second privacy route, since it currently has deeper liquidity and a larger anonymity set from higher transaction volume. The router compares both and picks based on what the transaction actually needs, speed, fees, or privacy strength. For settlement, we used Circle's CCTP to bridge USDC natively between Arc and Base Sepolia. This was a deliberate choice over a typical lock-and-mint bridge, CCTP burns and mints native USDC directly, so there's no wrapped asset sitting in a bridge contract that could leak information or introduce extra risk. The trickiest part was making the router logic pool-agnostic, so adding a new privacy pool later, STRK20, for example, doesn't mean rewriting the routing engine, just registering a new option it can compare against the existing ones.