hailin
e975e9d86c
Implement Solution 1 (Party Role Labels) to differentiate between persistent and delegate parties, with strict security guarantees for MPC threshold systems. Key Features: - PartyRole enum: persistent, delegate, temporary - K8s pod labels (party-role) for role identification - Role-based party filtering and selection - Strict persistent-only default policy (no fallback) - Optional PartyComposition for custom party requirements Security Guarantees: - Default: MUST use persistent parties (store shares in database) - Fail fast with clear error if insufficient persistent parties - No silent fallback to mixed/delegate parties - Empty PartyComposition validation prevents accidental bypass - MPC system compatibility maintained Implementation: 1. Added PartyRole type with persistent/delegate/temporary constants 2. Extended PartyEndpoint with Role field 3. K8s party discovery extracts role from pod labels (defaults to persistent) 4. Session creation logic with strict persistent requirement 5. PartyComposition support for explicit mixed-role sessions 6. K8s deployment files with party-role labels Files Modified: - services/session-coordinator/application/ports/output/party_pool_port.go - services/session-coordinator/infrastructure/k8s/party_discovery.go - services/session-coordinator/application/ports/input/session_management_port.go - services/session-coordinator/application/use_cases/create_session.go - k8s/server-party-deployment.yaml (persistent role) Files Added: - k8s/server-party-api-deployment.yaml (delegate role) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| adapters | ||
| application | ||
| cmd/server | ||
| domain | ||
| infrastructure/k8s | ||
| Dockerfile | ||