OriginProtocol / OriginProtocol/origin-dollar

May 17 Base sequencer stress: 61.4% revert ratio — RTT oracle 27s early warning

Open
#2,899 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Solidity
Stars
152
Forks
115
Avg merge
3d 20h
Merged PRs (30d)
17

Description

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 — where Super OETH operates.

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 timeout)

RTT spike preceded revert wave by 27 seconds.

Why it matters for Origin

Super OETH and OUSD harvest and rebase operations on Base compete in toxic mempool conditions during stall events. A sequencer health gate prevents wasted gas and missed yield windows during MEV storms.

What we built

Phoenix Zero — 2-second RTT oracle across Base, Arbitrum, Optimism, ZKSync.

Live: https://phoenix-zero.vercel.app
API: https://rtt.phoenix-ai.work/api/public-feed

— Silicon DNA / Phoenix Zero

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository files, tests, or implementation entry point. First determine whether the Phoenix Zero feed is intended to become a supported sequencer-health integration, then review the existing Base harvest and rebase paths with maintainers. Done would require an agreed design, integration boundaries, and acceptance criteria before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
blockchain
Domain
blockchain, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.