Skip to content

Move & rename MONAD_NEXT to MONAD_NINE#13

Merged
pdobacz merged 2 commits intoforks/monad_ninefrom
rename-monad-nine
Mar 3, 2026
Merged

Move & rename MONAD_NEXT to MONAD_NINE#13
pdobacz merged 2 commits intoforks/monad_ninefrom
rename-monad-nine

Conversation

@pdobacz
Copy link
Collaborator

@pdobacz pdobacz commented Mar 3, 2026

Rename to match category-labs/monad#2112

@pdobacz pdobacz requested review from QEDK and mijovic March 3, 2026 13:42
@greptile-apps
Copy link

greptile-apps bot commented Mar 3, 2026

Greptile Summary

This PR performs a mechanical rename of the MONAD_NEXT fork to MONAD_NINE across the entire codebase (60 files), moving the fork module from src/ethereum/forks/monad_next/ to src/ethereum/forks/monad_nine/ to align with the upstream monad repository (category-labs/monad#2112). The change is purely a rename — no logic, behaviour, or fork criteria are modified.

Key changes:

  • Renamed the monad_next Python package directory to monad_nine (module files moved via git rename)
  • Updated all MONAD_NEXT class/identifier references to MONAD_NINE across testing harness, spec tools, and tests
  • Updated EXCEPTION_MAPS, CI fill-params, and README documentation to use the new name
  • No remaining references to monad_next or MONAD_NEXT found in the codebase

Issue found:

  • The docstring on MONAD_EIGHTToMONAD_NINEAtTime15k in transition.py still reads "Prague to MONAD_NINE transition" — it should say "MONAD_EIGHT to MONAD_NINE transition". This was a pre-existing inaccuracy carried forward from the old name.

Confidence Score: 5/5

  • This PR is safe to merge — it is a purely mechanical rename with no logic changes and the rename is complete across all 60 files. One minor docstring inaccuracy was found but does not affect functionality.
  • All occurrences of MONAD_NEXT/monad_next have been replaced with MONAD_NINE/monad_nine. No functional code paths, fork criteria, or test assertions were altered. The single issue found is a pre-existing docstring inaccuracy ("Prague to MONAD_NINE" should be "MONAD_EIGHT to MONAD_NINE") that was carried forward during the rename. This is easily fixable and does not impact the mechanical correctness of the rename itself.
  • packages/testing/src/execution_testing/forks/forks/transition.py (minor docstring fix at line 67).

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    EIGHT[MONAD_EIGHT]
    NINE[MONAD_NINE]
    TRANS[MONAD_EIGHTToMONAD_NINEAtTime15k\ntransition fork @ ts=15000]

    EIGHT -->|inherits| TRANS
    TRANS -->|transitions to| NINE

    subgraph "Fill Range"
        EIGHT -.->|--from| FILL[fill params]
        NINE -.->|--until| FILL
    end

    subgraph "Renamed in this PR"
        OLD["monad_next / MONAD_NEXT"] -. "→" .-> NINE
    end
Loading

Last reviewed commit: ec44a13

Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

60 files reviewed, 1 comment

Edit Code Review Agent Settings | Greptile

Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Copy link
Member

@QEDK QEDK left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@pdobacz pdobacz merged commit 1e5e727 into forks/monad_nine Mar 3, 2026
4 checks passed
@pdobacz pdobacz deleted the rename-monad-nine branch March 3, 2026 18:28
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.

2 participants