Skip to content

chore(consume): Run the eest-runner on the page-only monad runloop - #68

Open
pdobacz wants to merge 2 commits into
forks/monad_ninefrom
eestnet/page-only-runloop
Open

pdobacz wants to merge 2 commits into
forks/monad_ninefrom
eestnet/page-only-runloop

Conversation

@pdobacz

@pdobacz pdobacz commented Oct 20, 2026 •

Copy link
Copy Markdown
Collaborator

Bump monad-bft and monad to upstream; the runloop executes only from MONAD_TEN on.

This follows monad dependency not supporting slot-based DB anymore.

RetriggerView in GreptileConfidence Score: 5/5

The PR appears safe to merge; no new actionable issues were found.

Summary

Updates the runloop stack to page-only storage and limits execution to MONAD_TEN onward.

  • The Monad runloop uses one page-encoded database for supported fixtures.
  • Storage performance runs compare MONAD_TEN with MONAD_ELEVEN.
  • The runner uses the updated upstream stack without leaving core dumps.

Review used code inspection; no runtime tests were run.

Reviews (2) · Last reviewed commit: "compare MONAD_TEN with MONAD_ELEVEN in t..." · Reviewed by Greptile

Bump monad-bft and monad to upstream; the runloop executes only from MONAD_TEN on.

Co-Authored-By: Claude Opus 5.5
@pdobacz
pdobacz requested review from QEDK and mijovic as code owners October 20, 2026 10:27
Comment thread .github/configs/feature.yaml
Comment thread MONAD_RUNLOOP_TESTING.md
The runloop no longer executes MONAD_NINE, so the perf cycle pairs the two page-encoded forks.

Co-Authored-By: Claude Opus 5.5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant