rwadurian/backend/mpc-system/services/server-party
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
..
adapters/output fix(server-party): fix context leak in GetPendingMessages acknowledgment 2025-12-06 06:42:07 -08:00
application/use_cases fix(tss): correct threshold signing to support t-of-n properly 2025-12-06 07:16:24 -08:00
cmd/server fix(server-party): use parent context in event handler for proper cancellation 2025-12-06 06:39:23 -08:00
domain refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing 2025-12-05 08:11:28 -08:00
infrastructure/cache feat(mpc-system): implement delegate party for hybrid custody 2025-12-05 09:07:46 -08:00
Dockerfile chore(mpc-system): update Dockerfiles to Go 1.24 and fix line endings 2025-12-05 16:40:32 -08:00