Skip to content

Stop party updates after fatal lifecycle errors - #14

Open
mswilkison wants to merge 1 commit into
devfrom
codex/party-lifecycle
Open

mswilkison wants to merge 1 commit into
devfrom
codex/party-lifecycle

Conversation

@mswilkison

Copy link
Copy Markdown

Retain the first fatal preparation or round-processing error and stop subsequent updates from storing messages or advancing the party. Input-validation and message-storage rejections remain recoverable. Check the expected keygen commitment part count before hashing and point decoding.

Adapted from the public lifecycle and commitment checks in upstream 16938849b0f49bf925ea3902f5fab21b9ea9904b.

Validation: go test -p 1 ./tss ./ecdsa/keygen -run 'TestBaseParty|TestUnmarshalVSSCommitmentPartCount' -count=1 passed with GOMAXPROCS=2. Tests cover each fatal-error source, retained error identity, recoverable rejections, normal progression, and valid/invalid commitment shapes. Full owning suites also passed with go test -p 1 ./tss ./ecdsa/keygen ./ecdsa/signing -count=1 -timeout=30m (keygen completed in about 16 minutes). Formatting, diff checks, and independent patch review passed.

Validate ECDSA keygen decommitment part counts before hashing and point decoding.

Adapted from public upstream commit 1693884.
@piotr-roslaniec
piotr-roslaniec changed the base branch from master to dev September 14, 2026 11:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant