Protocol reading challenge set

Identify the rule, its context and the evidence required for a claim.

LET’S PICTURE IT

A careful reader distinguishes a plan, a legal rule and a completed action.

SEE IT FOR YOURSELF

Link blocks, then see what an edit breaksStep 1 / 4

The first toy block records Maya sending Leo three units. A1 is an illustrative fingerprint label, not a real cryptographic digest.

Animated local teaching model. No wallet, RPC or live blockchain data. Some labels and hashes are abbreviated for readability.

Challenge one: decode the envelope

Given a transaction type, identify its specified fields and signing rules. Explain why a legacy v interpretation is not universal.

Challenge two: split the fee

For a stated EIP-1559 execution example, calculate base burn and priority payment. State which additional fee components are outside the example.

Challenge three: evaluate an upgrade claim

An article links an EIP and says the feature is live. Find the missing evidence connecting the proposal to an activated network fork.

Finish with source context

Record the specification version, network and relevant fork. A technically correct rule applied to the wrong context can still produce an incorrect conclusion.

Map the protocol concept

claim → exact specification
→ target network/fork
→ matching implementation or activation evidence
→ narrowly stated conclusion

A conceptual model. Exact fields, limits and processing rules must be checked against the intended network fork.

QUICK CHECK · NO PRESSURE

What should accompany a fork-sensitive protocol claim?

Your progress stays in this browser.

Keep exploring the original referenceethereum.org ↗

Original explanations by EtherTools. Examples are educational and source-linked; this site is independent of the Ethereum Foundation. Our approach.