Sanjay (sanjay)

Snapchain v0.4.1 is out. We now have an install script with autoupgrade and a built in grafana dashboard like hubble. You can set it up with the following command curl -sSL https://raw.githubusercontent.com/farcasterxyz/snapchain/refs/heads/main/scripts/snapchain-bootstrap.sh | bash

• 2 replies
• 2 recasts
• 34 reactions

Just released Snapchain v0.4.0 to support this change. It will take effect on July 16th 17:00 UTC. Please upgrade your nodes before then. As part of this, we're also extending the existing storage units expiry by one year (no user action required). Snapchain has enough headroom that we don't need to expire yet.

• 2 replies
• 1 recast
• 9 reactions

Released Hubble 0.19.3 which pushes version expiry to May 15. This will be the last hubble update. If you are still running hubs, please switch to snapchain instead of upgrading. Please reach out if you run into any issues with the migration.

• 1 reply
• 2 recasts
• 25 reactions

Reminder that the replicator is deprecated by shuttle. We’re going to remove the replicator from the hub codebase by end of next week to avoid any confusion. If you’re still using the replicator, please migrate to the shuttle package. Let me know if you have any questions around migration.

• 17 replies
• 113 recasts
• 758 reactions

I was originally leaning towards account ordering. But happy with where we ended up. The biggest issue with blockchains is managing block state growth. Thanks to @cassie for inspiring the solution on how to handle this in snapchains. Also, special thanks to @vrypan.eth for the App Ordering idea.

• 3 replies
• 87 recasts
• 144 reactions

Both @neynar and @warpcast are reading/writing to Snapchain now. If you’re using Hubble, you should migrate to use snapchain exclusively and let us know if you run into any issues. https://docs.farcaster.xyz/hubble/migrating https://warpcast.notion.site/Snapchain-Mainnet-Public-1b96a6c0c101809493cfda3998a65c7a?pvs=4

• 13 replies
• 26 recasts
• 164 reactions

Since this day, we're at 50x the message count, 180x the peer count, ~40x the db size. Perf metrics are harder to compare since it was during an incident but currently p95 merge latency is ~30ms and p95 gossip delay is <1s (vs 2000ms and ~2.5hrs during the incident)

• 12 replies
• 20 recasts
• 106 reactions