feat: defer tempo expiring-nonce signing until submission - #193
Merged
Merged
Conversation
onbjerg
force-pushed
the
onbjerg/tempo-late-signing
branch
from
August 31, 2026 11:09
26f0050 to
974c431
Compare
onbjerg
changed the title
decofe
force-pushed
the
onbjerg/tempo-late-signing
branch
from
September 10, 2026 17:33
974c431 to
39e130c
Compare
onbjerg
marked this pull request as ready for review
September 11, 2026 09:46
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
1 participant
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
--late-signing-specsupport for NDJSON files and stdin pipesCompatibility
Existing signed NDJSON and existing CLI invocations remain unchanged. Absolute
valid_beforerecords retain their pre-signed behavior. Deferred relative-expiry records are supported for standard and sponsored Tempo transactions; keychain-auth records retain generation-time signing.Validation
cargo test --workspace--defer-signingand--late-signing-spec, and uses the public-mix preparation from runner PR #401 on test branch. One pair, 30 seconds, 10 validators in us-east-1, 10 accounts, 100 target TPS, 1 GiB bloat: baseline 751/751 and feature 767/767 RPC-accepted, zero failures. The previous run had 73/775 and 72/765 expiry rejections. All 45 setup transactions still completed in approximately 22.5 seconds; no setup parallelization or expiry-window increase was used. This validates the submission-expiry fix for this smoke configuration, not high-load throughput or receipt-level workload success.