package octez-libs
Parameters
module C : Gossipsub_intf.WORKER_CONFIGURATION
Signature
We (re-)export the GS, Monad and Stream modules.
include Gossipsub_intf.WORKER_CONFIGURATION
with module GS = C.GS
with module GS.Topic = C.GS.Topic
with module GS.Peer = C.GS.Peer
with module Monad = C.Monad
with module Stream = C.Stream
with module Point = C.Point
module GS :
module type of struct include C.GS end
with module Topic = C.GS.Topic
with module Peer = C.GS.Peer
The gossipsub automaton that will be used by the worker.
module Point = C.Point
module Monad = C.Monad
Abstraction of the IO monad used by the worker.
module Stream = C.Stream
A mutable (FIFO) stream of data.
type message_with_header = {
message : GS.Message.t;
topic : GS.Topic.t;
message_id : GS.Message_id.t;
}
A message together with a header, that is, a topic and an id. This corresponds to what the spec calls a "full message".
type p2p_message =
| Graft of {
topic : GS.Topic.t;
}
| Prune of {
topic : GS.Topic.t;
px : GS.Peer.t Tezos_base.TzPervasives.Seq.t;
backoff : GS.Span.t;
}
| IHave of {
topic : GS.Topic.t;
message_ids : GS.Message_id.t list;
}
| IWant of {
message_ids : GS.Message_id.t list;
}
| Subscribe of {
topic : GS.Topic.t;
}
| Unsubscribe of {
topic : GS.Topic.t;
}
| Message_with_header of message_with_header
The following type defines the different kinds of messages a peer could receive from or sent to the P2P layer.
type p2p_input =
| In_message of {
from_peer : GS.Peer.t;
p2p_message : p2p_message;
}
| New_connection of {
peer : GS.Peer.t;
direct : bool;
trusted : bool;
bootstrap : bool;
}
| Disconnection of {
peer : GS.Peer.t;
}
The different kinds of input events that could be received from the P2P layer.
The different kinds of input events that could be received from the application layer.
A peer's origin is either another peer (i.e. advertised via PX), or none if it is trusted.
type p2p_output =
| Out_message of {
to_peer : GS.Peer.t;
p2p_message : p2p_message;
}
(*Emit the given
*)p2p_message
to the remote peerto_peer
.| Disconnect of {
peer : GS.Peer.t;
}
(*End the connection with the peer
*)peer
.| Kick of {
peer : GS.Peer.t;
}
(*Kick the peer
*)peer
: the peer is disconnected and blacklisted.| Connect of {
peer : GS.Peer.t;
origin : peer_origin;
}
(*Inform the p2p_output messages processor that we want to connect to the peer
*)peer
advertised by some other peerorigin
.| Connect_point of {
point : Point.t;
}
(*Version of connect where we provide a point directly.
*)| Forget of {
}
(*Inform the p2p_output messages processor that we don't want to connect to the peer
*)peer
advertised by some other peerorigin
.
The different kinds of outputs that could be emitted by the worker for the P2P layer.
type app_output = message_with_header
The application layer will be advertised about full messages it's interested in.
The different kinds of events the Gossipsub worker handles.
val make :
?events_logging:(event -> unit Monad.t) ->
?bootstrap_points:Point.t list ->
Random.State.t ->
(GS.Topic.t, GS.Peer.t, GS.Message_id.t, GS.span) Gossipsub_intf.limits ->
(GS.Peer.t, GS.Message_id.t) Gossipsub_intf.parameters ->
t
make ~events_logging ~bootstrap_points rng limits parameters
initializes a new Gossipsub automaton with the given arguments. Then, it initializes and returns a worker for it. The events_logging
function can be used to define a handler for logging the worker's events. The list of bootstrap_points
represents the list of initially known peers' addresses to which we may want to reconnect in the worker.
val start : GS.Topic.t list -> t -> unit
start topics state
runs the (not already started) worker whose state
is given together with the initial list of topics
the caller is interested in.
app_input state app_input
adds the given application input app_input
to the worker's input stream.
p2p_input state p2p_input
adds the given P2P input p2p_input
to the worker's input stream.
val p2p_output_stream : t -> p2p_output Stream.t
p2p_output_stream t
returns the output stream containing data for the P2P layer.
val app_output_stream : t -> app_output Stream.t
app_output_stream t
returns the output stream containing data for the application layer.
input_events_stream t
returns the input stream in which we push events to be processed by the worker.
val is_subscribed : t -> GS.Topic.t -> bool
is_subscribed t topic
checks whether topic
is in the mesh of t
.
val pp_p2p_output : Format.formatter -> p2p_output -> unit
Pretty-printer for values of type p2p_output
.
val pp_app_output : Format.formatter -> app_output -> unit
Pretty-printer for values of type app_output
.
module Introspection : sig ... end
Introspection and stats facilities
val stats : t -> Introspection.stats
val state : t -> GS.Introspection.view