# Network Upgrades

- [Overview](https://docs.megaeth.com/spec/network-upgrades/overview.md): MegaETH network upgrade history — hardfork timeline from MiniRex through Rex5 with activation dates and behavioral deltas.
- [MiniRex](https://docs.megaeth.com/spec/network-upgrades/minirex.md): MiniRex network upgrade — the foundational MegaEVM spec built on Optimism Isthmus (Ethereum Prague).
- [Rex](https://docs.megaeth.com/spec/network-upgrades/rex.md): Rex network upgrade — revised storage gas economics, 39K intrinsic storage gas, and state growth tracking.
- [Rex1](https://docs.megaeth.com/spec/network-upgrades/rex1.md): Rex1 network upgrade — patch release fixing cross-transaction gas detention state leak.
- [Rex2](https://docs.megaeth.com/spec/network-upgrades/rex2.md): Rex2 network upgrade — SELFDESTRUCT restored with EIP-6780, KeylessDeploy system contract added.
- [Rex3](https://docs.megaeth.com/spec/network-upgrades/rex3.md): Rex3 network upgrade — oracle detention revised to SLOAD-based triggering with 20M cap.
- [Rex4](https://docs.megaeth.com/spec/network-upgrades/rex4.md): Rex4 network upgrade — per-call-frame resource budgets, relative gas detention, storage gas stipend, and new system contracts.
- [Rex5](https://docs.megaeth.com/spec/network-upgrades/rex5.md): Rex5 network upgrade — SequencerRegistry with dual roles, dynamic system address, Oracle v2.0.0, KeylessDeploy trailing-bytes rejection, caller-account update deduplication, and CALLCODE new-account s


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.megaeth.com/spec/network-upgrades.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.