rwadurian

Commit Graph

Author	SHA1	Message	Date
hailin	c976fd3eb1	feat(mpc-system): implement party-driven architecture with SessionEvent broadcasting Fully implemented party-driven architecture according to international standards (Fireblocks, ING Bank, ZenGo patterns): Architecture Changes: - Parties actively connect to Message Router (not passively called by coordinator) - Session Coordinator publishes SessionEvents when creating sessions - Parties automatically subscribe and respond to SessionEvents - PartyID-based routing instead of network addresses New Features: 1. Session Coordinator → Message Router gRPC Client - PublishSessionEvent RPC for broadcasting session lifecycle events - Automatic event publishing after session creation 2. Message Router SessionEvent Broadcasting - SubscribeSessionEvents RPC for party subscriptions - PublishSessionEvent RPC for coordinator publishing - Targeted broadcasting to selected parties 3. Server-Party Auto-Registration & Subscription - RegisterParty on startup with role (persistent/delegate/temporary) - SubscribeSessionEvents for automatic session notifications - Event handler for automatic MPC participation Files Modified: - api/proto/message_router.proto: Added SessionEvent messages and RPCs - services/message-router/adapters/input/grpc/message_grpc_handler.go: PublishSessionEvent handler - services/session-coordinator/adapters/output/grpc/message_router_client.go: NEW - gRPC client - services/session-coordinator/application/use_cases/create_session.go: SessionEvent publishing - services/session-coordinator/cmd/server/main.go: Message Router client initialization - services/server-party/adapters/output/grpc/message_router_client.go: RegisterParty + SubscribeSessionEvents - services/server-party/cmd/server/main.go: Party registration and event subscription (commented pending full integration) - go.mod/go.sum: Updated grpc to v1.77.0 Technical Details: - gRPC streaming for SessionEvent subscriptions - Non-blocking channel broadcasts prevent slow subscribers from blocking - PartyRole support (persistent/delegate/temporary) - Join tokens distributed via SessionEvent 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-12-05 08:44:05 -08:00
hailin	747e4ae8ef	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing - Remove Address field from PartyEndpoint (parties connect to router themselves) - Update K8s Discovery to only manage PartyID and Role labels - Add Party registration and SessionEvent protobuf definitions - Implement PartyRegistry and SessionEventBroadcaster domain logic - Add RegisterParty and SubscribeSessionEvents gRPC handlers - Prepare infrastructure for party-driven MPC coordination This is the first phase of migrating from coordinator-driven to party-driven architecture following international MPC system design patterns.	2025-12-05 08:11:28 -08:00
Developer	393c0ef04d	>	2025-11-29 01:35:10 -08:00

Author

SHA1

Message

Date

hailin

c976fd3eb1

feat(mpc-system): implement party-driven architecture with SessionEvent broadcasting

Fully implemented party-driven architecture according to international standards (Fireblocks, ING Bank, ZenGo patterns):

**Architecture Changes:**
- Parties actively connect to Message Router (not passively called by coordinator)
- Session Coordinator publishes SessionEvents when creating sessions
- Parties automatically subscribe and respond to SessionEvents
- PartyID-based routing instead of network addresses

**New Features:**
1. Session Coordinator → Message Router gRPC Client
   - PublishSessionEvent RPC for broadcasting session lifecycle events
   - Automatic event publishing after session creation

2. Message Router SessionEvent Broadcasting
   - SubscribeSessionEvents RPC for party subscriptions
   - PublishSessionEvent RPC for coordinator publishing
   - Targeted broadcasting to selected parties

3. Server-Party Auto-Registration & Subscription
   - RegisterParty on startup with role (persistent/delegate/temporary)
   - SubscribeSessionEvents for automatic session notifications
   - Event handler for automatic MPC participation

**Files Modified:**
- api/proto/message_router.proto: Added SessionEvent messages and RPCs
- services/message-router/adapters/input/grpc/message_grpc_handler.go: PublishSessionEvent handler
- services/session-coordinator/adapters/output/grpc/message_router_client.go: NEW - gRPC client
- services/session-coordinator/application/use_cases/create_session.go: SessionEvent publishing
- services/session-coordinator/cmd/server/main.go: Message Router client initialization
- services/server-party/adapters/output/grpc/message_router_client.go: RegisterParty + SubscribeSessionEvents
- services/server-party/cmd/server/main.go: Party registration and event subscription (commented pending full integration)
- go.mod/go.sum: Updated grpc to v1.77.0

**Technical Details:**
- gRPC streaming for SessionEvent subscriptions
- Non-blocking channel broadcasts prevent slow subscribers from blocking
- PartyRole support (persistent/delegate/temporary)
- Join tokens distributed via SessionEvent

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

Co-Authored-By: Claude <noreply@anthropic.com>

2025-12-05 08:44:05 -08:00

hailin

747e4ae8ef

refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing

- Remove Address field from PartyEndpoint (parties connect to router themselves)
- Update K8s Discovery to only manage PartyID and Role labels
- Add Party registration and SessionEvent protobuf definitions
- Implement PartyRegistry and SessionEventBroadcaster domain logic
- Add RegisterParty and SubscribeSessionEvents gRPC handlers
- Prepare infrastructure for party-driven MPC coordination

This is the first phase of migrating from coordinator-driven to party-driven
architecture following international MPC system design patterns.

2025-12-05 08:11:28 -08:00

Developer

393c0ef04d

2025-11-29 01:35:10 -08:00

3 Commits