Tezos_dal_node_libmodule Accuser : sig ... endmodule Amplificator : sig ... endThis module is about shard amplification, a feature allowing DAL nodes which receive enough shards of a given slot to contribute to the DAL reliability by reconstructing the slot, recomputing all the shards, and republishing the missing shards on the DAL network.
module Attestable_slots : sig ... endmodule Block_handler : sig ... endmodule Cli : sig ... endmodule Committee_cache : sig ... endCache for the DAL committee.
module Configuration_file : sig ... endmodule Constants : sig ... endmodule Crawler : sig ... endThis module maintains information about the layer 1 chain.
module Daemon : sig ... endmodule Dal_metrics : sig ... endmodule Dal_node_client : sig ... endmodule Dal_plugin : sig ... endmodule Dal_profiler : sig ... endmodule Dal_proto_types : sig ... endmodule Dal_store_sqlite3 : sig ... endmodule Dal_store_sqlite3_events : sig ... endmodule Errors : sig ... endmodule Event : sig ... endmodule History_check : sig ... endmodule L1_helpers : sig ... endmodule Message_validation : sig ... endmodule Metrics : sig ... endmodule Node_context : sig ... endmodule Opentelemetry_helpers : sig ... endmodule Process_worker : sig ... endmodule Profile_manager : sig ... endThis module provides different handlers related to DAL profiles.
module Proto_plugins : sig ... endThis module provides functionality related to protocol plugins.
module RPC_server : sig ... endmodule Rpc_context : sig ... endmodule Single_value_store : sig ... endHelper module to load/store a single value from/to disk.
module Slot_manager : sig ... endThis module provides different handlers related to DAL slots.
module Store : sig ... endThis module handles the on-disk storage of the DAL node. We rely on the Key_value_store module from lib_stdlib_unix. For shards storage, we rely on a cache mechanism in the case of non-prover profiles.
module Store_cleanup : sig ... endmodule Transport_layer_parameters : sig ... endmodule Value_size_hooks : sig ... endThe encoded_value_size required by Key_value_store.layout is known when the daemon loads a protocol, after the store is initialized. We use the closures like set_share_size to perform delayed protocol-specific parameter passing.
module Worker_parameters : sig ... end