rwadurian/backend/mpc-system/pkg
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
..
config refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing 2025-12-05 08:11:28 -08:00
crypto refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing 2025-12-05 08:11:28 -08:00
errors refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing 2025-12-05 08:11:28 -08:00
grpcutil feat(mpc-system): integrate reliability mechanisms and enable party-driven architecture 2025-12-05 20:30:03 -08:00
jwt refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing 2025-12-05 08:11:28 -08:00
logger test(logger): set Development=true to test if it affects debug logging 2025-12-06 03:41:50 -08:00
middleware feat(mpc-system): integrate reliability mechanisms and enable party-driven architecture 2025-12-05 20:30:03 -08:00
retry feat(mpc-system): integrate reliability mechanisms and enable party-driven architecture 2025-12-05 20:30:03 -08:00
tss fix(tss): correct threshold signing to support t-of-n properly 2025-12-06 07:16:24 -08:00
utils refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing 2025-12-05 08:11:28 -08:00