Skip to content

Update EIP-7069: Move to Review #8659

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eth-bot merged 2 commits into from
Jun 17, 2024
Merged

Update EIP-7069: Move to Review #8659

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
65e4be2
Update eip-7069.md
timbeiko Jun 12, 2024
2985bf0
Update eip-7069.md
timbeiko Jun 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions EIPS/eip-7069.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ title: Revamped CALL instructions
description: Introduce EXTCALL, EXTDELEGATECALL and EXTSTATICCALL with simplified semantics
author: Alex Beregszaszi (@axic), Paweł Bylica (@chfast), Danno Ferrin (@shemnon), Andrei Maiboroda (@gumb0), Charles Cooper (@charles-cooper)
discussions-to: https://ethereum-magicians.org/t/eip-revamped-call-instructions/14432
status: Draft
status: Review
type: Standards Track
category: Core
created: 2023-05-05
Expand Down Expand Up @@ -97,11 +97,11 @@ In case this EIP is included as part of the greater EOF upgrade, execution seman

Execution of `RETURNDATACOPY` which is not in EOF formatted code (i.e. is in legacy code) is not changed.

<!-- *TODO:* Clarify which side (caller/callee) is gas deducted from and where an error originates from. -->
**TODO:** Clarify which side (caller/callee) is gas deducted from and where an error originates from.

<!-- *TODO:* Mention gas refunds? -->
**TODO:** Mention gas refunds?

<!-- *TODO:* Consider option where non-calldata value transfer is not allowed, but there's a specific `TRANSFER`/`PAY` function for that. Would simplify the logic greatly. -->
**TODO:** Consider option where non-calldata value transfer is not allowed, but there's a specific `TRANSFER`/`PAY` function for that. Would simplify the logic greatly.

## Rationale

Expand Down