Content
@
0 reply
20 recasts
20 reactions
Varun Srinivasan
@v
One point of feedback we got on the Snapchain design doc is that we didn't fully explain why sync in the current model is a problem. @sanjay wrote up a good thread on our internal slack, which i'll try to summarize below. https://warpcast.notion.site/Snapchain-v2-Public-10e6a6c0c101807aadfacbcddda8ce4f?pvs=74
3 replies
38 recasts
86 reactions
Varun Srinivasan
@v
1. There is no source of truth to sync from. Messages can be added or removed from any node at any point in history due to the eventually consistent nature of CRDTs. Changes are gossiped out when they happen, but this could fail for a variety of reasons. The only way for a node to catch up 100% is to 1) sync with every other node and compare every message and 2) prevent messages from entering the network until this is completed. There are 4000 nodes x 150 million messages today with 100s of messages changing every second making this impossible.
1 reply
0 recast
14 reactions
jd 🌺
@jdl
thanks for that additional detail. would love for you go deeper on a couple other pieces…
3 replies
0 recast
0 reaction
Sinaver Idrisov
@sinaver.eth
on a high level the main difference with existing hubs' protocol: ordered blocks of shards which can reach consensus in parallel, but still synced fully?
0 reply
0 recast
0 reaction
IndrissaHerrerabase.eth
@indrissaherrera
Thanks for that additional detail! Like it! 🙏🏽🔥
0 reply
0 recast
0 reaction
XRP
@hitman07
Great 👍
0 reply
0 recast
0 reaction
Youngseries
@ethereum2050
Thanks for explaining it here.
0 reply
0 recast
0 reaction
Kaifseoul
@kaifseoul
🫰
0 reply
0 recast
0 reaction
Romani
@teimurazovi
V2
0 reply
0 recast
0 reaction
