Skip to content

Leios requirements for the transaction Mempool #1509

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

Open
nfrisby opened this issue May 14, 2025 · 0 comments
Open

Leios requirements for the transaction Mempool #1509

nfrisby opened this issue May 14, 2025 · 0 comments
Labels
leios-blocker A Leios question blocking some work

Comments

@nfrisby
Copy link
Contributor

nfrisby commented May 14, 2025

This unanswered Leios question is relevant to how the Mempool needs to change.

Image

For example, perhaps the answer is: the IB will have the RB-pointer field, and there's no limit on its age. Then today's transaction Mempool could stay the same, and the node minting an IB would simply flush it into that IB and record the "last applied block" of isLedgerState as the RB-pointer field of that IB.

But currently it's undecided, and so might need something else. For example, if the RB can't be too young, then the Mempool's syncing command should be using the youngest old-enough RB instead of simply its tip, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
leios-blocker A Leios question blocking some work
Projects
Status: 🚫 Help needed
Development

No branches or pull requests

1 participant