We’ve spent this week refactoring our backend and consolidating all Farcaster-specific logic into our newly revamped Superhub repo. It was a massive effort - hundreds of internal commits - and the result is a clean, modular, and open-source Farcaster Layer 2 that anyone can fork and customize. Our goal has always been to support Farcaster’s march toward 1B DAU, so we’re thrilled to give developers a versatile foundation for spinning up their own L2, experimenting with unique features, and acc...

We know the goal of Farcaster is to hit 1B DAU - and that's why we're excited about exploring scaling strategies outside of the Snapchain. When far.quest was the first viral client at a time when Farcaster was invite-only, we immediately overcame this limitation via address-as-FID endpoints. Our logic was: why lose a potential user when we can just make our endpoints work? We called our solution a "Farcaster L2", and had a lot of initial pushback given Farcaster was a small network. Now we th...

We're here to share our key learnings from one year of running our own completely vertical Farcaster infra that powers far.quest & other Wield apps - with no downtime when reaching 80K+ DAU! We're here to cover core, digestible ideas that apply more to Farcaster than general infra - you should already believe in e.g. Pagerduty, alerting, monitoring, etc! If you want to learn about general infra/SRE, I recommend Google's SRE Books.Choose your fighter (database)We went with MongoDB for it's "pa...