Dark Crossing
The dark crossing engine matches encrypted orders against each other so that a trade never has to touch a public pool.
How it works
- Encrypt. A swap begins as an encrypted intent: asset in, asset out, size, and limit constraints, encrypted to the crossing engine.
- Rest. The intent joins a book of shielded orders. No participant — including other traders — can read it.
- Match. Opposite intents cross at the oracle midpoint, the mid-price of the referenced oracle feed at the time of crossing.
- Settle. A match is a note-for-note exchange inside the shielded pool. No public swap occurs.
Why the midpoint
Because both sides are matched at the mid-price, neither pays spread or price impact. Execution quality on the crossed portion is not a function of pool depth.
Partial fills
Crossing is opportunistic: it fills what it can. Any unmatched remainder is handed to the routing engine for a fragmented public leg.
What is visible
| Public pool swap | Dark cross | |
|---|---|---|
| Size | Visible | Hidden |
| Price | Visible | Hidden (midpoint) |
| Counterparty | Visible | Hidden |
| Mempool exposure | Yes | None |
Trust note
The oracle determines the midpoint. Oracle manipulation would affect the crossing price for a pair; it cannot affect custody of funds. See Threat model.