Collect batch fees into the builder wallet - #2635
Draft
Mirko-von-Leipzig wants to merge 4 commits into
Draft
Mirko-von-Leipzig wants to merge 4 commits into
Mirko-von-Leipzig wants to merge 4 commits into
Conversation
Mirko-von-Leipzig
added this pull request to stack #2569
September 16, 2026 08:31
Mirko-von-Leipzig
force-pushed
the
mirko/batch-fees-collection
branch
from
September 16, 2026 13:07
8895a0c to
9107378
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
The sequencer runs batch fee collection as an independent task. Each collection reads the public wallet and its unspent P2ID notes from the store, then submits an ordinary sealed transaction through the in-process RPC to consume those notes into the wallet.
The collection interval defaults to five minutes and is configurable through
--batch.builder.wallet-sync-interval. Transactions respect the protocol input-note limit and include a fee note even when fees are zero.Each transaction expires after 30 blocks. The task waits for expiration before another collection, including when submission reports an error. Each collection reads fresh chain state, so no separate account database is required.
Transaction execution runs on a blocking worker. Proving is delegated to the remote transaction prover configured with
--tx-prover.url.Part of #2501.
Changelog