meta: tracking v1 release

[MysticRyuujin]

This issue tracks what has to land before we tag v1.0.0, and what we want to finish but will not hold the tag for.

Blocking

eth_simulateV1 after Amsterdam

• #868 Decide what a simulated block looks like after Amsterdam: header field set, blockAccessListHash rules, traceTransfers under EIP-7708.
• #881 Spec PR for the above. Adds slotNumber to Block. Supersedes #806.
• ethereum/go-ethereum#35668 and ethereum/go-ethereum#35617 Reference implementation of #881. Both must merge before the simulate fixtures can be regenerated.

Test chain on Amsterdam

• #867 Bump the test chain from Osaka to Amsterdam and regenerate fixtures. Waits on #881 and the geth PRs.

Block parameter forms

• #859 Allow EIP-1898 block objects in BlockNumberOrTagOrHash. Approved. Closes most of #713.
• #491 eth_estimateGas and eth_createAccessList take BlockNumberOrTag; eth_call takes BlockNumberOrTagOrHash. Clients accept a hash on all three. PR: eth: accept a block hash in eth_estimateGas and eth_createAccessList #889.

Engine API

• #781 / #777 engine_getBlobsV2 result schema lacks the null branch that osaka.md specifies. engine_getBlobsV3 already has it. Approved and green; the osaka.md type labels also need | null.

Should fix before v1

Spec gaps found while surveying clients. None changes the shape of an existing response.

eth methods

• #883 blockOverrides.difficulty and unknown override keys in eth_simulateV1. Six clients, five behaviors.
• #884 Fields whose EIP is not active at the target block. Five of six clients reject them in eth_call; eth_createAccessList before Berlin fails on geth and reth and succeeds elsewhere. Error codes stay with #784.
• #854 / #853 eth_createAccessList with an unfunded sender. Waits on ethereum/go-ethereum#35397.
• #461 eth_call with the block parameter omitted defaults to latest. The schema marks it optional and does not state the default. PR: eth: document block parameter default and post-execution state #888.
• #877 / #874 eth_getHeaderByHash and eth_getHeaderByNumber. Ready for review. Include if merged before the tag.

Engine, live forks

• #548 engine_forkchoiceUpdated does not say whether the EL validates safeBlockHash, whether it must be on the head's chain, or what happens to state on rejection.
• #546 Behavior of V1 engine methods after Shanghai. shanghai.md constrains the CL, not the EL.

Non-blocking

Testing methods

• #857 / #862 testing_buildBlockV1 sends targetGasLimit on Amsterdam. Rebase #862 onto #867 once it merges.

callTracer

• #855 Specify callTracer output and add debug_traceCall. Stacked on #867. Also makes speccheck validate named-tracer results, which today accept anything (ethereum/hive#1588 is the hive side).
• #852 EIP-8037 two-dimensional gas in tracer output and a stateGasTracer. Also waits on #867. Overlaps #855 on CallFrame; reconcile before either merges.

Engine proposals

• #760 Allow zero safeBlockHash and finalizedBlockHash after finalization. A behavior change on the same paris.md lines as #548. The Lighthouse PR that motivated it was closed unmerged.
• #856 Custody bitarray bit ordering. Amsterdam only. Waits on ethereum/EIPs#12054.

Other spec work

• #845 / #847 debug_executionWitness. Fixtures stay speconly until clients implement the canonical witness.
• #817 / #784 / #823 Error codes. eth_simulateV1 keeps its -38xxx codes; the catalog gets cleaned before it is wired into more methods. Resolve the contradiction in #817 in the text before v1. Wider standardization follows in a minor release.

Housekeeping

• Close #806, superseded by #881.
• Merge or close #837 (Amsterdam ToC).
• Close #353, superseded by #758.
• Close #537. unevaluatedProperties is gone from src/.
• Rebase or close #815.
• Close engine PRs already landed or abandoned: #608 (resolved by #796), #769 (landed via #778, #798, #834), #597 (consensus-specs#3972 closed unmerged), #557 (replaced by #885), #302 and #297 (JWT secret handling, inactive since 2023).
• Close answered or abandoned engine issues: #662, #271, #333, #208.
• Close #631 as answered. Deprecated fields are still required from servers.

[MysticRyuujin]

Hey, @mkalinin

Do you think you could take a look at some of the engine PRs and Issues in this tracker and let me know if any of them can be closed or merged or should be removed from the tracker?