EIP-7805 -- Honest Validator¶
- Introduction
- Prerequisites
- Configuration
- Time parameters
- Helpers
- New
GetInclusionListResponse - Protocols
ExecutionEngine- Beacon chain responsibilities
- Validator assignments
- Block and sidecar proposal
- Inclusion list proposal
- Attesting
- Sync committee
Introduction¶
This document represents the changes to be made in the code of an "honest validator" to implement EIP-7805.
Prerequisites¶
This document is an extension of the Fulu -- Honest Validator guide. All behaviors and definitions defined in this document, and documents it extends, carry over unless explicitly noted or overridden.
All terminology, constants, functions, and protocol mechanics defined in the updated Beacon Chain doc of EIP-7805 are requisite for this document and used throughout. Please see related Beacon Chain doc before continuing and use them as a reference throughout.
Configuration¶
Time parameters¶
| Name | Value | Unit | Duration |
|---|---|---|---|
INCLUSION_LIST_SUBMISSION_DUE_BPS |
uint64(6667) |
basis points | ~67% of SLOT_DURATION_MS |
PROPOSER_INCLUSION_LIST_CUTOFF_BPS |
uint64(9167) |
basis points | ~92% of SLOT_DURATION_MS |
Helpers¶
New GetInclusionListResponse¶
Protocols¶
ExecutionEngine¶
Note: get_inclusion_list function is added to the ExecutionEngine protocol
for use as an inclusion list committee member.
The body of this function is implementation dependent. The Engine API may be used to implement it with an external execution engine.
New get_inclusion_list¶
get_inclusion_list returns GetInclusionListResponse with the most recent
inclusion list transactions that has been built based on the latest view of the
public mempool.
Beacon chain responsibilities¶
All validator responsibilities remain unchanged other than those noted below.
Validator assignments¶
Inclusion list committee¶
A validator may be a member of the new inclusion list committee for a given
slot. To determine inclusion list committee assignments, the validator can run
the following function:
get_inclusion_committee_assignment(state, epoch, validator_index) where
epoch <= next_epoch.
Inclusion list committee selection is only stable within the context of the current and next epoch.
Lookahead¶
get_inclusion_committee_assignment should be called at the start of each epoch
to get the assignment for the next epoch (current_epoch + 1). A validator
should plan for future assignments by noting their assigned inclusion list
committee slot.
Block and sidecar proposal¶
Constructing the BeaconBlockBody¶
ExecutionPayload¶
Note: In this section, state is the state of the slot for the block proposal
without the block yet applied. That is, state is the previous_state
processed through any empty slots up to the assigned slot using
process_slots(previous_state, slot).
Note: The only change to prepare_execution_payload is to call
get_inclusion_list_store and get_inclusion_list_transactions to set the new
inclusion_list_transactions field of PayloadAttributes.
Note: A proposer should produce an execution payload that satisfies the
inclusion list constraints with respect to the inclusion lists gathered up to
get_proposer_inclusion_list_cutoff_ms(epoch) milliseconds into the slot.
Inclusion list proposal¶
A validator is expected to propose a
SignedInclusionList at the beginning
of any slot for which
get_inclusion_committee_assignment(state, epoch, validator_index) returns.
If a validator is in the current inclusion list committee, the validator should
create and broadcast the signed_inclusion_list to the global inclusion_list
subnet by get_inclusion_list_submission_due_ms(epoch) milliseconds into the
slot after processing the block for the current slot and confirming it as the
head. If no block is received by
get_inclusion_list_submission_due_ms(epoch) - 1000 milliseconds into the slot,
the validator should run get_head to determine the local head and construct
and broadcast the inclusion list based on this local head by
get_inclusion_list_submission_due_ms(epoch) milliseconds into the slot.
Constructing the SignedInclusionList¶
The validator creates the signed_inclusion_list as follows:
- First, the validator creates the
inclusion_list. - Set
inclusion_list.slotto the assigned slot returned byget_inclusion_committee_assignment. - Set
inclusion_list.validator_indexto the validator's index. - Set
inclusion_list.inclusion_list_committee_rootto the hash tree root of the committee that the validator is a member of. - Set
inclusion_list.transactionsusing the response fromExecutionEngineviaget_inclusion_list. - Sign the
inclusion_listusing the helperget_inclusion_list_signatureand obtain thesignature. - Set
signed_inclusion_list.messagetoinclusion_list. - Set
signed_inclusion_list.signaturetosignature.
Attesting¶
Attestation data¶
Note: The only change to attestation_data is to call
get_attester_head(store, head_root) to set the beacon_block_root field of
attestation_data.
Modified LMD GHOST vote¶
Set attestation_data.beacon_block_root = get_attester_head(store, head_root).
Sync committee¶
Note: The only change to get_sync_committee_message is to call
get_attester_head(store, head_root) to set the beacon_block_root parameter
of get_sync_committee_message.
get_sync_committee_message¶
Modified beacon_block_root¶
The beacon_block_root parameter MUST be set to return value of
get_attester_head(store: Store, head_root: Root)
function.