Frame Transactions (EIP-8141) - #3047
Open
SamWilsn wants to merge 12 commits into
Open
Conversation
gurukamath
force-pushed
the
eips/amsterdam/eip-8141
branch
from
July 21, 2026 13:02
362b750 to
1402c53
Compare
gurukamath
force-pushed
the
eips/amsterdam/eip-8141
branch
from
July 31, 2026 08:11
1402c53 to
2f8aa48
Compare
gurukamath
changed the base branch from
forks/amsterdam
to
eips/amsterdam/eip-8141
July 31, 2026 08:12
Contributor
|
Note to reviewers: The first commit of this PR I have built the frame transaction implementation on top of the re-factor since the changes introduced in the refactor make it much nicer to implement frames. Once PR#3192 gets approved and merged, I will rebase this PR branch. |
gurukamath
marked this pull request as ready for review
July 31, 2026 08:18
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## eips/amsterdam/eip-8141 #3047 +/- ##
===========================================================
- Coverage 93.49% 93.13% -0.37%
===========================================================
Files 624 576 -48
Lines 37056 33246 -3810
Branches 3394 2975 -419
===========================================================
- Hits 34647 30962 -3685
+ Misses 1653 1586 -67
+ Partials 756 698 -58
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
gurukamath
force-pushed
the
eips/amsterdam/eip-8141
branch
from
July 31, 2026 11:13
2f8aa48 to
aef48b6
Compare
Implement the type-6 frame transaction flow on the amsterdam fork, separated from the regular flow from admission onwards: - static validation, signature verification, intrinsic gas, and the two gas anchors (standard_gas_limit, max_gas) in transactions/frame_transaction.py - consensus receipt types (FrameReceipt, FrameTransactionReceipt) and the 0x06 receipt codec arms in blocks.py - TransactionEnvironment split into top_level_context/frame_context in vm/__init__.py - admission through a dedicated check_frame_transaction in frame_processing.py; process_transaction dispatches frame transactions after the chain-id check - frames execute as independent top-level calls in vm/frame_interpreter.py: per-frame gas meters, atomic batches, cross-frame warm journal, default verify code, approval rollback - the six frame opcodes (TXPARAM, FRAMEDATALOAD, FRAMEDATACOPY, FRAMEPARAM, SIGPARAM, APPROVE) in vm/instructions/frame.py - settlement anchored on the standard gas limit with the calldata floor binding through max_gas; the payer refund is max_cost - charged_fee; the frame transaction receipt reports status, gas, and logs per frame Co-authored-by: lightclient <lightclient@protonmail.com>
Co-authored-by: lightclient <lightclient@protonmail.com>
Co-authored-by: lightclient <lightclient@protonmail.com>
gurukamath
force-pushed
the
eips/amsterdam/eip-8141
branch
from
August 4, 2026 14:18
aef48b6 to
fb05113
Compare
Co-authored-by: lightclient <lightclient@protonmail.com>
gurukamath
force-pushed
the
eips/amsterdam/eip-8141
branch
from
August 4, 2026 15:34
fb05113 to
7f4ee85
Compare
SamWilsn
commented
Aug 4, 2026
| VERSIONED_HASH_VERSION_KZG, | ||
| ) | ||
|
|
||
| if U256(tx.nonce) >= U256(U64.MAX_VALUE): |
EIP-8141 aligned the SIGPARAM (0xb4) copy operation's stack order with CALLDATACOPY (ethereum/EIPs 4a9ad32c): after signatureIndex and param the operands are memOffset, dataOffset, length. The implementation still popped them in the old order (length, dataOffset, memOffset) — the reverse of its own FRAMEDATACOPY. Swap to match the live spec.
Frame transaction processing initializes the shared, once-per-tx warm address set with the sender so its first EVM access is charged warm (100) rather than cold (2600). The sender is loaded unconditionally for the nonce check and, like a regular transaction's origin, must start warm per EIP-2929 and EIP-3651.
Contributor
|
Hey I made a couple of fixes, opened PRs: |
fix: correct SIGPARAM copy operand order
gurukamath
force-pushed
the
eips/amsterdam/eip-8141
branch
from
August 6, 2026 12:25
cb6d6cf to
94b7234
Compare
fix: warm the sender for frame transactions
Contributor
Thanks @Marchhill |
kevaundray
reviewed
Aug 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🗒️ Description
My work so far on frame transactions (EIP-8141)
Cute Animal Picture