Farcaster Devs

Reading the Snapchain doc: https://warpcast.notion.site/Snapchain-Public-0e6b7e51faf74be1846803cb74493886

Going to cast all my stupid questions in this thread as they come up 🧵👇

> Snaps are produced by hubs every 15 seconds

Does this mean any user action / delta will have a <15 second latency? So clients would optimistically display state changes before they're written to hubs?

👨‍💻 /uno and /outside, @unofficial

So a responsive app should optimistically display a user action in the UI if writing to a hub

Then reads happen from a DB that has ingested data from hubs using Shuttle?

What happens in the event that an action fails to be included on...hub? Is the UI then stuck in a bad state?

cc @cassie

most clients will display state changes from a database like Postgres or local state, very few directly react to hub events.

Working on building zkTLS infra/products. A ruthless empiricist and meme connoisseur.

http://opacity.network

You can do a hybrid PoA/PoS setup.

Hubs that trust each other can gossip messages for faster client updates, and then the network will finalize it after more slowly.

today we have a p99 target of 1min. this is hardly felt because feeds aren't regenerated instantly anyway 

our pessimistic goal for snapchain is a p99 of 15sec, our optimistic goal is sub 5s

No different than today, clients already should be creating optimistic state changes for decent UX, and usually has a backend component that is synchronizing data with hubs