p2p-interface.md

Heze -- Networking

Note: This document is a work-in-progress for researchers and implementers.

• Introduction
• Modifications in Heze
  • Configuration
  • Helpers
    • Modified compute_fork_version
  • The gossip domain: gossipsub
    • Topics and messages
      • Global topics
        • inclusion_list
  • The Req/Resp domain
    • Messages
      • InclusionListByCommitteeIndices v1

Introduction

This document contains the consensus-layer networking specifications for Heze.

The specification of these changes continues in the same format as the network specifications of previous upgrades, and assumes them as pre-requisite.

Modifications in Heze

Configuration

Name	Value	Description
MAX_REQUEST_INCLUSION_LIST	2**4 (= 16)	Maximum number of inclusion list in a single request
MAX_BYTES_PER_INCLUSION_LIST	2**13 (= 8,192)	Maximum size of the inclusion list's transactions in bytes

Helpers

Modified compute_fork_version

def compute_fork_version(epoch: Epoch) -> Version:
    """
    Return the fork version at the given ``epoch``.
    """
    if epoch >= HEZE_FORK_EPOCH:
        return HEZE_FORK_VERSION
    if epoch >= GLOAS_FORK_EPOCH:
        return GLOAS_FORK_VERSION
    if epoch >= FULU_FORK_EPOCH:
        return FULU_FORK_VERSION
    if epoch >= ELECTRA_FORK_EPOCH:
        return ELECTRA_FORK_VERSION
    if epoch >= DENEB_FORK_EPOCH:
        return DENEB_FORK_VERSION
    if epoch >= CAPELLA_FORK_EPOCH:
        return CAPELLA_FORK_VERSION
    if epoch >= BELLATRIX_FORK_EPOCH:
        return BELLATRIX_FORK_VERSION
    if epoch >= ALTAIR_FORK_EPOCH:
        return ALTAIR_FORK_VERSION
    return GENESIS_FORK_VERSION

The gossip domain: gossipsub

Topics and messages

The new topics along with the type of the data field of a gossipsub message are given in this table:

Name	Message Type
inclusion_list	SignedInclusionList

Global topics

Heze introduces a new global topic for inclusion lists.

inclusion_list

This topic is used to propagate signed inclusion list as SignedInclusionList. The following validations MUST pass before forwarding the inclusion_list on the network, assuming the alias message = signed_inclusion_list.message:

• [REJECT] The size of message.transactions is within upperbound MAX_BYTES_PER_INCLUSION_LIST.
• [IGNORE] The slot message.slot is equal to the current slot (with a MAXIMUM_GOSSIP_CLOCK_DISPARITY allowance), i.e. data.slot == current_slot.
• [IGNORE] The inclusion_list_committee for slot message.slot on the current branch corresponds to message.inclusion_list_committee_root, as determined by hash_tree_root(inclusion_list_committee) == message.inclusion_list_committee_root.
• [REJECT] The validator index message.validator_index is within the inclusion_list_committee corresponding to message.inclusion_list_committee_root.
• [IGNORE] The message is either the first or second valid message received from the validator with index message.validator_index.
• [REJECT] The signature of signed_inclusion_list.signature is valid with respect to the validator's public key.

The Req/Resp domain

Messages

InclusionListByCommitteeIndices v1

Protocol ID: /eth2/beacon_chain/req/inclusion_list_by_committee_indices/1/

For each successful response_chunk, the ForkDigest context epoch is determined by compute_epoch_at_slot(signed_inclusion_list.message.slot).

Per fork_version = compute_fork_version(epoch):

fork_version	Chunk SSZ type
HEZE_FORK_VERSION	heze.SignedInclusionList

Request Content:

(
  slot: Slot
  committee_indices: Bitvector[INCLUSION_LIST_COMMITTEE_SIZE]
)

Response Content:

(
  List[SignedInclusionList, MAX_REQUEST_INCLUSION_LIST]
)