Routing & Leak Score
Whatever cannot be crossed in the dark is executed against public liquidity — Uniswap v2, v3, and v4 on Robinhood Chain. The routing engine's job is to make that public leg reveal as little as possible, and the Leak Score's job is to tell you exactly how much it still reveals.
Fallback routing
| Technique | What it does |
|---|---|
| Split | Breaks the remainder into pieces of randomized size. |
| Timing jitter | Dispatches pieces at randomized intervals so they don't cluster into one recognizable print. |
| One-time addresses | Each piece is submitted by a relayer from a fresh address with no prior history. |
| Re-shield | Proceeds are returned to new notes automatically; output never sits in a traceable wallet. |
Leak Score
Before signing, you see a Leak Score for the proposed execution. It is derived from:
- the share that crosses internally versus routes publicly,
- the number and size distribution of public pieces, and
- the freshness of the addresses used.
The slider
A single control moves you between two ends:
- Best price — more public routing, tighter execution, higher leak.
- Least exposure — more patient crossing, more fragmentation, lower leak.
The choice is explicit and made by you, not by the protocol.
Honesty about the residual
Intelena does not reduce the visibility of the public leg to zero; it minimizes and fragments it. The Leak Score exists precisely so that residual exposure is measured and chosen, never hidden.