Varun Srinivasan on Warpcast

Content pfp

0 reply

20 recasts

20 reactions

Varun Srinivasan pfp

Varun Srinivasan

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

46 recasts

109 reactions

Varun Srinivasan pfp

Varun Srinivasan

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

1 recast

23 reactions

Sinaver Idrisov pfp

Sinaver Idrisov

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

jd 🌺 pfp

thanks for that additional detail. would love for you go deeper on a couple other pieces…

3 replies

0 recast

0 reaction

Susan331 pfp

0 reply

0 recast

0 reaction

ThanhC48 pfp

Thank bro, going through it soon

0 reply

0 recast

0 reaction

Asadking pfp

0 reply

0 recast

0 reaction

base.eth pfp

cảm ơn chuyên gia, tôi sẽ nghiên cứu vấn đề này

0 reply

0 recast

0 reaction

Lesha pfp

0 reply

0 recast

0 reaction

Slaveofchrist pfp

Thanks for explaining it here.

0 reply

0 recast

0 reaction

Kaifseoul pfp

0 reply

0 recast

0 reaction