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
..
deposit-order.aggregate.spec.ts	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00
deposit-order.aggregate.ts	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00
index.ts	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00
ledger-entry.aggregate.spec.ts	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00
ledger-entry.aggregate.ts	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00
settlement-order.aggregate.spec.ts	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00
settlement-order.aggregate.ts	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00
wallet-account.aggregate.spec.ts	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00
wallet-account.aggregate.ts	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00