Inclusion list production duty

[mehdi-aouadi]

New inclusion list committee duty

Some validators are selected to submit signed inclusion list. Validators should call get_inclusion_committee_assignment at the beginning of an epoch to be prepared to submit their inclusion list during the next epoch.

A validator should create and broadcast the signed_inclusion_list to the global inclusion_list subnet by PROPOSER_INCLUSION_LIST_CUT_OFF seconds into the slot, unless a block for the current slot has been processed and is the head of the chain and broadcast to the network.

Constructing a signed inclusion list

The validator creates the signed_inclusion_list as follows:

• First, the validator creates the inclusion_list.
• Set inclusion_list.slot to the assigned slot returned by get_inclusion_committee_assignment.
• Set inclusion_list.validator_index to the validator's index.
• Set inclusion_list.inclusion_list_committee_root to the hash tree root of the committee that the validator is a member of.
• Set inclusion_list.transactions using the response from engine_getInclusionListV1 from the execution layer client.
• Sign the inclusion_list using the helper get_inclusion_list_signature and obtain the signature.
• Set signed_inclusion_list.message to inclusion_list.
• Set signed_inclusion_list.signature to signature.

def get_inclusion_list_signature(
        state: BeaconState, inclusion_list: InclusionList, privkey: int) -> BLSSignature:
    domain = get_domain(state, DOMAIN_INCLUSION_LIST_COMMITTEE, compute_epoch_at_slot(inclusion_list.slot))
    signing_root = compute_signing_root(inclusion_list, domain)
    return bls.Sign(privkey, signing_root)