Doc Updates

This page tracks what changed in the documentation with each update. Newest entries first. Check back regularly — the docs evolve alongside the implementation, often on a daily basis.

---

March 17, 2026 (Update 2)

EVM & VM vertical integration — the "Simple Transaction" flow works end-to-end.

• EVM Integration — completely rewritten journal entry documenting the full vertical integration: FrameTransactionContext, four new opcodes, frame execution loop, default code for EOAs, and 6 running examples
• Spec Feedback: New Findings — three new findings: accessList assumption in typed transactions, default code as non-EVM execution, dual APPROVE implementation requirement
• Code changes: frameContext.ts in EVM, opcode handlers (functions.ts, gas.ts, codes.ts), runFrameTx.ts in VM, runTx.ts modifications for frame tx handling, 14 new tests (12 EVM + 2 VM), 6 new examples (3 EVM + 3 VM)

---

March 17, 2026 (Update 1)

First implementation day — FrameEIP8141Tx scaffolded in @ethereumjs/tx.

• Transaction Parsing — new journal entry documenting the full tx type scaffolding, the TransactionInterface friction story, computed gas limit, and signature hash VERIFY data elision
• Spec Feedback: Transaction Structure — new finding on how Frame TX breaks all base transaction assumptions and the practical implications for implementers
• Code changes: EIP-8141 Common activation, tx params, FrameEIP8141Tx class with constructors, capabilities, factory integration, 39 tests (all passing), and example

---

March 17, 2026

Initial public release — the documentation goes live at eip-8141-docs.feelyourprotocol.org.

What's in this first release:

• Spec Overview — full structured walkthrough of EIP-8141 covering transaction structure, frame modes, all four new opcodes, execution behavior, gas accounting, and EOA default code
• Spec Chronology — detailed history of how the spec evolved from initial publication (Jan 29) through the APPROVE relaxation, EOA support addition, approval bits, and community debates — with commit links and forum references
• Implementation Journal — first entries covering initial impressions, scoping, and planned approach for transaction parsing and EVM integration
• Design Decisions — framework for documenting architecture choices and trade-offs as the implementation progresses
• Spec Feedback — initial assessment covering clarity/completeness issues, protocol alignment analysis (EIP-2718, 1559, 4844, 7702, 2929, 1153), and strategic fit evaluation (PQ security, AA, UX, decentralization)
• About — project context, audience guide, EIP version reference, and the AI experiment disclaimer