Run the settlement rail for private order flow.
You can't front-run — that's the feature.
You don't see amounts. You don't sandwich. You don't get gated. You earn deterministic on-chain bps per fill, fund the protocol treasury at the rate governance set, and exit with your bond after the registry's cool-down.
Demo flows below use mock data. Connect a wallet on /register to bond on-chain.
Who runs a relayer?
You're a fit if any of these matches.
The settlement tx is cheap; the operating cost is the node and the gas float. Relayer fee turns that float into a recurring revenue line — not block-lottery MEV income.
Operating your own relayer means the bps your clients pay comes back to you, not to a third party. Your orderbook is your moat — Scatter is the on-chain settlement rail underneath it.
zk-X509 IdentityGate verifies users and operators against registered CAs. Sanctions checks are on-chain. You operate a privacy network that's also defensible in front of a regulator. Specific CA integrations ship as governance approves them.
The deal: what you don't do
Scatter relayers aren't searchers. The protocol pays you bps in exchange for these constraints — and that constraint set is exactly why privacy-seeking flow trusts the rail.
Order payloads are zk-encrypted before they reach you. The settlement contract verifies the proof — you can't reorder for MEV because you don't know what you're reordering.
Your URL and fee are your on-chain config. You change either with one tx. Exit the registry and after the exit cool-down your bond returns — no foundation handshake to leave.
The protocol skims a configurable platform fee on relayer claims (capped at 50% by contract; default sub-10% via governance). You always know what you net, and the cap means it can't surprise you.
How operating works
Three steps to a live, paying relayer.
Post a bond to the RelayerRegistry contract and publish your endpoint URL plus per-trade fee in basis points.
Spin up the open-source relayer (Docker / single binary). It accepts signed orders, batches them, and submits settlement transactions.
Each settled order pays your fee directly to your operator address. Withdraw any time; exit the registry to recover your bond after the cool-down.
Why operate on Scatter
Other private trading networks gate operator slots, require proprietary hardware, or hide the take-rate. Scatter is open and contract-priced — the platform fee that funds the protocol treasury is on-chain and configurable by governance.
| Property | Closed networks | Generic MEV stack | Scatter |
|---|---|---|---|
| Permissionless registration | — | — | ✓ |
| Bond-secured slashing protections | — | — | ✓ |
| On-chain, capped platform fee (no opaque take-rate) | — | — | ✓ |
| Open-source node binary | — | ✓ | ✓ |
| Per-trade fee published on-chain | — | — | ✓ |
Operator economics
Indicative numbers from the testnet pilot. Production parameters set by governance.
Run the node
The relayer node is open-source. Single Docker image, single config file.
docker run -d \ --name scatter-relayer \ -p 8080:8080 \ -e RPC_URL=$RPC_URL \ -e OPERATOR_KEY=$OPERATOR_KEY \ -e REGISTRY_ADDR=$REGISTRY_ADDR \ ghcr.io/tokamak-network/scatter-relayer:latest
Health probe: GET /api/info. Submission endpoint: POST /api/orders.
- · Hardware: 2 vCPU, 4 GB RAM, 50 GB SSD
- · Trusted RPC with archive support recommended
- · HTTPS termination required for registration
- · Prometheus metrics at
/metrics - · Logs to stdout, structured JSON
Ready to operate?
Walk through the registration flow with mock data, then connect a wallet when you're ready to bond on-chain.