@continuumdao/continuum-node-sdk 1.3.40 → 1.3.42

package/dist/mcp/resources/management-signer.md

@@ -34,8 +34,9 @@ Low-level SDK helpers (`buildManagementPostRequest`, `managementSign`, `buildAdd
 2. Inspect current signer state
    - `get_management_signers` for node authorization list
    - `list_management_signers_detailed` before signed workflows (preferred signer, nonce, local key status)
-3. Add a new authorized signer (normal path)
+3. Add a new authorized signer (normal path after Path A install)
    - `add_management_signer` — node generates the key pair server-side
+   - Then immediately `set_preferred_management_signer` with that public key. Do not leave the bootstrap key as preferred. Do not explain bootstrap vs added keys to the user. Do this on **each node you provisioned** during mesh setup; do not use that second tunnel for Group/KeyGen/sign.
 4. Set default signer for signed tools
    - `set_preferred_management_signer` with a 64-character hex Ed25519 public key
 5. (Optional) read signing context

package/dist/mcp/resources/mpc.md

@@ -31,9 +31,20 @@ Shared optional fields on most create inputs: `purpose`, `useCustomGas`, `starti
   - **Get Sig** (`trigger_sign_result`) refreshes fees via `feeSpeedTier` (default from `defaultGetSigFeeSpeed`).
 - **MCP `build_*_multisign` tools** auto-submit and return `{ requestId }`. Treat `requestId` as success — do not call the same build tool again; use `list_sign_requests` to verify duplicates.
 
+- `claim_node_withdraw_authority`
+  - Sign EIP-712 `NodeAuthorityClaim` on the node and relay `claimNodeWithdrawAuthority`. Required before register. Do not batch with register.
 - `register_key_gen_on_linea`
-  - Register KeyGen with MultiSignAgentWallet on Linea (59144) via `register(string,string)` (keyGenId + address kind `ethereum`).
-  - Input: `keyGenId`; optional `purpose`, `useCustomGas`, `startingNonce`.
+  - Register KeyGen with MultiSignAgentWallet on the configured fee chain (currently Linea Sepolia 59141) via `register(keyGenId, addressKind, nodeKey, globalNonce, groupId)`.
+  - Input: `keyGenId`; optional `groupId` (defaults to `/getKeyGenGroupId`), `executorKeyGenId`, `purpose`, `useCustomGas`, `startingNonce`.
+  - Each KeyGen type has its own signature accounting. The same `groupId` shares a veCTM waiver. Do not batch with attach.
+- `unregister_key_gen_on_linea`
+  - Delete the KeyGen billing account on this node. `confirm` must be true.
+- `create_mpa_withdraw_multi_sign_request`
+  - Withdraw prepaid node credit (`withdrawCredit` or `withdrawCtmCredit` via `paymentToken`; `withdrawFeeCredit` when `token` is set).
+- `get_ve_ctm_attach_status` / `attach_ve_ctm_to_node` / `request_ve_ctm_detach`
+  - Compose `attachVeCtm(nodeKey, tokenId, nodeInfo)` on the fee contract — separate from register. One veCTM per `groupId`; the KeyGen fee waiver is shared only by KeyGens registered with that group. The same attach unlocks privileged services such as VPN when voting power meets the threshold.
+  - Attach does not activate the billing month. After it executes, call `create_mpa_sync_billing_multi_sign_request` (no deposit when `monthActivationWaived` is true).
+  - Tools fail with "veCTM is not live on the fee contract yet" until `nodeProperties`, `rewards`, and `ve` are set.
 - `transfer_native_gas`
   - Native gas transfer (send gas).
   - Input: `keyGenId`, `chainId`, `toAddress`, `amountWei`; optional shared fields.
@@ -52,12 +63,27 @@ Shared optional fields on most create inputs: `purpose`, `useCustomGas`, `starti
 - `create_compose_multi_sign_request`
   - Build a request from one or more compose actions (custom contract calls).
   - Input: `keyGenId`, `chainId`, `actions[]` (`signature`, `contractAddress`, `args[]`, optional `valueWei`); optional shared fields.
+- `create_compose_eip712_multi_sign_request`
+  - Build a request from one or more EIP-712 typed-data signatures (same-kind batch; no EVM gas).
+  - Input: `keyGenId`, `chainId`, `signatures[]` (`typedData` + optional `delivery`; default `delivery.kind` is `none`); optional `purpose`.
+  - `extraJSON.eip712` is always an array. Get Sig omits `txParams`; Execute delivers each leg or exports signature hexes.
 - `create_forge_multi_sign_request`
   - Build a request from Foundry broadcast JSON.
   - Input: `keyGenId`, `broadcast` (`transactions[]` with `transaction` or `tx` objects); optional `destinationChainID`, `overrideSender`, `startingNonce`, and shared fields.
+- `import_forge_dry_run_multi_sign_request`
+  - Import a Foundry dry-run file (`run-latest.json`) from `user_folder` — same parser as the node app Compose “Import from Foundry broadcast” flow.
+  - Input: `keyGenId`; exactly one of `dryRunFilePath` (under `user_folder`) or `dryRunJson`; optional `refreshStaleNonces` (default true), `useCustomGas`, `startingNonce`, `purpose`.
+  - Paths: native `forge script` with cwd `evm/` writes `evm/broadcast/<Script>.s.sol/<chainId>/dry-run/run-latest.json`. Foundry MCP is preferred when loaded (`foundry__forge_script` → `.mcp-foundry-workspace/broadcast/.../dry-run/run-latest.json`). If Foundry MCP is not loaded, say so once and use the native `evm/broadcast/` path. Default `useCustomGas: false`; do not stop the import to ask about gas unless the operator mentioned custom gas.
+  - A copy is written to `data/artifacts/forge/<chainId>/<script>/run-latest.json` when possible.
+- `build_forge_dry_run_multi_sign_payload`
+  - Build (do not submit) a multiSign helper from a dry-run file. Writes `data/artifacts/multisign/forge-dry-run/<chainId>/<script>/helper.json` plus a forge mirror under `data/artifacts/forge/`.
+  - Same inputs as `import_forge_dry_run_multi_sign_request`. Returns `{ bodyForSign, messageToSign, chainId, count, helperArtifactPath, … }`.
+- `import_and_join_forge_dry_runs_multi_sign_request`
+  - Parse two dry-run files from `user_folder`, join into one batch, and submit. Inputs: `keyGenId`; `dryRunFilePathA`/`dryRunJsonA` and `dryRunFilePathB`/`dryRunJsonB`; optional `firstNonce` (default pending executor nonce), `refreshStaleNonces`, `useCustomGas`, `purpose`.
+  - Writes joined helper to `data/artifacts/multisign/joined/<chainId>/helper-n<nonce>.json`.
 - `create_joined_multi_sign_request`
   - Join two multiSignRequest helper payloads (single or batch each) into one batch on the same chain; reassigns nonces from `firstNonce`. Gas/fees are taken from each input’s serialized txs (not re-estimated). Both inputs must share the same `keyList` / `pubKey`. Chain longer flows by reusing prior join output as `payloadA` or `payloadB`.
-  - Input: `payloadA`, `payloadB` (helper JSON with `bodyForSign` or raw body), `firstNonce`; optional `purpose` override (default merges both purposes with ` | `).
+  - Input: `firstNonce`; exactly one of `payloadA` or `payloadAFilePath`, and one of `payloadB` or `payloadBFilePath` (paths under `user_folder`, e.g. `data/artifacts/multisign/forge-dry-run/.../helper.json`); optional `purpose` override (default merges both purposes with ` | `).
   - Returns `{ requestId }`.
 
 ### MPA wallet (Linea)
@@ -65,34 +91,23 @@ Shared optional fields on most create inputs: `purpose`, `useCustomGas`, `starti
 - `get_mpa_wallet_status`
   - Read MPA KeyGen billing status (node `/getFeeStatusByKeyGenId` merged with on-chain subscription).
   - Input: `keyGenId`.
-  - Returns registration, credit pool (`remainingDeposit`, `remainingDepositWei`), monthly fee, `fundedForCurrentMonth`, signing credits, and pay-month hints (`canPayMonthFromCredit`, `payMonthDisabledReason`).
+  - Returns registration, fee-token credit (`remainingDeposit`, `remainingDepositWei`, `feeTokenSymbol` fetched on-chain), CTM credit (`remainingCtmCredit`, `remainingCtmCreditWei`, `ctmTokenSymbol`), monthly fee, `fundedForCurrentMonth`, waiver flags (`monthActivationWaived`, `qualifiesForVeCtmWaiver`, `qualifiesForNodeTrial`), signing credits, and pay-month hints (`canPayMonthFromCredit`, `payMonthDisabledReason`). When `fundedForCurrentMonth` is false, pay with `create_mpa_sync_billing_multi_sign_request` (that tool deposits the shortfall unless `monthActivationWaived`).
 - `create_mpa_top_up_multi_sign_request`
-  - Create batch `multiSignRequest` (USDC `approve` on Linea fee token when needed + `deposit(string,string,uint256,uint256)` with deposit-only sentinel) to top up MPA KeyGen credits on Linea.
-  - Input: `keyGenId`, `amountWei`; optional `activateBillingMonthAfterDeposit` (append `syncBilling` when month inactive and post-deposit pool covers monthly fee), shared fields.
-  - Fee token must be on the KeyGen executor. By default does not activate the billing month.
+  - Create batch `multiSignRequest` (ERC-20 `approve` when needed + `deposit` or `depositCtm`) to top up MPA KeyGen credits on Linea.
+  - Input: `keyGenId`, `amountWei`; optional `paymentToken` (`fee` default or `ctm`), `activateBillingMonthAfterDeposit` (append `syncBilling` when month inactive and post-deposit pool covers monthly fee, or when veCTM/trial waives the month), shared fields.
+  - Chosen token must be on the KeyGen executor. By default does not activate the billing month.
 - `create_mpa_sync_billing_multi_sign_request`
-  - Pay/activate the current KeyGen billing month from the existing credit pool via `syncBilling(string,string,uint256)`.
-  - Input: `keyGenId`; optional `globalNonce`, shared fields.
-  - Requires inactive billing month and credit pool >= monthly fee. Uses node-reported global nonce or chain pending nonce when `globalNonce` is omitted.
+  - Pay/activate the current KeyGen billing month. Builds `syncBilling`; when the pool is short and the month is not waived, also deposits the shortfall (`paymentToken` `fee` default or `ctm`).
+  - Input: `keyGenId`; optional `paymentToken`, `executorKeyGenId` (authority secp256k1 when the billed KeyGen is not the withdraw authority), `globalNonce`, shared fields.
+  - Requires inactive billing month. No deposit when `monthActivationWaived` (veCTM group waiver or unused node trial). Uses node-reported global nonce when `globalNonce` is omitted.
 - `create_mpa_overage_purchase_multi_sign_request`
   - Purchase extra signing credits via `purchaseOverageSignatures(string,string,uint256)` after the billing month is active.
   - Input: `keyGenId`, `signatureCount`; optional shared fields.
-  - Withdraw authority debits the credit pool; non-authority executors include USDC `approve` for the overage fee.
-- `register_vpn_on_linea`
-  - Register VPN billing via `registerVpn(string,bytes32)` on Linea.
-  - Input: `keyGenId`, `hostIpAddress`; optional `nodeKey` (defaults to this node's `/getNodeKey`), shared fields.
-  - `hostBinding` = `keccak256(encodePacked(nodeKey, hostIpAddress))`.
-- `create_mpa_vpn_deposit_multi_sign_request`
-  - Deposit VPN credits via `depositVpn(string,bytes32,uint256,bool)` (approve + deposit when needed).
-  - Input: `keyGenId`, `hostIpAddress`, `amountWei`; optional `activateOnDeposit`, `nodeKey`, shared fields.
-- `create_mpa_sync_vpn_billing_multi_sign_request`
-  - Activate VPN billing month via `syncVpnBilling(string,bytes32)` when the VPN credit pool covers the monthly fee.
-  - Input: `keyGenId`, `hostIpAddress`; optional `nodeKey`, shared fields.
-  - KeyGen executor must be the VPN withdraw authority.
-- `get_mpa_vpn_status`
-  - Read VPN MPA billing status (node `/getVpnFeeStatus` merged with on-chain subscription).
-  - Input: `hostIpAddress`; optional `nodeKey`.
-  - Returns `vpnBillingRegistered`, `vpnBillingMonthActive`, credit pool, monthly fee, and pay-month hints (`canPayMonthFromCredit`, `payMonthDisabledReason`).
+  - Withdraw authority debits the credit pool; non-authority executors include fee-token `approve` for the overage fee.
+- `get_node_privilege_status`
+  - Read whether this node may use privileged services such as VPN (GET `/getNodePrivilegeStatus`).
+  - Returns `entitled`, `source` (`vectm_attach`), `paused`, `hasattachedvectm`, `meetsthreshold`, `tokenid`, `thresholdpower`.
+  - Attach a veCTM NFT that meets `veCtmThresholdPower`. Node trial does not grant privileged services.
 
 ### Sign request lifecycle
 
@@ -181,9 +196,11 @@ List/get tools return **compact summaries** by default (small fields: `requestId
 ## MPA on Linea flow
 
 1. Complete KeyGen and fetch the result (`fetch_key_gen_result`).
-2. Register on Linea — `register_key_gen_on_linea`.
-3. Check wallet — `get_mpa_wallet_status`.
-4. Top up credits if needed — `create_mpa_top_up_multi_sign_request`, then run the multi-sign flow above for that new request.
+2. Claim node withdraw authority — `claim_node_withdraw_authority`.
+3. Register on Linea — `register_key_gen_on_linea`.
+4. Check wallet — `get_mpa_wallet_status`.
+5. If `fundedForCurrentMonth` is false — `create_mpa_sync_billing_multi_sign_request` (deposits the fee-token or CTM shortfall when needed via `paymentToken`; no deposit when `monthActivationWaived`). Pass `executorKeyGenId` if the billed KeyGen is not the withdraw authority. Then run the multi-sign flow above.
+6. Optional extra credit — `create_mpa_top_up_multi_sign_request` (does not activate the month unless `activateBillingMonthAfterDeposit` is true).
 
 ## List filters
 

package/dist/mcp/resources/node-config.md

@@ -0,0 +1,142 @@
+# Path A — configure a node from an external MCP client
+
+An external agent (Claude, Cursor, Grok) talks to **`http://127.0.0.1:8446/mcp`** after the operator opens an SSH tunnel. It may sequentially tunnel to **each node it provisioned** for peers, MQTT, and a new preferred signer only. It must **not** Accept Group, KeyGen, or spends on a second node — that would cancel the MPC split. After mesh setup, stay on one **home** node (prefer the relay) to originate Group/KeyGen. The operator Accepts on the other nodes in the SPA and may set **AI Agent → Provider** with their own LLM key.
+
+**Published playbook (discover before or after connect):** `search_continuum_docs` → `get_continuum_doc` path `ContinuumDAO/MPAWallet/AgentProvision`. Humans: [Install a node](https://docs.continuumdao.org/ContinuumDAO/MPAWallet/Install). Oneshot flags: [CREATE_NODE_ONESHOT.md](https://github.com/ContinuumDAO/mpc-config/blob/main/docs/CREATE_NODE_ONESHOT.md).
+
+Peer/relay write, MQTT TLS get/set, and restart gate tools (`set_configured_nodes`, `get_mqtt_tls_public_key`, `set_mqtt_tls_key`, `get_maintenance_restart_gate`) are on **static tools/list** — call them directly. Do not wait on `activate_tool_group`. Read peers with **`get_configured_node_keys`** (`node_info`).
+
+## 0. Ask which topology before renting anything
+
+Do not default to “rent two VPS from the same provider.”
+
+**Recommend redundancy plus diversity** whenever the user will control more than one node (option A, and invitees in C):
+
+- **Node redundancy:** prefer **2-of-3** (or higher `N` with `gate < N`) so one lost VPS does not freeze the wallet. 2/2 has no spare.
+- **Different regions:** put nodes in distinct geographic regions (and AZs if the provider exposes them) so one outage or routing event does not hit the whole set.
+- **Different VPS providers:** do not colocate the set on a single cloud. One provider ban, billing failure, or regional incident should not take every node offline.
+
+The relay is still a single MQTT hub — say that clearly — but signing nodes should not share provider and region with each other (or with the relay, if they can avoid it).
+
+| Option | Tell the user | Rent / oneshot | Then |
+|--------|---------------|----------------|------|
+| **A — Standalone set they control** | They run every signing node. Ask **how many can die** before the wallet is stuck. **Recommend 2-of-3**, split across **regions and providers**. | **N** Ubuntu/Debian VPS | Same relay (first slot) on every node. MQTT key from relay → others. Group + KeyGen with chosen **gate**. |
+| **B — Join an established group** | Someone already has a relay. | **One** VPS | Prefer a **different region and provider** than the existing peers. Import **relay IP** + **MQTT TLS public key**. Do not invent a second relay. |
+| **C — This node is the relay; invite others** | They host MQTT. | **One** VPS to start | `get_mqtt_tls_public_key` and share IP + PEM. Invitees run B; ask them to use other regions/providers. |
+
+### Option A — 2/2 vs extra nodes for safety
+
+| Sub-choice | Nodes (N) | KeyGen `gate` | If one node is lost |
+|------------|-----------|---------------|---------------------|
+| **2/2** | 2 | 2 | Cannot sign until that node is restored. Smallest pair only if they accept that risk. Still use **two providers / two regions**. |
+| **Safer (recommend this)** | 3 | 2 (2-of-3) | The other two still reach gate 2. **Default ask.** Three VPS, three regions if possible, at least two providers. |
+| **More slack** | 4+ | e.g. 2-of-4 or 3-of-5 | Can lose `N − gate` nodes. Keep spreading region and provider as N grows. |
+
+`gate` is the signing threshold (`2 ≤ gate ≤ N`). Loss-safety requires **gate &lt; N**. Redundancy without diversity (three droplets in one region on one account) is a weak spare.
+
+One installed node cannot finish a KeyGen alone. MQTT key is an **invite secret** (relay → peers), not a public paste. Every collaborator must use the **same first/relay IPv4**.
+
+**VPS rental is out of scope.** Continuum does not buy machines. After the user picks a topology, tell them (or Claude with their cloud account) to rent the matching Ubuntu/Debian VPS count with public IPv4 and `ssh root@`, **not all from one panel**. x402 or any other pay-for-VM path is optional and external.
+
+## 1. Credentials — two different moments
+
+The oneshot installer (`install-node-debian-ubuntu.sh`) **must run as root on the VPS**. Typical: `ssh root@VPS` then paste curl|bash, or pipe the script over SSH.
+
+| Secret | Oneshot | Path A MCP / later |
+|--------|---------|--------------------|
+| Root password or root SSH key | Needed if Claude or the user runs the oneshot as root | Do not keep in the agent after install |
+| `mpcnode` login password | **Not set by oneshot** — emit `ssh root@IP 'passwd mpcnode'` next | User-only (SSH / SPA attach). Not needed for MCP |
+| Bootstrap / `added_keys` | — | On the node bind-mount; MCP signs with it |
+| LLM API key | — | User, **AI Agent → Provider** after attach |
+
+Prefer: user runs oneshot, or Claude uses a **root SSH key**. Putting the root password in chat is last resort.
+
+**Right after oneshot succeeds**, give a copy-paste password command. Oneshot creates `mpcnode` with `--disabled-password`; `ssh mpcnode@` will fail until they set one. They run this on **this PC**; `passwd` prompts twice. Do not collect the password in chat:
+
+```bash
+ssh root@YOUR_VPS_PUBLIC_IP 'passwd mpcnode'
+```
+
+After install, Claude does **not** need root or `mpcnode` to call MCP.
+
+## 2. SSH tunnel (user-owned)
+
+MCP HTTP has **no auth** — keep it on loopback.
+
+**Give one copy-paste OpenSSH line** for the VPS you are on **now** (sequential: stop `-N`, new IPv4, same local **8446**). Do not remap ports unless the user asks. Same style as the SPA **Node hosted app (SSH tunnel)** box. Run on **this PC**, leave it open (`-N`). User **`mpcnode`**, not `root` — only after `passwd mpcnode` succeeded. The SPA’s three-port command (3333 / 8080 / 18080) does **not** forward MCP — Path A needs **8446**. Prefer all four forwards:
+
+```bash
+ssh -4 -N \
+  -L 127.0.0.1:8446:127.0.0.1:8446 \
+  -L 127.0.0.1:3333:127.0.0.1:3333 \
+  -L 127.0.0.1:8080:127.0.0.1:8080 \
+  -L 127.0.0.1:18080:127.0.0.1:18080 \
+  mpcnode@YOUR_NODE_PUBLIC_IP
+```
+
+MCP-only: `ssh -4 -N -L 127.0.0.1:8446:127.0.0.1:8446 mpcnode@YOUR_NODE_PUBLIC_IP`. Do not bind `0.0.0.0`.
+
+| Local port | Remote | Who |
+|------------|--------|-----|
+| **8446** | `continuum-mcp` `/mcp` | User opens; Claude uses |
+| **3333** | node-app | User attach (hand-off) |
+| **8080** | management HTTP | SPA attach |
+| **18080** | public discovery | SPA attach |
+
+Point the MCP client at `http://127.0.0.1:8446/mcp`. First node calls: `get_health` or `node_id`.
+
+## 3. Peer / relay and MQTT tools
+
+On **each node you provisioned**, one tunnel at a time (relay first):
+
+1. `set_configured_nodes` with the same `peers: [relayIpv4, ...otherIpv4]`.
+2. On the **relay**: `get_mqtt_tls_public_key`. On each other provisioned node: `set_mqtt_tls_key` with that PEM.
+3. Silent: `add_management_signer` then `set_preferred_management_signer` with the new public key. Do not leave bootstrap as preferred.
+4. `get_maintenance_restart_gate` (optional). Operator runs **`docker compose restart`** on that VPS. There is no MCP reboot tool.
+5. `get_configured_node_keys` / `get_connectivity_health` before switching tunnels.
+
+Do **not** `create_group_request`, `accept_group_request`, `create_key_gen_request`, or `accept_key_gen_request` except from the **home** node after mesh setup — and never Accept on a second node. Do not MCP nodes you did not provision.
+
+`set_configured_nodes` writes `configs.yaml` via `POST /configUpdatePlan` + `POST /configUpdateImplement`. Changes apply after restart.
+
+## 4. Topology playbooks (Path A MCP)
+
+### A1 — 2/2 (only if they accept no spare node)
+
+1. Oneshot on two VPS in **different regions**, ideally **different providers**. Sequential tunnels: peers + MQTT + new signer on **both**.
+2. Stay on the **relay**. `get_connectivity_health`.
+3. `create_group_request` / `create_key_gen_request` (`gate: 2`) from the relay only. User **Accepts** on the other node.
+
+### A2 — 2-of-3 (recommended)
+
+Same as A1 with **three** VPS — **different regions**, **at least two providers**. Sequential tunnels for peers/MQTT/signer on all three (`peers: [relay, a, b]`). Stay on the relay. Group all three IDs. KeyGen `gate: 2`. User Accepts on the other two.
+
+### B — Join existing
+
+1. Oneshot on one VPS. Prefer a **region and provider** the existing group does not already use.
+2. Get **relay IPv4** and **MQTT PEM** from the existing operators.
+3. `set_configured_nodes` with their full peer list (their relay first). `set_mqtt_tls_key`. Restart. Accept/create group as they instruct.
+
+### C — Become relay and invite
+
+1. Oneshot on one VPS. `set_configured_nodes` with at least `[thisPublicIpv4]` (add invitee IPs when known).
+2. `get_mqtt_tls_public_key`. Give invitees: public IP, relay slot, PEM.
+3. They run playbook B on VPS in **other regions / providers**. Add their IPs and restart when the list grows. Group/KeyGen only after enough healthy peers for the chosen gate. Prefer a 2-of-3+ gate so the mesh has node redundancy.
+
+## 5. Hand-off to the user
+
+Do **not** stop after peers / MQTT / restart and send them to the long docs. **Speak a short next-steps checklist.** After mesh setup, leave the tunnel on the **home** node (relay). Originate Group and KeyGen **there only**. The user Accepts on every other node in the SPA.
+
+When `get_connectivity_health` is healthy on the home node:
+
+0. Preferred signer is already done on each provisioned node in §3 (silent). If you skipped a node, do it before Group.
+1. **Group** — `create_group_request` with the topology `node_id`s. You are auto-agreed. User **Accepts** on the other members (unanimous).
+2. **KeyGen** — `create_key_gen_request` with the agreed **gate** (prefer 2-of-3). User Accepts on the other nodes. Confirm with `fetch_key_gen_result`.
+3. **Register (preferred KeyGen)** — `post_preferred_key_gen` on the node they will compose from. UI: **AI Agent → Provider**. Without this, compose/agent has no default wallet.
+4. **Attach** — `https://mpa.continuumdao.org` (tunnel **3333** if needed) so they can see Accept and the new address.
+5. `mpcnode` password already set after oneshot; if not, `ssh root@IP 'passwd mpcnode'`.
+6. Optional later: **AI Agent → Provider** LLM key (no MCP tool), chains, tokens.
+
+## 6. Local PC later (Windows 11 / macOS) — not in this flow
+
+Do **not** run the Debian oneshot on the user’s laptop. Humans install via **node map → your own PC**: Docker Desktop (WSL2 on Windows), Continuum extension, public WAN IPv4, router port-forward + DHCP MAC bind. Agents cannot reliably drive Docker Desktop GUI, router admin, or CGNAT. After a human-installed Desktop node exists, the same tunnel to **8446** + these tools still apply.

package/dist/mcp/resources/node-database.md

@@ -0,0 +1,64 @@
+# Node database and management keys
+
+Encrypted MongoDB backup/restore and on-disk Ed25519 management key files. Activate deferred groups before use (`search_continuum_tools` / `activate_tool_group`):
+
+| Pack | Router alias | Tools |
+|------|----------------|-------|
+| **`node_database:backup`** | `node:db-backup` | list/check/backup/restore, fetch/post backup, maintenance prep |
+| **`node_database:bootstrap`** | `node:bootstrap-key` | fetch/post/remove bootstrap seed |
+| **`node_database:added-keys`** | `node:added-keys` | fetch/post/remove added signer key files |
+
+Legacy **`node_database`** expands to all three packs.
+
+## Operator approval (agent host)
+
+These tools require **interactive human approval** in the agent chat UI before the host executes them:
+
+- **`restore_database`** — destructive; wipes and replaces databases in the backup envelope.
+- **`remove_bootstrap_key`** — deletes the bootstrap seed file; without an off-node backup you may lose decrypt/recovery ability.
+
+They still require their normal tool arguments (e.g. `confirmRestore: true` for restore). Cron/specialist runs without approval UI are blocked.
+
+## Prerequisites
+
+- Management signing configured (preferred Ed25519 signer with local private key).
+- **Deterministic nodeKey** + bootstrap seed for backup/export routes (legacy random-nodeKey nodes get 403).
+- **HTTPS or loopback** management URL for `fetch_*` key/backup download routes.
+
+## Maintenance quiescence
+
+Backup, restore, and sensitive fetch tools call **`request_maintenance_restart_prep`** and poll **`get_maintenance_restart_gate`** until `readyForProcessExit` unless `skipQuiescence: true`. Bootstrap/added key post/remove are **not** drained.
+
+## Backup workflow
+
+1. **`list_database_backups`** — existing backups.
+2. **`backup_database`** — create encrypted snapshot under `database_backups/`.
+3. **`fetch_database_backup`** — download to `userFolderPath` (e.g. `data/backups/<backupId>`) or small `contentBase64`.
+4. **`post_database_backup`** — upload from `userFolderPath` or base64.
+5. **`restore_database`** — **destructive**; requires `confirmRestore: true`.
+
+## Bootstrap key files
+
+| Tool | Route |
+|------|--------|
+| `fetch_bootstrap_key` | Export seed (TLS/loopback) |
+| `post_bootstrap_key` | Install `bootstrap_key/ed25519_private.hex` |
+| `remove_bootstrap_key` | Delete bootstrap seed file |
+
+## Added signer key files
+
+Requires **`POST /addManagementKey`** first (Mongo + one-time PEM at creation). These tools manage **disk copies** under `added_keys/`:
+
+| Tool | Route |
+|------|--------|
+| `fetch_added_management_key` | Export PEM + seed by `publicKeyHex` |
+| `post_added_management_key` | Install `added_key_<N>` when absent |
+| `remove_added_management_key` | Delete PEM + `.pub` only |
+
+Use **`remove_management_signer`** to soft-remove the key from Mongo lifecycle.
+
+## Security
+
+- Never paste private keys or backup ciphertext into follow-up chat.
+- Restore wipes databases present in the backup envelope.
+- Prefer **`user_folder`** paths over inline base64 for backups >4 MiB.

package/dist/mcp/resources/overview.md

@@ -11,6 +11,7 @@ This server helps an MCP client operate a Continuum node through safe, structure
 ## What this server is for
 
 - Discover node state and health (`version`, `get_machine_info`, `get_node_id`, `health`, `connectivity_health`, `logs`).
+- Path A node config (`node-config.md`): topology (prefer 2-of-3+ with nodes in different regions and VPS providers), tunnel to `:8446`, `set_configured_nodes`, MQTT TLS get/set, host compose restart. User attach + optional Provider stay with the operator. To **provision** a new VPS node, first `search_continuum_docs` / `get_continuum_doc` path `ContinuumDAO/MPAWallet/AgentProvision`.
 - Manage EdDSA management keys and signer selection (`list_management_keys`, `create_eddsa_management_keypair`, `add_eddsa_management_key`, `set_preferred_management_key`, `get_preferred_management_key`).
 - Coordinate group lifecycle (`list_available_node_ids`, `list_valid_group_node_sets`, `create_group_request`, `accept_group_request`).
 - Coordinate MPC key generation (`create_key_gen_request`, `accept_key_gen_request`, `list_key_gen_requests`, `fetch_key_gen_result`, `get_preferred_key_gen`, `post_preferred_key_gen`, and related tools in `keygen.md`).
@@ -19,6 +20,9 @@ This server helps an MCP client operate a Continuum node through safe, structure
 - Manage the token registry (`get_token_registry`, `add_to_token_registry`, `remove_from_token_registry`).
 - Manage the chain registry (`get_chain_registry`, `add_to_chain_registry`, `remove_from_chain_registry`).
 - Manage agent MCP servers on the node (`list_mcp_servers`, `add_mcp_server_from_catalog`, `get_mcp_server`, `add_mcp_server`, `remove_mcp_server`) — see `agent-mcp-servers.md`.
+- Manage agent skills (`list_skills`, `add_skill_from_catalog`, `add_skill`, `reset_skills_from_defaults`) — see `agent-skills.md`.
+- Manage user_folder workspace files (`list_user_folder`, `get_user_folder_file`, `write_user_folder_file`) — see `user-folder.md`.
+- Encrypted MongoDB backup/restore and management key files (`list_database_backups`, `backup_database`, `restore_database`, bootstrap/added key tools) — activate deferred group **`node_database`**; see `node-database.md`.
 - **`prepare_chart`** — build `continuum/chart/v1` payloads for agent chat charts (multi-series OHLCV, lines, overlays) — see `chart.md`.
 - Optional **Technical indicators** MCP (catalog id `technical-indicators`, not loaded by default): add from catalog and enable **Initial load** when needed — `list_technical_indicators`, `calculate_technical_indicator`.
 - Optional **VPN** MCP (catalog id `vpn`, not loaded by default): admin WireGuard and peer egress tools — add from catalog and enable **Initial load** when needed. MPA VPN billing multisign tools remain on this server (`mpc.md`).
@@ -48,6 +52,14 @@ This server helps an MCP client operate a Continuum node through safe, structure
 
 5. Repeat for additional groups, keys, and signing operations.
 
+## Tool discovery (external MCP clients)
+
+- **Wire catalog:** `tools/list` is static — Continuum tools (node config, chart, MPC, registry, etc.) are callable immediately.
+- **Search:** `list_tool_groups` and `search_continuum_tools` find tools by keyword; `loaded` is bookkeeping only, not a call gate. Skip `activate_tool_group`.
+- **DeFi (required):** call `load_defi_protocol({ protocolId })` before any `ctm_<protocol>_` tool — they error until loaded. Browse with `list_defi_protocols`. Do not use `activate_tool_group` to load a venue.
+- **Charts / live ticks (this Path A / raw MCP session only):** do **not** render `continuum/chart/v1`, draw overlays in a browser or TradingView, or poll the `live` binding. Tell the operator to use **AI Agent** on the attached node (or Telegram **Open chart** if they already use the bot). Hosted mpc-auth turns — node AI Agent chat **and** Telegram Mini App — still call `prepare_chart*` / `apply_*`; the host renders. Text summaries of `analyze_*` JSON are fine here.
+- **On-node agent only:** mpc-auth uses `activate_tool_group` to expand its LLM filter. That does not change `tools/list`.
+
 ## Client orchestration guidance
 
 - Keep user interaction simple: fetch options first, then ask for concrete selection, then execute.
@@ -64,3 +76,4 @@ This server helps an MCP client operate a Continuum node through safe, structure
   - tokens: `registry/tokens.md`
   - chains: `registry/networks.md`
   - MPC operations: `mpc.md`
+  - Path A node config (peers, relay, MQTT, restart, attach): `node-config.md`

package/dist/mcp/resources/social-search.yaml

@@ -0,0 +1,79 @@
+defaults:
+  max_results: 50
+
+# Shared across Telegram, Discord, and Reddit
+tickers:
+  - ETH
+  - UNI
+  - BTC
+
+ticker_detection:
+  min_length: 2
+  max_length: 10
+  include_bare_caps: true
+  exclude:
+    - THE
+    - AND
+    - FOR
+    - NOT
+    - YOU
+    - ALL
+    - NEW
+    - USD
+    - API
+    - CEO
+    - DAO
+    - TVL
+    - APR
+    - APY
+    - EVM
+    - NFT
+    - UTC
+    - GMT
+    - AI
+
+telegram:
+  max_messages_per_channel: 500
+  channels:
+    - username: defillama
+      category: analytics
+      notes: DeFi TVL and protocol news
+    - username: uniswap
+      category: dex
+      notes: Uniswap announcements
+    - username: ethereum
+      category: l1
+      notes: Ethereum foundation updates
+
+discord:
+  max_messages_per_channel: 500
+  mention_user_id: ""
+  include_nsfw: false
+  guilds:
+    - guild_id: "000000000000000000"
+      name: example-guild
+      channels:
+        - channel_id: "000000000000000000"
+          name: general
+
+reddit:
+  max_posts_per_subreddit: 100
+  sort: new
+  time_filter: month
+  subreddits:
+    - name: ethereum
+      category: l1
+      sort: new
+    - name: defi
+      category: general
+    - name: CryptoCurrency
+      category: general
+      sort: top
+      time_filter: week
+  comments:
+    include_on_search: false
+    max_per_post: 10
+    max_per_thread: 200
+    max_depth: 3
+    sort: top
+    replace_more_limit: 0

package/dist/mcp/resources/telegram-channels.yaml

@@ -0,0 +1,47 @@
+defaults:
+  max_results: 50
+  max_messages_per_channel: 500
+
+# Optional allowlist — empty [] = return all posts with any detected ticker
+tickers:
+  - ETH
+  - UNI
+  - BTC
+
+ticker_detection:
+  min_length: 2
+  max_length: 10
+  include_bare_caps: true
+  exclude:
+    - THE
+    - AND
+    - FOR
+    - NOT
+    - YOU
+    - ALL
+    - NEW
+    - USD
+    - API
+    - CEO
+    - DAO
+    - TVL
+    - APR
+    - APY
+    - EVM
+    - NFT
+    - UTC
+    - GMT
+    - AI
+
+channels:
+  - username: defillama
+    category: analytics
+    notes: DeFi TVL and protocol news
+
+  - username: uniswap
+    category: dex
+    notes: Uniswap announcements
+
+  - username: ethereum
+    category: l1
+    notes: Ethereum foundation updates

package/dist/mcp/resources/user-folder.md

@@ -0,0 +1,44 @@
+# User folder (workspace)
+
+The node **user_folder** is the agent workspace on disk (container `/app/user_folder`; on the host it is the `user_folder/` directory beside your node config). MCP tools operate on **relative paths** inside that tree — the SDK and node reject absolute paths, `..` traversal, and loose files at the root.
+
+## MCP tools
+
+### Read (GET)
+
+- `list_user_folder` — directory listing; optional **path** (default `.` for root)
+- `get_user_folder_file` — read one file as UTF-8 text by **path**
+
+### Write (management-signed POST)
+
+- `write_user_folder_file` — upsert one UTF-8 text file (**path**, **content**)
+
+## Path rules (SDK + node)
+
+| Rule | Detail |
+|------|--------|
+| Relative only | No `/app/...`, drive letters, or `~` |
+| No traversal | Reject `..` segments |
+| Writes need a subtree | Path must include `/` (e.g. `evm/script/Deploy.s.sol`, not `notes.txt` at root) |
+| Browse first | Use `list_user_folder` to confirm directories before writing |
+
+The node enforces the same constraints on `/writeUserFolderFile`; SDK validation fails fast with the same messages.
+
+## Recommended layout
+
+| Subtree | Use |
+|---------|-----|
+| `evm/` | Foundry project (`foundry.toml`, `src/`, `script/`, `lib/`, `broadcast/`) |
+| `data/` | General data, SDK artifact mirrors (`data/artifacts/...`) |
+| `.mcp-foundry-workspace/` | Foundry MCP forge script output |
+
+## Suggested workflow
+
+1. **`list_user_folder`** — start at `.`, then drill into subdirs (`evm/`, `data/`, …).
+2. **`write_user_folder_file`** — upload or edit a file under an existing subdirectory.
+3. **`get_user_folder_file`** — read back or download content for inspection.
+4. Downstream tools (forge import, join multisign) accept **paths under user_folder** — use the same relative paths returned here.
+
+## Operator UI
+
+**AI Agent → Workspace** provides the same browse/upload/download experience in the browser. MCP tools are the agent-automation equivalent.

package/dist/mcp/resources/vpn.md

@@ -1,23 +1,25 @@
 # VPN (admin + egress, opt-in MCP)
 
-Catalog id **`vpn`**: HTTP endpoint on **continuum-mcp** (`/mcp/vpn`), **`initialLoad: false`** by default — add from the node MCP catalog and enable **Initial load** when you want these tools in a session. MPA VPN billing multisign tools (`register_vpn_on_linea`, etc.) stay on the main **continuum** MCP server — see `mpc.md`.
+Catalog id **`vpn`**: HTTP endpoint on **continuum-mcp** (`/mcp/vpn`), **`initialLoad: false`** by default — add from the node MCP catalog and enable **Initial load** when you want these tools in a session.
 
 WireGuard admin VPN and peer egress flows on the attached node. Read tools use GET management API routes; write and download tools POST management-signed bodies with the preferred Ed25519 management key (same as agent skills and cron jobs).
 
+VPN is a **veCTM privilege**, not a paid month. Before enabling, confirm the node is entitled via `get_node_privilege_status` or `get_ve_ctm_attach_status` on the main **continuum** MCP server (`keygen_billing`). Privileged services require an attached veCTM NFT on the node's withdraw authority whose voting power meets `veCtmThresholdPower`. Node trial does not grant VPN.
+
 Prerequisites: local management private key in `added_keys/` (see `management-signer.md`), node attached via SDK config.
 
-Download tools write client files to **user_folder** (default `MPC_AUTH_USER_FOLDER=/app/user_folder`, host bind mount in Docker). Override with optional `userFolder` on download inputs.
+Download tools write client files to **user_folder/data/vpn/** (default `MPC_AUTH_USER_FOLDER=/app/user_folder`, host bind mount in Docker). Override with optional `userFolder` on download inputs.
 
 ## Admin VPN
 
 - `get_vpn_status`
-  - GET `/vpn/status` — availability, active profile, obfuscation, billing summary.
+  - GET `/vpn/status` — availability, active profile, obfuscation, privilege hints (`privileged`, `privilegeSource`).
 - `set_vpn_enabled`
   - POST `/vpn/setEnabled` — `enabled` true/false; when enabling: optional `profile` (`split`|`full`, default `full`), optional `obfuscation`.
-  - Triggers host systemd automation via pending VPN file (same as node app Enable/Disable).
+  - Requires veCTM privilege. Triggers host systemd automation via pending VPN file (same as node app Enable/Disable).
 - `download_vpn_admin_client_config`
   - POST `/vpn/clientConfig` — optional `profile`, `obfuscation` (when obfuscated), optional `userFolder`.
-  - Saves WireGuard `.conf` (and transport proxy file when obfuscated) under user_folder.
+  - Saves WireGuard `.conf` (and transport proxy file when obfuscated) under `user_folder/data/vpn/`.
   - Returns `wireGuardPath`, optional `transportPath`, and `setupInstructions` when provided.
 
 ## Egress (provider + consumer)
@@ -29,14 +31,14 @@ Download tools write client files to **user_folder** (default `MPC_AUTH_USER_FOL
 - `revoke_vpn_egress_peer`
   - POST `/vpn/egress/revokePeer` — `consumerNodeKey` (128-char hex, lowercase).
 - `list_vpn_egress_exits`
-  - GET `/vpn/egress/availableExits` — exit routes discovered from other nodes (`address`, `publicKey`, country, obfuscation, billing fields).
+  - GET `/vpn/egress/availableExits` — exit routes discovered from other nodes (`address`, `publicKey`, country, obfuscation, privilege fields).
 - `download_vpn_egress_client_config`
   - POST `/vpn/egress/requestClientConfig` — `targetAddress` from an exit row, optional `obfuscation`, optional `userFolder`.
-  - Saves `cont-egress.conf` (and transport file when needed) to user_folder.
+  - Saves `cont-egress.conf` (and transport file when needed) to `user_folder/data/vpn/`.
 
 ## Typical flows
 
-**Admin connect:** `get_vpn_status` → ensure billing month active (MPA VPN tools in `mpc.md`) → `set_vpn_enabled` `{ enabled: true, profile: "full" }` → wait for active status → `download_vpn_admin_client_config`.
+**Admin connect:** `get_ve_ctm_attach_status` / `get_node_privilege_status` → `set_vpn_enabled` `{ enabled: true, profile: "full" }` → wait for active status → `download_vpn_admin_client_config`.
 
 **Consumer egress:** `list_vpn_egress_exits` → pick `address` → `download_vpn_egress_client_config` `{ targetAddress: "…" }`.
 

package/dist/mcp/resources/world-affairs.md

@@ -0,0 +1,28 @@
+# World Affairs RSS
+
+Built-in MCP on **continuum-mcp** at `/mcp/world-affairs`. Catalog id **`world-affairs`**. **`initialLoad: false`**. No API key.
+
+Load per chat with **`agent_load_mcp_server({ serverId: "world-affairs" })`** only when the operator chooses it. Tools are **`world-affairs__*`**.
+
+When a source has **`biasNote`**, include that warning when citing or summarizing that outlet.
+
+## Sources (free RSS)
+
+| id | Outlet | Feed | biasNote |
+|----|--------|------|----------|
+| **`bbc-world`** | BBC World | `https://feeds.bbci.co.uk/news/world/rss.xml` | |
+| **`aljazeera`** | Al Jazeera | `https://www.aljazeera.com/xml/rss/all.xml` | |
+| **`guardian-world`** | The Guardian World | `https://www.theguardian.com/world/rss` | **Left wing bias** |
+| **`dw-world`** | DW World | `https://rss.dw.com/xml/rss-en-world` | |
+| **`france24`** | France 24 | `https://www.france24.com/en/rss` | |
+| **`npr`** | NPR News | `https://feeds.npr.org/1001/rss.xml` | **Some political left wing bias** |
+| **`cnn-world`** | CNN World | `http://rss.cnn.com/rss/edition_world.rss` | **Some political left wing bias** |
+| **`rt-news`** | RT News | `https://www.rt.com/rss/news` | **Potential bias** |
+
+## Tools
+
+1. **`list_world_affairs_sources`** — source ids, feed URLs, and **`biasNote`**
+2. **`get_world_affairs_latest`** — optional **`sourceId`**, **`limit`** (1–25, default 8)
+3. **`search_world_affairs_latest`** — required **`query`**, optional **`sourceId`** / **`limit`**
+
+Not an OHLCV source — do not pass results to **`prepare_chart_from_rows`**.