🔥 Hub Update 🔥

We have a Hub testnet running with a full copy of all data! There are a few errant memory leaks and cpu issues we’re tracking down. 

Apps will be able to write directly to Hubs as early as this weekend, or pessimistically by next week.

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

@pfh @sds @adityapk @cassie and @deodad have been shipping like crazy working late nights and weekends to get this out.

They've managed to accomplish an incredible amount in the span of a few months, and their velocity in the last few weeks has been (literally) off the charts.  https://i.imgur.com/OpWQwr0.png

While speed is the right choice for now, not choosing reliability makes life harder for devs. There have been bugs and delays that we’re not proud of. 

We're going to see more of this as Hubs ship — while we’ve tested a lot, it’s still an incredibly complicated system and will take time to stabilize.

We want to thank all the developers who have been very supportive of us taking this approach. 

Thank you for the last minute upgrades to your bots, libraries and scripts to keep up with our crazy pace. We couldn’t have asked for a more supportive group of people to build with!

I also want to say that we’re going to shift the needle back pretty heavily towards reliability as hubs stabilize. 

The next chapter is about reaching scale and building the best ecosystem for developers and we’re ok moving a tiny bit slower to achieve that.

Onwards!

Top of mind for us is making the right tradeoff between speed and reliability.

We're choosing speed, because reaching credible neutrality and eliminating reliance on Warpcast is the most important thing for the health of the Farcaster protocol.

🔥🔥

Halfway through setting up Hubble on EC2, will get it running next week 🤞🏽

can’t imagine the amount of technical work that went into this — huge congrats to you and the team, pumped to start using Hubs!!