Withdrawals push #2836
Withdrawals push #2836
Conversation
minor Merge and forkchoice updates release
Co-authored-by: Mikhail Kalinin <noblesse.knight@gmail.com>
release v1.1.7
release v1.1.8
|
We may also consider a separate |
Ensure that the SSZ object classes are ordered
djrtwo
force-pushed
the
withdrawals-push
branch
from
531fdb9
to
1ab5206
Compare
djrtwo
force-pushed
the
withdrawals-push
branch
from
1ab5206
to
3dd83cf
Compare
|
We've been working on a proposal for execution layer only push with a mechanism closer to how the deposit contract works: |
| ```python | ||
| def process_block(state: BeaconState, block: BeaconBlock) -> None: | ||
| process_block_header(state, block) | ||
| if is_execution_enabled(state, block.body): |
There was a problem hiding this comment.
I think that this check and other checks in the spec that are related to the Merge transition should be removed in a cleanup fork after the Merge. Not directly related to Cappella but worth keeping in mind.
There was a problem hiding this comment.
yeah, I think so too
will address in separate PR. It needs some testing fixes -- e.g. all transition tests need to be labeled with_only_bellatrix
There was a problem hiding this comment.
Should be reviewed. There is a problem between the account and management account is being reviewed
tests/core/pyspec/eth2spec/test/capella/block_processing/test_process_withdrawals.py
Show resolved
Hide resolved
Co-authored-by: Alex Stokes <r.alex.stokes@gmail.com>
…nto withdrawals-push
BeaconStatemaintains a queue ofwithdrawal_receipts(one receipt added for each call towithdraw())min(MAX_WITHDRAWAL_TRANSACTIONS_PER_PAYLOAD, len(withdrawal_receipts))receipts are dequeued into ExecutionPayload at each slotExecutionEngineinterfaceprocess_withdrawalsandprocess_full_withdrawals