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

Determine how p2p event sync should work #172

Open
Tracked by #144
ryardley opened this issue Nov 3, 2024 · 1 comment
Open
Tracked by #144

Determine how p2p event sync should work #172

ryardley opened this issue Nov 3, 2024 · 1 comment
Labels
Ciphernode Related to the ciphernode package enhancement New feature or request

Comments

@ryardley
Copy link
Contributor

ryardley commented Nov 3, 2024

This is a placeholder issue for working out how the network should manage restart during outages and retrieving historical p2p messages (not evm)

@ryardley ryardley added enhancement New feature or request Ciphernode Related to the ciphernode package labels Nov 3, 2024
@ryardley
Copy link
Contributor Author

ryardley commented Dec 17, 2024

At a guess - we should probably try something along the lines of storing a certain cache of recent messages on kademlia. There are suggestions of minimising node traffic by only gossiping message hashes between nodes whilst storing the message content on kademlia. Nodes could then either store some kind of list of historical message ids in kademlia. How this list would work I am not sure. I can imagine a hash chain should guarantee some kind of integrity acknowledging there is no consensus guarantees. The event publisher could be responsible for determining the most recent event to trail. Investigating the use of prolly trees to provide a kind of auto consensus could also be interesting.

Properties:

  • Low internode traffic
  • Some kind of historical message order
  • Avoid a single node storing the whole list

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ciphernode Related to the ciphernode package enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant