Insider MEVINSIDER
DOCS/Risk engine

Engine

Risk engine

Anti-rug filters, cluster watch with exit-ahead front-running, and atomic revert protection — enforced by the engine.

CH 062 MIN READENGINE

Speed without guardrails is a liability. Every target clears anti-rug filters before a single unit of capital is committed, enforced by the engine — not as an afterthought, and not as dials you have to manage.

Anti-rug is active, not a checklist

Screening a token once tells you what it looked like a block ago. The engine keeps watching the wallets that matter: it maps the cluster that moves together on a token — deployer, early snipers, funded siblings — and tracks their balances and their pending intent in the mempool.

When a large cluster lines up to dump, the exit is front-run in the same block. The engine sizes the sell against pool depth and the size of their order, then gets out ahead of the impact instead of behind it — the same front-run machinery the engine uses to earn, pointed at protecting the position.

01

Cluster mapping

Wallets that funded each other, minted together, or bought in the same block are grouped as one actor, so a dump split across twenty addresses still reads as one exit.

02

Exit-ahead front-run

Their pending sell is detected in the mempool, the price impact is calculated against live pool depth, and the counter-sell is placed ahead of it in the same block.

03

Anti-rug filters

Honeypots, sell taxes, mint and blacklist authorities, and unlocked liquidity are all screened before entry. Tokens that can be bought but not sold never get a bundle.

04

Liquidity screening

Only assets with real, tradeable DEX depth are targeted. Illiquid and unsellable tokens are filtered out first.

05

Atomic execution

Every MEV bundle is atomic. It clears a profit or it reverts on-chain — the engine simulates first and never submits a bundle that fails simulation.

06

Private relays

Bundles route through private relays, so your intent never sits exposed in the public mempool.

ON RECORD

There is nothing to configure — the engine handles execution. Protection is structural, applied to every bundle it builds, not a set of knobs you have to manage.