8000 Mempool monitoring is dependent on single mempool · Issue #15 · RoboSats/taptrade-core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Mempool monitoring is dependent on single mempool #15

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.

Sign up for GitHub

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

Jump to bottom
Open
f321x opened this issue Aug 27, 2024 · 1 comment
Open

Mempool monitoring is dependent on single mempool #15

f321x opened this issue Aug 27, 2024 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers
Milestone
v0.1

Comments

@f321x
Copy link
Member
f321x commented Aug 27, 2024

The mempool monitoring currently uses only one mempool. This could be insecure after restarting the coordinator backend node until it has collected a sufficiently sized mempool again. To make this less risky functionality to connect to multiple backends for mempool monitoring could be introduced to have some redundancy, especially in the case of large mempools (e.g. >300mb).
@f321x f321x added enhancement New feature or request good first issue Good for newcomers labels Aug 27, 2024
@f321x f321x added this to the v0.1 milestone Aug 27, 2024
@khadar1020
Copy link

I will work on this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Milestone
v0.1
Development

No branches or pull requests
2 participants
@f321x @khadar1020
0