Tezos_dal_node_services.TypesSourceA Tezos level.
An index of a DAL slot header.
An index of a DAL page.
A topic is defined by a public key hash of an attester and a slot index.
A message id uniquely identifies a share whose commitment is included in an L1 block. It is defined by a tuple containing the commitment, the level at which the commitment is successfully included in an L1 block, the corresponding slot index, the shard index, as well as the public key hash pkh of the delegate expected to attest it.
A message is a portion of an encoded slot's data. It's basically a shard without the corresponding index. The proof that the corresponding shard belong to the commitment (part of the message id) is also part of the message.
From the Gossipsub point of view, a peer is given by a cryptographic node identity P2p_peer.Id.t. It's up to the caller to associate the P2p_peer.Id.t to a P2p_point.Id.t if needed (to e.g. implement peers exchange, which needs addresses and ports instead of cryptographic identities).
A point is made of an IP address and a port. Only the worker knows about the notion. The automaton only sees peers (i.e. cryptographic identities of nodes).
A set of slots, represented by a list of booleans (false for not in the set). It is used for instance to record which slots are deemed available by an attester. The level at which the slots have been published is also given.
The set of attestable slots of an attester (which may not necessarily be in the committee for a given level).
An index of a DAL shard
type header_status = [ | `Waiting_attestationThe slot header was included and applied in a finalized L1 block but remains to be attested.
*)| `AttestedThe slot header was included in an L1 block and attested.
*)| `UnattestedThe slot header was included in an L1 block but not timely attested.
*)| `Not_selectedThe slot header was included in an L1 block but was not selected as the slot header for that slot index.
*)| `Unseen_or_not_finalizedThe slot header was not seen in a *final* L1 block. This could only happen if the RPC `PATCH /commitments/<commitment>` was called but the corresponding slot header was not included in a final block. In turn, this means that the publish operation was not sent (yet) to L1, or sent but not included (yet) in a block, or included in a not (yet) final block.
*) ]The status of a header a DAL node is aware of:
type operator_profile = | Attester of Tezos_crypto.Signature.public_key_hashAttester pkh downloads all shards assigned to pkh. Used by bakers to attest availability of their assigned shards.
| Producer of {}Producer {slot_index} produces/publishes slot for slot index slot_index.
| Observer of {}Observer {slot_index} observes slot for slot index slot_index: collects the shards corresponding to some slot index, reconstructs slots when enough shards are seen, and republishes missing shards.
Profiles that operate on shards/slots.
List of operator profiles. It may contain dupicates as it represents profiles provided by the user in unprocessed form.
type profiles = | BootstrapThe bootstrap profile facilitates peer discovery in the DAL network. Note that bootstrap nodes are incompatible with attester/producer/observer profiles as bootstrap nodes are expected to connect to all the meshes with degree 0.
*)| Operator of operator_profiles| Random_observerDAL node can track one or many profiles that correspond to various modes that the DAL node would operate in.
type slot_header = {slot_id : slot_id;commitment : Cryptobox.Commitment.t;status : header_status;}Information associated to a slot header in the RPC services of the DAL node.
The with_proof flag is associated to shards computation. It indicates whether we also compute shards' proofs or not.