chore(ntx-builder): selection and execution of sponsorship notes - #2499
Open
SantiagoPittella wants to merge 1 commit into
Open
Conversation
SantiagoPittella
force-pushed
the
santiagopittella-sponsorship-note-selection
branch
from
August 21, 2026 13:10
7418557 to
8a85630
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Part 2 of 3 for #2327
Transaction selection now works on note groups and each network note ("feature note") is selected together with the
FEE_SPONSORSHIPnotes bound to it, since a sponsorship may only be consumed in the same transaction as its feature note. Groups are packed atomically against the per-tx note budget and never split. When a feature note has more pending sponsorships than the cap (--max-sponsorships-per-note, and defaults to 3), a random subset is selected.A new
--require-sponsorshipflag (default off) gates selection for zee-fees chains. With the flag off, behavior on zero-fee chains is unchangedSince the consumability checker eliminates notes individually, the surviving ones are re-paired before execution and sponsorships whose feature note was eliminated are dropped. Failures of a sponsorship are attributed to its feature note, which carries the attempt tracking for the whole group.
Changelog