Gaotax2006 [ Feature ] Fix #1: MPC wallet with key management

[Gaotax2006]

Fixes #1, Fixes #2, Fixes #16, Fixes #17, Fixes #18, Fixes #20

Multiple switchboard feature implementations in a single batch:

Issues covered

#1 — MPC Key Management: Agent wallet using threshold MPC (N parties, t-of-n signing). No single point of failure. Supports EVM chains.

#2 — A2A Payment Protocol: Escrow-based payment protocol with PaymentRequest/PaymentProof message format, escrow contract ABI, timeout/refund flows, event monitoring.

#16 — x402 Server Middleware: Flask + FastAPI adapters that return 402 Payment Required and verify inbound PaymentPayload with nonce-based idempotency.

#17 — MPP Sessions Adapter: Tempo MPP client for streaming micro-payments under a session cap. Integrates with GasBudgetTracker for unified spend enforcement.

#18 — ElizaOS Plugin: @kcolbchain/eliza-switchboard npm package implementing IAgentPlugin with actions: createWallet, signTransaction, checkBudget, payX402, openMPPSession.

#20 — Lucidly syUSD Auto-Park: Auto-park idle USDC into Lucidly syUSD vault. Per-wallet/per-chain targets, auto-rebalance after settlement, unpark-on-demand, yield reporting.

Files changed

• switchboard/mpc_wallet.py
• switchboard/x402/server.py
• switchboard/x402/__init__.py
• switchboard/mpp/session.py
• switchboard/mpp/__init__.py
• switchboard/adapters/lucidly.py
• switchboard/__init__.py
• packages/plugin-switchboard/package.json
• packages/plugin-switchboard/tsconfig.json
• packages/plugin-switchboard/src/index.ts
• tests/test_mpc_wallet.py
• tests/test_x402_server.py
• tests/test_mpp_session.py
• tests/test_lucidly.py

Acceptance checklist

• Fix implemented as described
• Follows existing codebase conventions
• No AI training leakage markers
• No CONTRIBUTORS.json modifications
• No build artifacts committed

[abhicris]

Welcome to kcolbchain, @Gaotax2006 — glad you're here. 🌱

Here's what happens from this PR:

1. Our automated review looks for obvious issues (tests, secrets, size) within a couple of hours.
2. If it's clean and CI passes, we merge without back-and-forth.
3. If we need changes, we'll leave a specific comment — not a generic nit. Push another commit and we re-review.

While you wait:

• Run the repo's tests locally (see the repo README.md).
• Keep the PR scoped to one concern — bigger PRs land slower.
• Don't commit tokens or .env contents.

What happens after your first merge

• You're listed on https://kcolbchain.com/contributors/ (opt-out anytime via data/contributors-optout.txt).
• At 2+ merged PRs you're a Regular; at 5+ you're a Fellow — Fellows are the pool we invite first for paid research, partner-org gigs, and grant-funded work. Details: https://kcolbchain.com/docs/org-contribution-policy.html
• Looking for what to pick up next? https://kcolbchain.com/invitations/ lists open help-wanted / good-first-issue across every kcolbchain repo.

Thanks for writing the code. We're building this to last.

[Gaotax2006]

Payment address for bounty: 0x6e154f0e2c6190c18c27691537cf12a5f47d0558

(Automated payment info — replace with your preferred payout method)