alpenglow: improve certificate processing, delivery and signing persistence - #288
Merged
14 commits merged intoSep 25, 2026
Merged
14 commits merged into
14 commits merged into
Conversation
Keep full-field independent coefficients and existing verification admission. Use sequential G1/G2 MultiExp with one arithmetic task for at least 16 members, retaining the scalar path where setup costs dominate. Preserve individual fallback and failed-batch subdivision. Validate invalid members, wrong payloads and cancelling shares across both paths. Document local component and execution-contention measurements; native and live validation remain pending.
Native contention tests showed that MultiExp task handoffs can increase certificate wall time with GOMAXPROCS=1. Preserve the original scalar path there while retaining bounded MultiExp for larger batches on multi-thread runtimes. Repeat combined native race tests, adversarial tests at one and two threads, vet and build. Record both fold gains and noisy execution samples; no live voting improvement is inferred.
…rtificate-delivery
This was referenced Sep 24, 2026
7layermagik
changed the title
7layermagik
marked this pull request as draft
September 24, 2026 05:37
NeerajGodiyal
closed this pull request by merging all changes
into
alpenglow-dev
in
edd8851
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
2 participants
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.
Reduce certificate verification contention and isolate peer delivery, with signing persistence reviewed as a distinct set of commits in this PR.
Recovery contract
The durable reservation must cover a signature before signing is allowed. After an unclean restart, a valid-looking history file does not establish that every prior signing decision survived. Recovery must respect the durable upper bound and verified-finality gate. Persistence failure must not authorize further signatures. See
docs/reserved-vote-history.mdfor the protocol and failure cases.Combines #288 and #291 against
alpenglow-dev; replaces the voting portion of #279. Kept draft for explicit crash-recovery review. No signing assumptions were weakened to combine the reviews.Validation: full race suites passed on this exact source tree for alpenglow, consensus, node/config commands and blockprod. Historical Zen 5 64-vote fold: 14.2 → 6.8–7.1 ms. This is a component measurement, not proof of live FAST improvement; tests are not exhaustive power-loss conformance.