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

Updates links to eips repo to be absolute, not relative #9

Merged
merged 1 commit into from
Feb 5, 2024
Merged

Updates links to eips repo to be absolute, not relative #9

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
20 changes: 10 additions & 10 deletions RIPS/rip-7560.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,8 +13,8 @@ requires: 4337, 6780

## Abstract

Combining the [EIP-2938](./eip-2938)
and [ERC-4337](./eip-4337)
Combining the [EIP-2938](https://eips.ethereum.org/EIPS/eip-2938)
and [ERC-4337](https://eips.ethereum.org/EIPS/eip-4337)
into a comprehensive Native Account Abstraction proposal.

We propose splitting the Ethereum transaction scope into multiple steps: validations, execution,
Expand Down Expand Up @@ -75,7 +75,7 @@ smart contracts. This, however, is impossible without an addition of Native Acco

### New Transaction Type

A new [EIP-2718](./eip-2718) transaction with type AA_TX_TYPE is introduced. Transactions of this type are referred to as
A new [EIP-2718](https://eips.ethereum.org/EIPS/eip-2718) transaction with type AA_TX_TYPE is introduced. Transactions of this type are referred to as
“AA transactions”. Their payload should be interpreted as:

```
Expand Down Expand Up @@ -274,7 +274,7 @@ in order for the transaction to be considered valid for a given position in a bl

In terms of block validity, all validation and execution frames may read and write any state when included in the block.
However, the AA transactions in the mempool SHOULD be bound by storage access rules to avoid DoS on block builders.
These rules are defined in [ERC-7562](./eips/eip-7562).
These rules are defined in [ERC-7562](https://eips.ethereum.org/EIPS/eips/eip-7562).

In all top-level frames, the global variables have the following meaning:

Expand Down Expand Up @@ -562,8 +562,8 @@ There is a number of behaviours that define transaction-wide effects in Ethereum
This list includes, but is not limited to:

* Tracking `accessed_addresses`
* [EIP-1283](./eip-1283) Gas metering for SSTORE
* [EIP-1153](./eip-1153) Transient storage opcodes
* [EIP-1283](https://eips.ethereum.org/EIPS/eip-1283) Gas metering for SSTORE
* [EIP-1153](https://eips.ethereum.org/EIPS/eip-1153) Transient storage opcodes

Any such behaviour has separate effects in the "Validation Virtual Transaction" and "Execution Transaction".

Expand Down Expand Up @@ -792,9 +792,9 @@ It will enable all existing EOAs to benefit from the improved UX features like g

In the future, this can be used to pay gas for transactions that add code to the EOA addresses,
once Ethereum implements changes like the ones proposed in
[EIP-5003: Insert Code into EOAs with AUTHUSURP](./eip-5003),
[EIP-6913: SETCODE instruction](./eip-6913) and
[EIP-7377: Migration Transaction](./eip-7377).
[EIP-5003: Insert Code into EOAs with AUTHUSURP](https://eips.ethereum.org/EIPS/eip-5003),
[EIP-6913: SETCODE instruction](https://eips.ethereum.org/EIPS/eip-6913) and
[EIP-7377: Migration Transaction](https://eips.ethereum.org/EIPS/eip-7377).

## Backwards Compatibility

Expand All @@ -808,7 +808,7 @@ The assumption that `tx.origin` is the address that pays for the current transac
Any code that expects a single top-level execution frame for an Ethereum transaction will have to accommodate
the new transaction type.

[EIP-3607](./eip-3607) introduces a ban on transactions from senders with deployed code.
[EIP-3607](https://eips.ethereum.org/EIPS/eip-3607) introduces a ban on transactions from senders with deployed code.
This limitation does not apply to AA_TX_TYPE transactions.

### Migration path for existing ERC-4337 projects and further roadmap
Expand Down