hailin 51c0f59924 fix(tss): remove threshold-1 in signing to match keygen exactly ... The signing code was using thresholdT-1 while keygen was using thresholdT, causing Lagrange coefficient mismatch and "U doesn't equal T" error in round 9. Root cause: commit d0c504dc added -1 to signing threshold to "match user expectation", but this broke the keygen/sign consistency that TSS-lib requires. Changes: - tss-party/main.go: Sign now uses thresholdT (same as keygen) - pkg/tss/signing.go: Add logging, emphasize threshold must match keygen - tss-wasm/main.go: Add comment about threshold consistency NOTE: This fix maintains backward compatibility with existing wallets. No wallet regeneration is needed. ROLLBACK: If this causes issues, revert to commit before this one. Previous signing threshold was thresholdT-1 (commit d0c504dc). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>		2025-12-31 12:08:40 -08:00
..
account	Revert "fix(co-keygen): convert threshold at storage time to match tss-lib convention"	2025-12-31 10:24:25 -08:00
message-router	fix(message-router): 修复 JoinSession 代理未转发 Status 字段	2025-12-30 09:20:15 -08:00
server-party	feat(server-party): add ExecuteWithSessionInfo for co-managed keygen	2025-12-30 00:43:09 -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
server-party-co-managed	fix(server-party-co-managed): use session_started event for participants list	2025-12-30 00:52:28 -08:00
service-party-app	fix(tss): remove threshold-1 in signing to match keygen exactly	2025-12-31 12:08:40 -08:00
session-coordinator	fix(session): distinguish keygen vs sign in CanStart() and AllPartiesReady()	2025-12-31 08:34:40 -08:00
tss-wasm	fix(tss): remove threshold-1 in signing to match keygen exactly	2025-12-31 12:08:40 -08:00