What we observed
On May 17, 2026 at 23:29–23:42 UTC our RTT oracle detected a two-wave MEV stress event on Base.
Timeline:
23:29:43 UTC — Base P99 RTT: 52ms → 739ms (14x spike)
23:30:10 UTC — Revert ratio: 0.19 → 0.56
23:39:35 UTC — Peak: 61.36% of all Base transactions reverted
23:41:52 UTC — Full sequencer stall (P99 = 5000ms)
RTT led the revert wave by 27 seconds.
Why it matters for Curve
Curve pools on Base and Arbitrum face MEV sandwich attacks during sequencer stress. During 61% revert events, arb bots dominate the mempool. A 27-second warning allows:
- Temporarily widen A parameter or fees
- Pause admin actions during toxic conditions
- Alert liquidity providers before cascade losses
What we built
Phoenix Zero — RTT oracle, 2-second resolution, Base/Arbitrum/Optimism/ZKSync.
Live: https://phoenix-zero.vercel.app
API: https://rtt.phoenix-ai.work/api/public-feed
— Silicon DNA / Phoenix Zero
What we observed
On May 17, 2026 at 23:29–23:42 UTC our RTT oracle detected a two-wave MEV stress event on Base.
Timeline:
23:29:43 UTC— Base P99 RTT: 52ms → 739ms (14x spike)23:30:10 UTC— Revert ratio: 0.19 → 0.5623:39:35 UTC— Peak: 61.36% of all Base transactions reverted23:41:52 UTC— Full sequencer stall (P99 = 5000ms)RTT led the revert wave by 27 seconds.
Why it matters for Curve
Curve pools on Base and Arbitrum face MEV sandwich attacks during sequencer stress. During 61% revert events, arb bots dominate the mempool. A 27-second warning allows:
What we built
Phoenix Zero — RTT oracle, 2-second resolution, Base/Arbitrum/Optimism/ZKSync.
Live: https://phoenix-zero.vercel.app
API: https://rtt.phoenix-ai.work/api/public-feed
— Silicon DNA / Phoenix Zero