Layer 4 - Rug detector
Don't get rugged on the way out. Mempool surveillance with dual websockets, twenty two patterns across three tiers. Critical-tier matches auto sell before the rug confirms.
The frame
Most rug protection is post hoc. X alerts, telegram pings, dashboards. By the time a human reads any of it, the position is zero. The rug detector runs at the mempool layer and the only metric that matters is whether the auto sell lands in the same block as the rug attempt. It does.
Dale will sell your bag before the rug confirms. That is the entire pitch.
Three tiers
Why two websockets
One websocket is a single point of failure. Two independent websockets, on independent infrastructure, give us redundancy at the latency layer. If the primary lags, the secondary fires. The cost is paying for two. The benefit is a system that does not blink when the primary node operator does.
The twenty two patterns
Liquidity removal. Ownership transfers to dead. Mint function activated. Tax flipped above threshold. Trading paused. Whitelist edited. Twenty two in total, classified into Watch / Alert / Execute. Specifics live under NDA.
Confirmed working on real rug events. Receipts available on request. The kill log on the home page is a live feed of events the rug detector has acted on.