fc-updates

Scaling Gossip with Bundles

Hubs are running into scaling issues with libp2p. We're proposing a change to "bundle" messages to fix some of these issues. 

This may add a ~1s delay to casts moving between clients.

Scaling Gossip with Bundles

Hubs are running into scaling issues with libp2p. We're proposing a change to "bundle" messages to fix some of these issues. 

This may add a ~1s delay to casts moving between clients.

https://warpcast.notion.site/Scaling-Gossip-in-Hubble-e66c766fa6b04afcb407f4800134cd72?pvs=25

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

Blockchains use libp2p, but they generate only 10's or 100's of items per second today. 

Hubs generate 10,000 items per second at peak traffic, which is 100x - 1000x over your average blockchain. Importantly, hubs do not have any notion of a "block" and each cast or like is treated as a separate gossip message.

Bundles are not blocks. 

Blocks are strictly ordered, globally unique and immutable, and bundles are none of those things. This is because messages in farcaster are un-ordered and hubs may receive them in different orders and generate bundles differently.

The bundle logic would need to assume that there are duplicates, mutations etc and handle all of this gracefully.

@adityapk's proposal would group all the messages that appear in 1 second into a bundle, which is then gossiped out. 

Each bundle is substantially larger in size, but we will have ~100x fewer gossip messages running around at any given time.

I can't remember exactly but this smells like something that was added the the Flow Blockchain libp2p gossip a few years back when I was there as well.

There's actually quite a lot of meta chatter that can happen between sequencing nodes.

Maybe someone remembers ...