Skip to content

Commit

Permalink
Update eip-2026.md
Browse files Browse the repository at this point in the history
  • Loading branch information
@ret2happy
ret2happy authored Feb 22, 2024
1 parent 7dc21dd commit 2c10166
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions EIPS/eip-2026.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ The penalty is levied to the transaction sender. Rather than raising the gas cos
## Specification

Check failure on line 27 in EIPS/eip-2026.md

View workflow job for this annotation

GitHub Actions / Markdown Linter

Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "## Specification"] 

EIPS/eip-2026.md:27 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "## Specification"]

Check failure on line 27 in EIPS/eip-2026.md

View workflow job for this annotation

GitHub Actions / Markdown Linter

Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "## Specification"] 

EIPS/eip-2026.md:27 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "## Specification"]
On and after block `H`, every newly created account gets a new field `rentbalance` of type unsigned 256-bit integer.
On and after block `H`, any operation that leads to the creation of a new account, deducts the amount `ACCOUNT_PREPAYMENT` from `tx.origin`. This amount is added to the `rentbalance` field of the created account.
On and after block `H`, any operation that modifies an account that does not yet have `rentbalance` field, deducts the amount `ACCOUNT_PREPAYEMENT` from `tx.origin`. This amount is added to the `rentbalance` field of the modified account. This is a anti-hoarding measure.
On and after block `H`, any operation that modifies an account that does not yet have `rentbalance` field, deducts the amount `ACCOUNT_PREPAYEMENT` from `tx.origin`. This amount is added to the `rentbalance` field of the modified account. This is an anti-hoarding measure.

Operations leading to the creations of a new account:
1. Creation of a non-contract account by sending non-zero ETH to an address with no associated account

Check failure on line 33 in EIPS/eip-2026.md

View workflow job for this annotation

GitHub Actions / Markdown Linter

Lists should be surrounded by blank lines [Context: "1. Creation of a non-contract ..."] 

EIPS/eip-2026.md:33 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "1. Creation of a non-contract ..."]

Check failure on line 33 in EIPS/eip-2026.md

View workflow job for this annotation

GitHub Actions / Markdown Linter

Lists should be surrounded by blank lines [Context: "1. Creation of a non-contract ..."] 

EIPS/eip-2026.md:33 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "1. Creation of a non-contract ..."]
Expand All @@ -45,7 +45,7 @@ Prior to rent prepayments, other alternatives were considered:
1. In [first version of State Rent proposal](https://github.com/ledgerwatch/eth_state/blob/master/State_rent.pdf), there was no notion of extra levy upon account creation. It created a slight usability issue, where newly created contracts with 0 endowment would be evicted in the same block (when rent is introduced). It delays the benefits of the State Rent programme until the actual introduction of rent (in second or third hard-fork).

Check warning on line 45 in EIPS/eip-2026.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
  --> EIPS/eip-2026.md
   |
45 | 1. In [first version of State Rent proposal](https://github.com/ledgerwatch/eth_state/blob/master/State_rent.pdf), there was no notion of extra levy upon account creation. It created a slight usability issue, where newly created contracts with 0 endowment would be evicted in the same block (when rent is introduced). It delays the benefits of the State Rent programme until the actual introduction of rent (in second or third hard-fork).
   |
   = help: see https://ethereum.github.io/eipw/markdown-rel-links/

Check warning on line 45 in EIPS/eip-2026.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
  --> EIPS/eip-2026.md
   |
45 | 1. In [first version of State Rent proposal](https://github.com/ledgerwatch/eth_state/blob/master/State_rent.pdf), there was no notion of extra levy upon account creation. It created a slight usability issue, where newly created contracts with 0 endowment would be evicted in the same block (when rent is introduced). It delays the benefits of the State Rent programme until the actual introduction of rent (in second or third hard-fork).
   |
   = help: see https://ethereum.github.io/eipw/markdown-rel-links/
2. In the [second version of State Rent proposal](https://github.com/ledgerwatch/eth_state/blob/master/State_Rent_2.pdf), there was a notion of lock-up. It is very similar to rent prepayment, with the different that lock-up would not be covering future rent payments.

Check warning on line 46 in EIPS/eip-2026.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
  --> EIPS/eip-2026.md
   |
46 | 2. In the [second version of State Rent proposal](https://github.com/ledgerwatch/eth_state/blob/master/State_Rent_2.pdf), there was a notion of lock-up. It is very similar to rent prepayment, with the different that lock-up would not be covering future rent payments.
   |

Check warning on line 46 in EIPS/eip-2026.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
  --> EIPS/eip-2026.md
   |
46 | 2. In the [second version of State Rent proposal](https://github.com/ledgerwatch/eth_state/blob/master/State_Rent_2.pdf), there was a notion of lock-up. It is very similar to rent prepayment, with the different that lock-up would not be covering future rent payments.
   |

An alternative approach to limiting the prepayments (instead of the using `gaslimit` * `gasprice` as the limit) is to introduce a new dedicated field `prepaymenlimit` into the transaction. This field would only limit prepayments). Such approach would require changes in the transaction format, as well as changes in the user interface for transaction sender, and having two counters during the transaction execution - one for gas, and one for prepayments.
An alternative approach to limiting the prepayments (instead of the using `gaslimit` * `gasprice` as the limit) is to introduce a new dedicated field `prepaymenlimit` into the transaction. This field would only limit prepayments. Such approach would require changes in the transaction format, as well as changes in the user interface for transaction sender, and having two counters during the transaction execution - one for gas, and one for prepayments.

## Backwards Compatibility

Check failure on line 50 in EIPS/eip-2026.md

View workflow job for this annotation

GitHub Actions / Markdown Linter

Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "## Backwards Compatibility"] 

EIPS/eip-2026.md:50 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "## Backwards Compatibility"]

Check failure on line 50 in EIPS/eip-2026.md

View workflow job for this annotation

GitHub Actions / Markdown Linter

Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "## Backwards Compatibility"] 

EIPS/eip-2026.md:50 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "## Backwards Compatibility"]
This change is not backwards compatible and requires hard fork to be activated.
Expand Down

0 comments on commit 2c10166

Please sign in to comment.