Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[EPIC] Head Exchange #1275

Open
3 tasks
jsimnz opened this issue Apr 1, 2023 · 0 comments
Open
3 tasks

[EPIC] Head Exchange #1275

jsimnz opened this issue Apr 1, 2023 · 0 comments
Labels
area/crdt Related to the (Merkle) CRDT system area/network Related to internal/external network components area/p2p Related to the p2p networking system feature New feature or request

Comments

@jsimnz
Copy link
Member

jsimnz commented Apr 1, 2023

Currently we don't proactively exchange heads between peers.

If a peer receives a new head, it will traverse the DAG and resolve all missing blocks. However, if a peer makes a local update offline, comes online, receives an update from another peer, it won't sync the change of its current document with the peer who just sent it the update.

So the first peer would have both updates, and the second peer would only have its own change.

This also goes towards the RPC api for the p2p system to actually implement the HeadRequest endpoint.

Tasks

@jsimnz jsimnz added feature New feature or request area/crdt Related to the (Merkle) CRDT system area/p2p Related to the p2p networking system area/network Related to internal/external network components labels Apr 1, 2023
@fredcarle fredcarle changed the title Head Exchange [EPIC] Head Exchange Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/crdt Related to the (Merkle) CRDT system area/network Related to internal/external network components area/p2p Related to the p2p networking system feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant