Content
@
0 reply
0 recast
2 reactions
Dan Romero
@dwr.eth
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.
8 replies
13 recasts
48 reactions
Dan Romero
@dwr.eth
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.
4 replies
1 recast
1 reaction
Dan Romero
@dwr.eth
...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.
0 reply
1 recast
1 reaction
Wasif Iqbal
@wazzymandias.eth
ah rocksdb, my old friend Such a pain to optimize but I guess if it already has NodeJS bindings I can see why y'all went for it
1 reply
0 recast
0 reaction
William Saar
@saarw.eth
Curious why Farcaster uses CRDTs? Do sets of updates get created in different places and merged in arbitrary order? If so, CRDTs are probably needed, but if one hub controls the creation of each set, techniques like event sourcing can provide smaller states
1 reply
0 recast
0 reaction
Tempe.degen 🎩 🔜 Devcon BKK
@tempetechie.eth
Did you also consider Ceramic Network (DB on top of IPFS) for storage? Or could Hubble switch to Ceramic in the future? 🤔
0 reply
0 recast
1 reaction