You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given that the bottleneck today is Bitswap, wouldn't an alternative, but temporary, solution be just opening a libp2p protocol (.dialProtocol(/peer-crdt/1.0.0) that sends the updates all together just like y.js does?
Y.js works by doing a handshake, where each side knows what's each others' latest, so that they can send only updates to each other.
Even so, I think we should create this as an alternative to the native DAG sync.
This would require a vector clock per operation (easily achievable).
Given that the bottleneck today is Bitswap, wouldn't an alternative, but temporary, solution be just opening a libp2p protocol (
.dialProtocol(/peer-crdt/1.0.0
) that sends the updates all together just like y.js does?//cc @pgte @fritzy
The text was updated successfully, but these errors were encountered: