A place for developers to talk about building on Farcaster.

/dev

How Farcaster Hubs work

Hubs validate, storage and replicate account messages to other hubs in a decentralized way. 

There are 3 main components: storage, p2p and sync.

Hubble will only peer with trusted peers and employs a simple network topology during beta. It peers only with known instances which must be configured at startup. In later releases, the network topology will be modified to operate closer to a trustless mesh.

2. P2P​
Hubble connects to other peers over a GossipSub network established using LibP2P. Messages merged into the Storage Engine are immediately gossiped to all of is peers.

...CRDT sets are implemented to meet the specification in the Farcaster protocol. The engine also tracks state of the Farcaster contracts, which are necessary for validating the Signer CRDT Set.

1. Storage​
Messages received by Hubble are forwarded to the Storage engine which forwards them to the appropriate CRDT Set. Once validated by the CRDT Set, messages are persisted to RocksDB and events are emitted to listeners.

Any boost here would be greatly appreciated

Any boost here would be greatly appreciated

https://twitter.com/dwr/status/1699810596135530634

3. Sync​
Hubble periodically performs a diff sync with other peers to discover messages that may have been dropped during gossip. This is performed using gRPC APIs exposed by each Hub instance.

Doing tricks with polynomials. Computational monadologist. Prev: ML HealthCareInc 🦄 | R&D PeopleFund | AI & Stats lecturer

I think thats validating that the message has the correct properties and correct data types

What is “Check Props” doing inside the Validate box?

Access to the data and APIs of the network. Same direct incentive for Bitcoin and Ethereum.

This is very helpful -- would also be cool to see an explainer on the Farcaster YouTube channel!

This is very helpful -- would also be cool to see an explainer on the Farcaster YouTube channel!

https://www.youtube.com/@farcasterxyz