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.

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

Update EIP-7002: Update eip-7002.md #9158

Merged
merged 2 commits into from
Dec 19, 2024
Merged
Changes from all commits
Commits
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
10 changes: 2 additions & 8 deletions EIPS/eip-7002.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,12 +29,6 @@ Note, 0x00 withdrawal credentials can be changed into 0x01 withdrawal credential

## Specification

### Constants

| Name | Value | Comment |
| - | - | - |
|`FORK_TIMESTAMP` | *TBD* | Mainnet |

### Configuration

| Name | Value | Comment |
Expand All @@ -57,7 +51,7 @@ Note, 0x00 withdrawal credentials can be changed into 0x01 withdrawal credential

#### Definitions

* **`FORK_BLOCK`** -- the first block in a blockchain with the `timestamp` greater or equal to `FORK_TIMESTAMP`.
* **`FORK_BLOCK`** -- the first block in a blockchain after this EIP has been activated.

#### Withdrawal request operation

Expand Down Expand Up @@ -149,7 +143,7 @@ When the input to the contract is length zero, interpret this as a get request f

##### System Call

At the end of processing any execution block where `block.timestamp >= FORK_TIMESTAMP` (i.e. after processing all transactions and after performing the block body withdrawal requests validations), call the contract as `SYSTEM_ADDRESS` and perform the following:
At the end of processing any execution block starting from the `FORK_BLOCK` (i.e. after processing all transactions and after performing the block body withdrawal requests validations), call the contract as `SYSTEM_ADDRESS` and perform the following:

* The contract's queue is updated based on withdrawal requests dequeued and the withdrawal requests queue head/tail are reset if the queue has been cleared (`dequeue_withdrawal_requests()`)
* The contract's excess withdrawal requests are updated based on usage in the current block (`update_excess_withdrawal_requests()`)
Expand Down
Loading