Skip to content

docs(node): add Rex5 to validator hardfork schedule and hooks #55

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Troublor merged 2 commits into from
Jun 16, 2026
Merged

docs(node): add Rex5 to validator hardfork schedule and hooks #55

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
45cef16
docs(node): add Rex5 to validator hardfork schedule and pre-execution…
Troublor Jun 16, 2026
bec890c
docs(node): split Rex5 bullet to one sentence per line
Troublor Jun 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions docs/node/validator-architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,10 +41,10 @@ For the file layout (not a runtime artifact), see the schema-shaped sample at [`

Despite the file carrying the full Genesis schema (allocations, gas limit, timestamp, base fee, ...), the validator consumes only two pieces of state from it:

| Derived value | Source in `config` | Use during validation |
| ----------------- | ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Chain ID | `chainId` | Drives the EVM `CHAINID` opcode and EIP-155 transaction-signature checks. |
| Hardfork schedule | `<fork>Block` and `<fork>Time` fields | Activates Ethereum (Cancun, Shanghai, ...), OP-Stack (Ecotone, Granite, Holocene, Isthmus, ...), and MegaETH (MiniRex, MiniRex1, MiniRex2, Rex, Rex1, Rex2, Rex3, Rex4) at their pre-declared block numbers or timestamps. |
| Derived value | Source in `config` | Use during validation |
| ----------------- | ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Chain ID | `chainId` | Drives the EVM `CHAINID` opcode and EIP-155 transaction-signature checks. |
| Hardfork schedule | `<fork>Block` and `<fork>Time` fields | Activates Ethereum (Cancun, Shanghai, ...), OP-Stack (Ecotone, Granite, Holocene, Isthmus, ...), and MegaETH (MiniRex, MiniRex1, MiniRex2, Rex, Rex1, Rex2, Rex3, Rex4, Rex5) at their pre-declared block numbers or timestamps. |

The genesis `alloc`, `gasLimit`, `baseFeePerGas`, and other initial-state fields are **not** consumed — once the chain has produced a single block, initial state is served by the witness, not by the genesis file.

Expand Down Expand Up @@ -190,6 +190,8 @@ Two layers run in order:
- **MiniRex** — deploy the oracle contract and the high-precision timestamp oracle contract.
- **Rex2** — deploy the keyless-deploy contract.
- **Rex4** — deploy the access-control contract and the `MegaLimitControl` contract.
- **Rex5** — deploy the `SequencerRegistry` contract (`0x6342000000000000000000000000000000000006`) and upgrade the oracle to its dynamic-authority version.
When a scheduled system-address or sequencer change is due, an additional pre-block system call to `applyPendingChanges()` is executed.
- **MiniRex1, MiniRex2, Rex, Rex1, Rex3** — no new system-contract deployments.
The fork still gates EVM behavior changes; the pre-execution hook list is just empty.

Expand Down
Loading