Our goal is to scale Farcaster to 1 million daily users. 

Farcaster will need to handle 10,000 messages / second while staying credibly decentralized. That's roughly in the same order of magnitude as most global credit card networks. 

Here's our proposal:

Our goal is to scale Farcaster to 1 million daily users. 

Farcaster will need to handle 10,000 messages / second while staying credibly decentralized. That's roughly in the same order of magnitude as most global credit card networks. 

Here's our proposal: https://github.com/farcasterxyz/protocol/discussions/163

Owner of /jellycuts + /routinehub, empowering devs to code from their mobile phone, starting w/ Shortcuts. Formerly: AMZN AI, META, Deadmau5.

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

cc @0xchris would love your thoughts on this as it relates to your experience helping scale WhatsApp to billions+

/ted | exploring the onchain frontier | surfing @ venice, ca | eating @ gjusta / gjelina

@v Strong write-up. Thank you for making these, they are clearly a labor of love. I read this doc 2x which means I don't have enough context but I one thing I notice is there isn't a clear end-to-end latency budget and then tiny latency budgets for each step in the sync value chain.  Happy to explain more via DM IRL.

There it is.  Sparing this thread and moving convi to Github.

The main budget is 10s for p90 message delivery.