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

[mempool]: investigate graph decoupling #595

Open
Mirko-von-Leipzig opened this issue Dec 19, 2024 · 0 comments
Open

[mempool]: investigate graph decoupling #595

Mirko-von-Leipzig opened this issue Dec 19, 2024 · 0 comments

Comments

@Mirko-von-Leipzig
Copy link
Contributor

The mempool's transaction and batch graphs are currently somewhat indirectly coupled.

As an example, transaction expiration is currently tracked separately in the mempool but ideally transaction and batch graphs should determine their expirations internally (see comment).

One hurdle is that the batch graph is effectively an overlay on top of the transaction graph. Which means separating them is difficult. One possible angle is to increase the richness of the graph return values, which could help the mempool react to changes in one that should impact the other.

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

No branches or pull requests

1 participant