Erebuzdocs

Routing

How Erebuz picks a lane, one call, three lanes, settled on-chain.

When your app calls findRoute(), Erebuz evaluates the available privacy lanes between the source and destination and picks the one with the best combination of anonymity set, cost and settlement time.

The three lanes

Every transfer moves through three stages:

  1. Shield: value enters a shared privacy pool on the source chain. Because the pool is shared across all Erebuz integrations, the anonymity set is large, your users are not fingerprintable as "users of your app".
  2. Screen: before anything moves, the transfer is screened for compliance. Non-compliant value never enters the pool. See Compliance.
  3. Settle: the value exits the pool on the destination chain to the recipient, typically in seconds.

What a route quote contains

const route = await erebuz.findRoute({
  from: { chain: "base", token: "USDC" },
  to: { chain: "arbitrum", address: recipient },
  amount: "100.00",
});
FieldExampleMeaning
receives99.58Amount delivered after fees
fee$0.42, coveredNetwork fee, Erebuz covers gas on the destination
compliance98Compliance score for this route (0-100)
settlesIn2sExpected settlement time

Gas handling

Recipients don't need gas on the destination chain. Fees are taken from the transferred amount and destination gas is covered by the router, so a fresh address can receive funds with zero setup.

On this page