Skip to content
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

Jump to bottom

Remove the deprecated "Validation phase observability" section #21

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Remove the deprecated "Validation phase observability" section #21

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 0 additions & 13 deletions RIPS/rip-7711.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,19 +112,6 @@ but are not represented as separate transactions in the block data.
![](../assets/rip-7560/block_overview.png)
*The structure of a block containing multiple Native Account Abstraction Transactions*

### Validation phase observability

The validation frames of the AA_TX_TYPE transaction are treated as separate individual transactions by the RPC clients.
They are assigned their own sequential `transactionIndex`, and their `transactionHash` is defined as
(`AA_TX_TYPE transaction hash + 1`).

All block-related RPC methods, like `eth_getBlockByHash` and `eth_getBlockByNumber`, must include these
validation frames as part of the `transactions` field and include validation in the block transaction count.

All transaction-related RPC methods, like `eth_getTransactionByHash` and `eth_getTransactionReceipt`, must
accept the validation frame transaction hash as input and return the details calculated as if the validation was a
separate transaction.

### Transaction execution context

Note that some behaviours in the EVM depend on the transaction context. These behaviours are:
Expand Down