Inputs
- Completed private swap intents.
- Intent input asset, input amount, and chain.
- Privacy settings active at signing time.
- Reference USD price for the input asset.
Back to Vaelun
Methodology
How privacy is enforced
Vaelun estimates MEV savings by comparing a completed private intent against a public execution exposure heuristic. This page documents the calculation, the data we use, and what is never stored server-side.
Heuristic
- Protected private swaps: input USD × 0.35%
- Public or reduced-privacy swaps: input USD × 0.08%
The protected estimate models avoided sandwiching, front-running, and adverse public mempool routing. The reduced-privacy estimate models residual exposure when the route still has solver execution but fewer confidentiality guarantees.
What stays private
- Vaelun does not store transaction contents or balances server-side.
- Position and analytics APIs are read-through views over the private shard.
- Only short-lived cache entries exist where configured.
- Sentry scrubs account IDs, addresses, amounts, transaction hashes, and intent IDs.