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

I think there's room to improve syncing (for example bundles) if you take into account that Farcaster has special patterns. For example, most users use a single hub (their client's hub) 99% of the time. Can we optimize assuming that the hub will bundle messages in a specific way, and treat bundles as probably unique?

Dad, geek, conversation liquidity provider. vrypan.net (home), /weatherxm (work), @l--o--l (fun). Also https://paragraph.xyz/@purplesubmarine

For example, if Warpcast hubs created separate bundles for messages originating from WC users in a well-defined way and messages received from other hubs, the originating bundles could travel across the network as such. And in most cases, hubs would only have to check the bundle hash to decide if they need them.

Actually, after reading the proposal again, I see that it is very close to what I said above. (I had missed the src=grpc part).
I can't comment on the proposal, is commenting open? (Never understood notion).

I.e. pay a higher cost if it turns out that messages are not bundled as "expected", but assuming that this cost will be rarely paid?