F3 Certificate Exchange

F3 Certificate Exchange

Note that this graph shows the PeerIDs as opposed to the number of Storage Providers. Multiple storage providers can run behind a single peer identity.

Shows the number of online peer IDs in each Nebula crawl, grouped by how they answer F3 certificate exchange requests. During a crawl, Nebula asks each peer for its latest F3 finality certificate. We compare the instance in this certificate with the network-wide finalized instance: the latest instance that reached quorum before the crawl started, as seen by our Hermes GossipSub node. The chart groups peers into five categories:

• Caught Up: The peer responded to our certificate exchange request and the latest finalized instance in the peer's point of view is at most one instance behind the network-wide finalized instance.
• Lagging: The peer responded to our certificate exchange request but the latest finalized instance in the peer's point of view is more than one instance behind the network-wide finalized instance.
• Exchange Error: The peer supports the F3 Certificate Exchange protocol but our certificate exchange request failed.
• No Support: The peer does not support the F3 Certificate Exchange protocol: /f3/certexch/get/1/filecoin
• Unknown: We consider this peer as being online but we could not determine the certificate exchange support status, for example because the identify exchange failed.

Use the agent select to show only the peers of one agent type.