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

Sync up mempool state with the network on bootsrapping a node. #1258

Closed
goshawk-3 opened this issue Jan 24, 2022 · 1 comment · Fixed by #1398
Closed

Sync up mempool state with the network on bootsrapping a node. #1258

goshawk-3 opened this issue Jan 24, 2022 · 1 comment · Fixed by #1398
Assignees

Comments

@goshawk-3
Copy link
Contributor

Describe the bug
In Gossip Network, when a node connects to a peer at startup, it requests a full copy of the Peer's mempool state via wire message topics.Mempool.

In Kadcast network, a node should be capable of selecting N nodes randomly from the network and requests from them via NetworkService.Send method most recent mempool state.

To Reproduce
On (re)starting a node, it will not get most recent transaction from the network.

Additional context
Kadcast library should provide a new API to return a set of random addresses of active nodes.

@autholykos
Copy link
Member

Goes without saying, but the transactions in the Mempool shall also be verified upon reception

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants