-
Notifications
You must be signed in to change notification settings - Fork 201
feat(l1): add cumulative balance check across sender pending txs #6606
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
ilitteri
wants to merge
2
commits into
main
Choose a base branch
from
feat/mempool-cumulative-balance
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TOCTOU between this cumulative check (mempool read lock) and the caller's later
add_transaction/add_transaction_no_broadcast(mempool write lock). Two concurrent submissions from the same sender can both pass the check independently with staleexisting_cost, then both insert, ending up above the cumulative budget.Concrete scenario: sender balance = 10. Existing pending costs = 5 (one tx). Two parallel RPC submissions of cost 3 each arrive on different worker tasks.
sum_cost_for_sender→ 5,+3 = 8 ≤ 10→ pass → write-lock-insert.sum_cost_for_sender→ 5 (still, A hasn't inserted yet),+3 = 8 ≤ 10→ pass → write-lock-insert.The existing single-tx balance check at
:2500has the same shape against the on-chain balance, so this isn't a new class of bug — but the cumulative gate's whole purpose is rate-limiting one sender, which is exactly the threat model where parallel-from-same-sender matters. Two ways to close it:add_transaction_inner— re-dosum_cost_for_senderafter acquiring the write lock. Slightly more lock time but no races.Not blocking — the window is small and only adversarial parallel submission exploits it, but worth noting for follow-up.