Erebus

Alpha · Robinhood Chain testnet

Erebus

Privacy at the network layer for tokenized finance. Erebus hides who you are, what you trade, and how you pay, so no observer can link any of it back to you.

What Erebus does

01
01

Hides your address

Your real network address never touches the chain.

Every packet is onion-encrypted for three independent mix nodes. Each hop peels one layer, holds the packet for a random delay, and forwards something no observer can match to what arrived.

02

Pays without a trace

Cover the relay fee without revealing who is paying.

A zero-knowledge proof shows a valid note is being spent, not whose note it is. Fees settle out of a shielded pool, so nothing on-chain links the payment back to a funding address.

03

Routes every request

Trades, RPC calls, and balance reads all take the same path.

Nothing leaves the client unmixed. Services answer through single-use reply blocks, so a venue or provider can respond to you without ever learning where you are.

How mixing works

02

Continuous
Poisson mixing

Each packet enters a delay queue at every hop and leaves after an independent exponential wait. Output order carries no information about input order, so an adversary watching every link still cannot pair what went in with what came out. Real traffic, loop probes, and drop cover are indistinguishable on the wire.

  • 3-hop stratified topology
  • Fixed 32 KB packets
  • Exponential delay per hop
  • Loop-probe cover traffic

Use cases

03

Primary application

Trade tokenized stocks without publishing your book

A stock token is an ERC-20, so every buy, sell, and holding size sits in public state next to an address that also holds your payroll deposits. Erebus keeps the position in a shielded pool: the client builds a proof locally, the mixnet carries it, and an exit node lands it on Robinhood Chain. The venue settles the trade without learning who took it.

State model
ZK-UTXO commitment tree (depth 32)
Operations
Deposit, withdraw, transfer, swap
Fee payment
Shielded; payer identity hidden
Venue access
Adaptor contracts per DEX/AMM
Execution
Atomic verify + execute on-chain

Network

04

Three layers of independent mix nodes, one drawn from each per path

Clients build Sphinx packets locally and route them through the entry, relay, and exit layers. Nodes are discovered from an on-chain registry where operators stake and publish their keys. Layer assignment is deterministic, so every client derives the same topology with no coordination and no directory server to trust.

Network status — no public fleet is running yet, and why.

ENTRYRELAYEXITYOUCHAIN

Discovery

On-chain registry

Sybil resistance

Operator stake + slashing

Path selection

Client-side, per request