Ethereum Learning

Ethereum Mastery Map · Sun, Aug 23, 2026

Briefs
1
Lessons
3
Streak
1d
Map
3/74
News brief

What happened

Everything in Ethereum since the last brief — calls, EIPs, devnets, incidents — and why it matters.

2026-08-23 · today Glamsterdam Ran in Public, and Lost Finality on Day One

A news brief for 2026-08-23 already exists.

Next one
~/code/ethereum-learning/lesson news
Topic lesson

What to learn

Next up: The Roadmap Frame — never covered; priority 1; foundation; moves with the roadmap

2026-08-23 · today How the EVM Runs Code

A topic lesson for 2026-08-23 already exists.

Next one
~/code/ethereum-learning/lesson topic

The map

new intro working deep stale
ETH mastery Protocol 1/8 · 4% Scaling 0/8 EVM 1/9 · 4% Contracts 0/10 Security 0/8 Accounts 1/6 · 6% Crypto 0/7 Apps 0/6 Governance 0/6 Roadmap 0/6 Proof of Stake MechanicsFork Choice & ReorgsValidator LifecycleSingle Slot FinalityProposer-Builder SeparationCensorship ResistanceIssuance & Staking EconomicsClients & Diversity RiskRollup ModelsBlobs & the Blob Fee MarketPeerDAS & Data Availability SamplingBlob Parameter ScheduleL2 InteroperabilityBased Rollups & PreconfirmationsL1 Gas Limit & ThroughputStatelessness & State GrowthEVM FundamentalsGas Metering as PolicyState Access & Creation CostsMultidimensional Gas & Fee MarketsAccess Lists & Block-Level Access ListsEOF and Why It Keeps SlippingPrecompilesSize & Structural LimitsAlternative Execution EnginesModern SolidityStorage Layout & PackingUpgradeability vs ImmutabilityDeterministic DeploymentGas Optimisation That SurvivesFoundry Testing DepthFormal VerificationHard Fork ResilienceToken StandardsOracles & Price FeedsReentrancy & CEIAccess Control & PrivilegeEconomic AttacksSignature SecurityMEV-Aware Contract DesignAudit PracticeIncident ResponseBridge & Cross-Chain TrustThe Post-7702 Account ModelEIP-7702 DelegationERC-4337 StackNative Account AbstractionKeys, Multisig & RecoveryIntents & SolversHashes, Merkle & SSZBLS SignaturesKZG CommitmentsSNARKs & STARKszkEVMs & Real-Time ProvingPost-Quantum MigrationPrivacy TechnologyDeFi PrimitivesStablecoins & PaymentsStaking, LSTs & RestakingThe MEV Supply ChainETH as an AssetNames, Identity & AttestationsThe EIP & ERC ProcessAll Core DevsDevnets, Testnets & Fork TestingEcosystem OrganisationsHard Fork HistoryContributing CrediblyThe Roadmap FrameFusaka — What ShippedGlamsterdam — What Is ComingAfter GlamsterdamLean EthereumEndgame Theses

Branches

  • Protocol & Consensus 1/8
  • Scaling & Data Availability 0/8
  • EVM & Execution Layer 1/9
  • Smart Contract Engineering 0/10
  • Security & Adversarial Thinking 0/8
  • Accounts, AA & Wallets 1/6
  • Cryptography 0/7
  • Applications & Economics 0/6
  • Governance & Process 0/6
  • Roadmap & Horizon 0/6

Queued next

  1. The Roadmap Frame
    new Roadmap & Horizon · moves with the roadmap
  2. Rollup Models
    new Scaling & Data Availability
  3. Modern Solidity
    new Smart Contract Engineering
  4. Reentrancy & CEI
    new Security & Adversarial Thinking
  5. Access Control & Privilege
    new Security & Adversarial Thinking
  6. The EIP & ERC Process
    new Governance & Process

Chosen by priority, staleness, and how well it follows the last lesson. The agent gets this same list and can override it.

Change the curriculum

Describe what you want changed — a topic added, split, reprioritised, dropped. Copy the command, paste it in a terminal.

3 changes so far
  • 2026-08-23 update deterministic-deploys — Two changes, both from today's reading rather than tidying. (1) The biggest item in the window was a testnet — Platåberget forking to Glamsterdam on 20 August, losing finality on a builder-deposit bug, and ACDC #185 proposing Sepolia 28 Sep and Hoodi 26 Oct off the back of devnet stability. The map has acd-calls for how forks get scoped and fork-history for what past forks changed, but nothing covers the pipeline that decides whether a fork is ready: devnet numbering, public testnets, ACDT, execution-spec-tests and hive, and how a contract engineer actually tests against a fork before it ships. That pipeline is where the reader's third goal — credible participation — is most reachable, and it is where today's news happened. (2) deterministic-deploys was p2 and its summary stops at CREATE2, salt design and EIP-7997. Today EIP-7610 came out of Glamsterdam and EIP-8253 replaced it with a one-time irregular state transition that sets nonce=1 on empty-code/zero-nonce/non-empty-storage accounts, which under EIP-684 makes those addresses permanently undeployable. That is a silent, non-revertible break for counterfactual addresses, and it follows yesterday's finding that pre-signed CREATE2 factory transactions break under the Glamsterdam repricings. Two independent hits in two days on a node whose summary does not mention the collision lineage at all.
  • 2026-08-23 add fork-testing — Two changes, both from today's reading rather than tidying. (1) The biggest item in the window was a testnet — Platåberget forking to Glamsterdam on 20 August, losing finality on a builder-deposit bug, and ACDC #185 proposing Sepolia 28 Sep and Hoodi 26 Oct off the back of devnet stability. The map has acd-calls for how forks get scoped and fork-history for what past forks changed, but nothing covers the pipeline that decides whether a fork is ready: devnet numbering, public testnets, ACDT, execution-spec-tests and hive, and how a contract engineer actually tests against a fork before it ships. That pipeline is where the reader's third goal — credible participation — is most reachable, and it is where today's news happened. (2) deterministic-deploys was p2 and its summary stops at CREATE2, salt design and EIP-7997. Today EIP-7610 came out of Glamsterdam and EIP-8253 replaced it with a one-time irregular state transition that sets nonce=1 on empty-code/zero-nonce/non-empty-storage accounts, which under EIP-684 makes those addresses permanently undeployable. That is a silent, non-revertible break for counterfactual addresses, and it follows yesterday's finding that pre-signed CREATE2 factory transactions break under the Glamsterdam repricings. Two independent hits in two days on a node whose summary does not mention the collision lineage at all.
  • 2026-08-17 add multidimensional-gas — EIP-8037 does not just reprice state — it makes gas two-dimensional, with separate block counters, block validity as max(execution_used, state_used), and the bottleneck dimension driving the base fee. EIP-8075 would go further and give state its own EIP-4844-style adaptive fee market. The map has gas-metering for repricing-as-policy, state-gas-costs for the specific Glamsterdam constants, and blobs for the blob fee market, but nothing covers the architectural question of multiple gas dimensions and how base fees and gas estimation behave across them. Today's lesson deliberately left that as an open question because there was no node to send it to.

Everything written