rwadurian/backend/mpc-system/services
hailin eb63b9341b fix(tss): correct threshold signing to support t-of-n properly
Previously, signing incorrectly required all n parties from keygen to participate. For 2-of-3 threshold, it required all 3 parties instead of just 2.

Root cause: tss.NewParameters was using len(currentSigners) instead of the original n from keygen.

Changes:
- Added TotalParties field to SigningConfig to store original n from keygen
- Modified participate_signing.go to read threshold_n from database
- Updated tss.NewParameters to use TotalParties instead of current signer count
- Added logging to show t, n, and current_signers

For 2-of-3: threshold_t=2, threshold_n=3, any 2 parties can now sign.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-12-06 07:16:24 -08:00
..
account feat(mpc-system): add event sourcing for session tracking 2025-12-05 23:31:04 -08:00
message-router fix(proto): add party_index to JoinSessionResponse for correct index assignment 2025-12-06 00:08:47 -08:00
server-party fix(tss): correct threshold signing to support t-of-n properly 2025-12-06 07:16:24 -08:00
server-party-api fix(context): use parent context instead of Background() to allow proper cancellation 2025-12-06 06:36:34 -08:00
session-coordinator fix(db): update repository to save and load delegate_party_id field 2025-12-06 05:52:34 -08:00