logo
pub struct GossipsubConfigBuilder { /* private fields */ }
Expand description

The builder struct for constructing a gossipsub configuration.

Implementations

The protocol id to negotiate this protocol (default is /meshsub/1.0.0).

Number of heartbeats to keep in the memcache (default is 5).

Number of past heartbeats to gossip about (default is 3).

Target number of peers for the mesh network (D in the spec, default is 6).

Minimum number of peers in mesh network before adding more (D_lo in the spec, default is 4).

Maximum number of peers in mesh network before removing some (D_high in the spec, default is 12).

Affects how peers are selected when pruning a mesh due to over subscription.

At least Self::retain_scores of the retained peers will be high-scoring, while the remainder are chosen randomly (D_score in the spec, default is 4).

Minimum number of peers to emit gossip to during a heartbeat (D_lazy in the spec, default is 6).

Affects how many peers we will emit gossip to at each heartbeat.

We will send gossip to gossip_factor * (total number of non-mesh peers), or gossip_lazy, whichever is greater. The default is 0.25.

Initial delay in each heartbeat (default is 5 seconds).

Time between each heartbeat (default is 1 second).

The number of heartbeat ticks until we recheck the connection to explicit peers and reconnecting if necessary (default 300).

Time to live for fanout peers (default is 60 seconds).

The maximum byte size for each gossip (default is 2048 bytes).

Duplicates are prevented by storing message id’s of known messages in an LRU time cache. This settings sets the time period that messages are stored in the cache. Duplicates can be received if duplicate messages are sent at a time greater than this setting apart. The default is 1 minute.

When set, prevents automatic forwarding of all received messages. This setting allows a user to validate the messages before propagating them to their peers. If set, the user must manually call crate::Gossipsub::report_message_validation_result() on the behaviour to forward a message once validated.

Determines the level of validation used when receiving messages. See ValidationMode for the available types. The default is ValidationMode::Strict.

A user-defined function allowing the user to specify the message id of a gossipsub message. The default value is to concatenate the source peer id with a sequence number. Setting this parameter allows the user to address packets arbitrarily. One example is content based addressing, where this function may be set to hash(message). This would prevent messages of the same content from being duplicated.

The function takes a GossipsubMessage as input and outputs a String to be interpreted as the message id.

A user-defined optional function that computes fast ids from raw messages. This can be used to avoid possibly expensive transformations from RawGossipsubMessage to GossipsubMessage for duplicates. Two semantically different messages must always have different fast message ids, but it is allowed that two semantically identical messages have different fast message ids as long as the message_id_fn produces the same id for them.

The function takes a RawGossipsubMessage as input and outputs a String to be interpreted as the fast message id. Default is None.

Enables Peer eXchange. This should be enabled in bootstrappers and other well connected/trusted nodes. The default is true.

Controls the number of peers to include in prune Peer eXchange.

When we prune a peer that’s eligible for PX (has a good score, etc), we will try to send them signed peer records for up to Self::prune_peers] other peers that we know of. It is recommended that this value is larger than [Self::mesh_n_high` so that the pruned peer can reliably form a full mesh. The default is 16.

Controls the backoff time for pruned peers. This is how long a peer must wait before attempting to graft into our mesh again after being pruned. When pruning a peer, we send them our value of Self::prune_backoff so they know the minimum time to wait. Peers running older versions may not send a backoff time, so if we receive a prune message without one, we will wait at least Self::prune_backoff before attempting to re-graft. The default is one minute.

Number of heartbeat slots considered as slack for backoffs. This gurantees that we wait at least backoff_slack heartbeats after a backoff is over before we try to graft. This solves problems occuring through high latencies. In particular if backoff_slack * heartbeat_interval is longer than any latencies between processing prunes on our side and processing prunes on the receiving side this guarantees that we get not punished for too early grafting. The default is 1.

Whether to do flood publishing or not. If enabled newly created messages will always be sent to all peers that are subscribed to the topic and have a good enough score. The default is true.

If a GRAFT comes before graft_flood_threshold has elapsed since the last PRUNE, then there is an extra score penalty applied to the peer through P7.

Minimum number of outbound peers in the mesh network before adding more (D_out in the spec). This value must be smaller or equal than mesh_n / 2 and smaller than mesh_n_low. The default is 2.

Number of heartbeat ticks that specifcy the interval in which opportunistic grafting is applied. Every opportunistic_graft_ticks we will attempt to select some high-scoring mesh peers to replace lower-scoring ones, if the median score of our mesh peers falls below a threshold (see https://godoc.org/github.com/libp2p/go-libp2p-pubsub#PeerScoreThresholds). The default is 60.

Controls how many times we will allow a peer to request the same message id through IWANT gossip before we start ignoring them. This is designed to prevent peers from spamming us with requests and wasting our resources.

The maximum number of new peers to graft to during opportunistic grafting. The default is 2.

The maximum number of messages we will process in a given RPC. If this is unset, there is no limit. The default is None.

The maximum number of messages to include in an IHAVE message. Also controls the maximum number of IHAVE ids we will accept and request with IWANT from a peer within a heartbeat, to protect from IHAVE floods. You should adjust this value from the default if your system is pushing more than 5000 messages in GossipSubHistoryGossip heartbeats; with the defaults this is 1666 messages/s. The default is 5000.

GossipSubMaxIHaveMessages is the maximum number of IHAVE messages to accept from a peer within a heartbeat.

By default, gossipsub will reject messages that are sent to us that has the same message source as we have specified locally. Enabling this, allows these messages and prevents penalizing the peer that sent us the message. Default is false.

Time to wait for a message requested through IWANT following an IHAVE advertisement. If the message is not received within this window, a broken promise is declared and the router may apply behavioural penalties. The default is 3 seconds.

Enable support for flooodsub peers.

Published message ids time cache duration. The default is 10 seconds.

Constructs a GossipsubConfig from the given configuration and validates the settings.

Trait Implementations

Returns the “default value” for a type. Read more

Performs the conversion.

Auto Trait Implementations

Blanket Implementations

Gets the TypeId of self. Read more

Immutably borrows from an owned value. Read more

Mutably borrows from an owned value. Read more

Returns the argument unchanged.

Calls U::from(self).

That is, this conversion is whatever the implementation of From<T> for U chooses to do.

Should always be Self

The type returned in the event of a conversion error.

Performs the conversion.

The type returned in the event of a conversion error.

Performs the conversion.