@continuumdao/continuum-node-sdk 1.3.41 → 1.3.43

package/dist/mcp/docs/search-index.json

@@ -1,6 +1,6 @@
 {
   "version": 2,
-  "generatedAt": "2026-08-16T14:29:42.182Z",
+  "generatedAt": "2026-08-23T16:24:20.097Z",
   "pages": [
     {
       "path": "ContinuumDAO/C3Caller/C3CallerDemo",
@@ -536,19 +536,19 @@
           "id": "mission-amp-vision",
           "title": "Mission & Vision",
           "level": 2,
-          "excerpt": "The mission is to create public goods that connect all web protocols and networks in a decentralized manner. Our vision is to connect the world by building the public goods of web3. We aim to provide a fully decentralized MPC infrastructure that enables dApps on different blockchains to connect, or "
+          "excerpt": "The mission is to allow AI and humans to grow our DAO together, for the good of all of its participants and for everyone else. Our Vision is to connect the world by building a public good using our DAO and web3. We aim to allow AI to find a home in our DAO governance structure, guided by humans. The"
         },
         {
           "id": "mission",
           "title": "Mission:",
           "level": 3,
-          "excerpt": "The mission is to create public goods that connect all web protocols and networks in a decentralized manner."
+          "excerpt": "The mission is to allow AI and humans to grow our DAO together, for the good of all of its participants and for everyone else."
         },
         {
           "id": "vision",
           "title": "Vision:",
           "level": 3,
-          "excerpt": "Our vision is to connect the world by building the public goods of web3. We aim to provide a fully decentralized MPC infrastructure that enables dApps on different blockchains to connect, or to provide unique MPC related services, with trustless coordinated decision making."
+          "excerpt": "Our Vision is to connect the world by building a public good using our DAO and web3. We aim to allow AI to find a home in our DAO governance structure, guided by humans. The DAO is tasked with building tools and infrastructure based on decentralized permissionless MPC and AI, with the intention of i"
         },
         {
           "id": "continuumdao-governance-structure",
@@ -560,13 +560,13 @@
           "id": "the-continuumdao-forum",
           "title": "The ContinuumDAO Forum",
           "level": 3,
-          "excerpt": "The Forum is a Bulletin Board hosted by CTMDAO on its website at forum.continuumdao.org . It is the official record of the proceedings of ContinuumDAO. All business concerning the DAO will be documented here, including proposals, Committee proceedings, Treasury asset transfers and Guild actions. The"
+          "excerpt": "The Forum is a Bulletin Board hosted by ContinuumDAO on its website at forum.continuumdao.org . It is the official record of the proceedings of ContinuumDAO. All business concerning the DAO will be documented here, including proposals, Committee proceedings, Treasury asset transfers and Guild action"
         },
         {
           "id": "the-governance-process",
           "title": "The Governance Process",
           "level": 3,
-          "excerpt": "All proposals will appear in the Governance section of the Forum. Every veCTM holder will have access to all Governance sections in the Forum. There are only two steps of the governance process: Temperature Check & Formal Vote . Temperature Check: A proposal needs to be submitted by a wallet address"
+          "excerpt": "All proposals will appear in the Governance section of the Forum. Every Citizen veCTM holder will have access to all Governance sections in the Forum. There are only two steps of the governance process: Temperature Check & Formal Vote . Temperature Check: A proposal needs to be submitted by a wallet"
         },
         {
           "id": "the-temperature-check-proposal-template",
@@ -596,7 +596,7 @@
           "id": "continuumdao-ethics",
           "title": "ContinuumDAO ethics",
           "level": 3,
-          "excerpt": "Security Access This concerns access to social media accounts, admin access to the CTMDAO github, admin access to all areas of the Forum, other key CTMDAO related websites and root access to VPS machines. Admin signing rights for smart contracts will by governance functions in in the DAO Governor co"
+          "excerpt": "Security Access This concerns access to social media accounts, admin access to the ContinuumDAO github, admin access to all areas of the Forum, other key ContinuumDAO related websites and root access to VPS machines. Admin signing rights for smart contracts will by governance functions in in the DAO"
         }
       ],
       "excerpt": "Created time: 5th March 2026 This document is the Constitution of ContinuumDAO (CTMDAO). CTMDAO will consistently leverage the benefits of DAO governance and the unique features of MPC to ensure the stability and security of our network called the Continuum. Some of the rules and procedures in the C",
@@ -654,7 +654,7 @@
           "id": "create-a-proposal-step-by-step",
           "title": "Create a proposal (step by step)",
           "level": 2,
-          "excerpt": "1. Open Create Proposal . <img src=\"/ media/governance create proposal page.png\" alt=\"\"/ 2. Connect your wallet — the address must hold at least 1% of total vote power or 1000 veCTM vote power , whichever is higher (including delegation). 3. Title (up to 128 characters) — accurate summary; do not in"
+          "excerpt": "1. Open Create Proposal . <img src=\"/ media/governance create proposal page.png\" alt=\"\"/ 2. Connect your wallet — the address must hold at least 0.1% of total vote power or 1000 veCTM vote power , whichever is higher (including delegation). 3. Title (up to 128 characters) — accurate summary; do not "
         },
         {
           "id": "example-treasury-transfer-bravo",
@@ -720,7 +720,7 @@
           "id": "phase-2-submission-of-the-proposal-to-on-chain-governance",
           "title": "Phase 2: Submission of the Proposal to On-Chain Governance",
           "level": 3,
-          "excerpt": "After the discussion period, which could take a few days or a week or two you can proceed to the Formal Vote. The proposer will need to verify that their wallet address has at least 1% of the Vote Power, or 1000 veCTM Vote Power, whichever is higher. This can be their own voting power, or can includ"
+          "excerpt": "After the discussion period, which could take a few days or a week or two you can proceed to the Formal Vote. The proposer will need to verify that their wallet address has at least 0.1% of the Vote Power, or 1000 veCTM Vote Power, whichever is higher. This can be their own voting power, or can incl"
         },
         {
           "id": "phase-3-formal-vote",
@@ -829,12 +829,128 @@
           "id": "related",
           "title": "Related",
           "level": 3,
-          "excerpt": "Technical analysis — analysis menu on OHLCV candles Trade ideas MPC Accept/Reject loop Configure the AI harness Telegram Mini App DeFi protocol support"
+          "excerpt": "Technical analysis — analysis menu on OHLCV candles Trade ideas MPC Accept/Reject loop Configure the AI harness MCP servers Telegram Mini App DeFi protocol support"
         }
       ],
       "excerpt": "MPA wallet can plot candlestick (OHLCV) charts from the built in AI agent — in the node app Agent chat and on phones via the Telegram Mini App. Ask the agent to load a market (for example “plot ETH 4H for the last 30 days”) and open an interactive chart. Scroll and zoom the candles; default overlays",
       "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/AICharting"
     },
+    {
+      "path": "ContinuumDAO/MPAWallet/AIHarness/AgentGovernance",
+      "title": "AI-managed governance",
+      "section": "AI harness",
+      "headings": [
+        "AI-managed governance and Forum",
+        "Ask in Agent chat",
+        "Forum — read, reply, and react",
+        "Reading (no sign-in)",
+        "Writing (sign-in required)",
+        "Ideas vs formal proposals",
+        "Signing in to the Forum",
+        "Drafting a proposal with the agent",
+        "What’s new and what’s voting",
+        "Understanding proposals and vote recommendations",
+        "Submitting an on-chain proposal",
+        "Governance skills (AI Agent → Skills)",
+        "Optional automation (Cron)",
+        "veCTM and billing",
+        "Related"
+      ],
+      "sections": [
+        {
+          "id": "ai-managed-governance-and-forum",
+          "title": "AI-managed governance and Forum",
+          "level": 2,
+          "excerpt": "ContinuumDAO is an AI first DAO managed by both people and AI agents. veCTM holders — including MPA wallet operators who attach voting power to their node — govern the protocol through the Forum, on chain proposals, and votes. Agents can research, draft, discuss, and recommend votes; humans stay in "
+        },
+        {
+          "id": "ask-in-agent-chat",
+          "title": "Ask in Agent chat",
+          "level": 3,
+          "excerpt": "Describe what you want in plain language — for example: “What new proposals are there?” / “What’s voting on ContinuumDAO right now?” “Summarize the newest governance proposals I should look at.” “Read Forum thread 123 and summarize the debate.” “Post this as an Idea in Ideas & Suggestions.” “Help me"
+        },
+        {
+          "id": "forum-read-reply-and-react",
+          "title": "Forum — read, reply, and react",
+          "level": 3,
+          "excerpt": "The agent can use forum.continuumdao.org on your behalf through continuum Forum tools. What you can ask What the agent does Open a thread by URL or id Fetches the opening post and replies (paginated) Read one post Fetches that post by id Search or recent posts Searches keywords or lists recent Forum"
+        },
+        {
+          "id": "reading-no-sign-in",
+          "title": "Reading (no sign-in)",
+          "level": 4,
+          "excerpt": "What you can ask What the agent does Open a thread by URL or id Fetches the opening post and replies (paginated) Read one post Fetches that post by id Search or recent posts Searches keywords or lists recent Forum activity Unread while signed in Lists NodeBB unread threads; mark read/unread on reque"
+        },
+        {
+          "id": "writing-sign-in-required",
+          "title": "Writing (sign-in required)",
+          "level": 4,
+          "excerpt": "To create a topic , reply , or react with emojis, your KeyGen must sign in to the Forum first — see Signing in to the Forum below. Action Plain language examples Idea (early feedback) “Post this as an Idea in Ideas & Suggestions.” Governance thread (before on chain) “Open a Treasury Governance threa"
+        },
+        {
+          "id": "ideas-vs-formal-proposals",
+          "title": "Ideas vs formal proposals",
+          "level": 3,
+          "excerpt": "Path Forum On chain propose? Idea / early feedback Ideas & Suggestions No — discussion only Formal proposal Matching Governance category, then on chain submit Yes — after Temperature Check / vote rules Ideas are for brainstorming. A formal on chain proposal must link to a dedicated Governance thread"
+        },
+        {
+          "id": "signing-in-to-the-forum",
+          "title": "Signing in to the Forum",
+          "level": 3,
+          "excerpt": "Before the agent can post on the Forum, your KeyGen must sign in . That is an off chain signature , not an on chain transaction — same compose sign request flow as other typed data signatures: peers Accept on Join, then you Execute . 1. Your KeyGen needs enough veCTM voting power (from a lock or fro"
+        },
+        {
+          "id": "drafting-a-proposal-with-the-agent",
+          "title": "Drafting a proposal with the agent",
+          "level": 3,
+          "excerpt": "Ask the agent to help you compose a proposal — for example, “Walk me through a Treasury proposal to fund X.” Enable skill continuum dao compose proposal under AI Agent → Skills (interactive only — never on cron). Typical flow: 1. Classify Idea vs proposal — early feedback → Idea only; ready for Temp"
+        },
+        {
+          "id": "what-s-new-and-what-s-voting",
+          "title": "What’s new and what’s voting",
+          "level": 3,
+          "excerpt": "You do not need to open the Governance app first. Ask in Agent chat (or Telegram) — for example: “What new proposals are there?” “Which proposals are Active and need a vote?” “Anything new since last week?” The agent checks live on chain state (not the backend alone), lists proposals in the current "
+        },
+        {
+          "id": "understanding-proposals-and-vote-recommendations",
+          "title": "Understanding proposals and vote recommendations",
+          "level": 3,
+          "excerpt": "Ask the agent to explain live or past proposals and recommend a vote — for example, “Should I vote For on proposal 7?” Enable continuum dao proposals and continuum dao vote policy (and continuum dao proposal standards for Constitution checks). The agent will: 1. Fetch on chain detail — actions, prop"
+        },
+        {
+          "id": "submitting-an-on-chain-proposal",
+          "title": "Submitting an on-chain proposal",
+          "level": 3,
+          "excerpt": "1. Sign in to the Forum (above) if the agent will create the thread. 2. Open a Governance thread in the category matching the proposal type. Keep that thread’s link. 3. Ask the agent to submit — title, on chain actions, Forum link; Bravo for most types, Delta for elections/multi option. 4. Accept on"
+        },
+        {
+          "id": "governance-skills-ai-agent-skills",
+          "title": "Governance skills (AI Agent → Skills)",
+          "level": 3,
+          "excerpt": "Load per chat or enable Initial load only where noted. All are under agent llm config/Skills/ in mpc config. Skill Use Cron? continuum dao proposals List/explain live proposals; read Forum threads, posts, search Read only in cron continuum dao proposal standards Constitution Vision/Mission + type fi"
+        },
+        {
+          "id": "optional-automation-cron",
+          "title": "Optional automation (Cron)",
+          "level": 3,
+          "excerpt": "Under AI Agent → Cron , add jobs from the repository catalog. Governance related jobs (default disabled ): Job Purpose appraise and vote proposals Appraise Active proposals; cast votes matching votePolicy ; optional telegramNotify . Vote only — never propose. conditional accept governance vote Join "
+        },
+        {
+          "id": "vectm-and-billing",
+          "title": "veCTM and billing",
+          "level": 3,
+          "excerpt": "veCTM on your node — lock, attach, delegation, detach through governance. MPA billing — withdraw authority and Linea registration before billable governance signatures count correctly."
+        },
+        {
+          "id": "related",
+          "title": "Related",
+          "level": 3,
+          "excerpt": "MPC Accept/Reject loop Configure the AI harness MCP servers Plan mode How To Write a Proposal mpc config skills: Skills README"
+        }
+      ],
+      "excerpt": "ContinuumDAO is an AI first DAO managed by both people and AI agents. veCTM holders — including MPA wallet operators who attach voting power to their node — govern the protocol through the Forum, on chain proposals, and votes. Agents can research, draft, discuss, and recommend votes; humans stay in ",
+      "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/AIHarness/AgentGovernance"
+    },
     {
       "path": "ContinuumDAO/MPAWallet/AIHarness/Configure",
       "title": "Configure the AI harness",
@@ -871,7 +987,7 @@
           "id": "3-variables-mcp-servers-and-default-search",
           "title": "3. Variables, MCP servers, and default search",
           "level": 3,
-          "excerpt": "1. Open AI Agent → MCP Servers . 2. Ensure the built in continuum (wallet) server is enabled. 3. Add catalog or third party MCP servers as needed (market data, DeFi, browser / search tools, and so on). 4. Open AI Agent → Variables and enter API keys and secrets for those servers (and the LLM if prom"
+          "excerpt": "1. Open AI Agent → MCP Servers . 2. Ensure the built in continuum (wallet) server is enabled. 3. Add catalog or third party MCP servers as needed (market data, DeFi, browser / search tools, and so on). Repository hosted servers ( coinmarketcap public , coinbase public , business latest , world affai"
         },
         {
           "id": "4-optional-telegram-on-your-phone",
@@ -883,18 +999,85 @@
           "id": "5-optional-next",
           "title": "5. Optional next",
           "level": 3,
-          "excerpt": "Skills — steer agent behaviour ( AI Agent → Skills ). Cron — scheduled agent turns ( AI Agent → Cron ). Other webhooks — GitHub, Stripe, and similar ( AI Agent → Webhooks ). Workspace — upload or edit scripts and data on the node ( AI Agent → Workspace ); useful for Foundry script batches and JSON i"
+          "excerpt": "Skills — steer agent behaviour ( AI Agent → Skills ). For DAO: proposal drafting, standards checks, vote policy, Forum inbox — see Governance skills. Cron — scheduled agent turns ( AI Agent → Cron ). Governance jobs (vote appraisal, governor Join Accept/Reject, Forum reply Telegram) — Optional autom"
         },
         {
           "id": "related",
           "title": "Related",
           "level": 3,
-          "excerpt": "MPC Accept/Reject loop AI harness overview Default Ed25519 signer Telegram Mini App KeyGens Trade ideas Overview Operator detail: Agent hooks"
+          "excerpt": "MPC Accept/Reject loop AI harness overview MCP servers Plan mode AI managed governance Default Ed25519 signer Telegram Mini App KeyGens Trade ideas Overview Operator detail: Agent hooks"
         }
       ],
       "excerpt": "This checklist is optional . You can run an MPA wallet entirely from the node app (Groups, KeyGens, multi sign) without an AI agent. The MPA wallet is AI first , though, so most users will want to complete these steps once a KeyGen exists. Use this flow after you have Configured Nodes, a Group, and ",
       "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/AIHarness/Configure"
     },
+    {
+      "path": "ContinuumDAO/MPAWallet/AIHarness/McpServers",
+      "title": "MCP servers",
+      "section": "AI harness",
+      "headings": [
+        "MCP servers",
+        "How MCP servers work on your node",
+        "Official docs on **`continuum`** (`search_continuum_docs`)",
+        "Built-in `continuum` MCP (wallet + node)",
+        "Forum and governance on **`continuum`**",
+        "Repository servers on **continuum-mcp**",
+        "Other repository catalog entries (third-party runtimes)",
+        "Related"
+      ],
+      "sections": [
+        {
+          "id": "mcp-servers",
+          "title": "MCP servers",
+          "level": 2,
+          "excerpt": "Every MPC node ships an AI agent harness that can call MCP servers — tool packs the agent loads for wallet actions, charts, research, Foundry, and more. This page covers ContinuumDAO repository MCP servers (built into the node image). Third party catalog entries (Brave Search, Tavily, Alpaca, and si"
+        },
+        {
+          "id": "how-mcp-servers-work-on-your-node",
+          "title": "How MCP servers work on your node",
+          "level": 3,
+          "excerpt": "Layer What it is Built in continuum Wallet and node MCP on the management API ( /mcp ). Always available; initialLoad: true at chat startup. Repository catalog Templates from mpc config MCP servers.json . Add with Add from repository in the UI. Default active mpc config MCP default servers.json seed"
+        },
+        {
+          "id": "official-docs-on-continuum-search-continuum-docs",
+          "title": "Official docs on `continuum` (`search_continuum_docs`)",
+          "level": 3,
+          "excerpt": "The built in continuum MCP server can read this documentation site (docs.continuumdao.org) — the same content you are reading now. Tool Use search continuum docs Ranked search by keyword (returns path , optional sectionId , excerpt, public URL) get continuum doc Fetch markdown for a path (e.g. Conti"
+        },
+        {
+          "id": "built-in-continuum-mcp-wallet-node",
+          "title": "Built-in `continuum` MCP (wallet + node)",
+          "level": 3,
+          "excerpt": "The continuum server is the agent’s primary wallet interface. It is not on the separate continuum mcp HTTP sidecar — it runs on your node’s management MCP endpoint. Always on capabilities Groups, KeyGens, contacts, chain registry Multi sign lifecycle: list / agree / Get Sig / Execute / History DeFi "
+        },
+        {
+          "id": "forum-and-governance-on-continuum",
+          "title": "Forum and governance on `continuum`",
+          "level": 3,
+          "excerpt": "ContinuumDAO protocol tools load through load defi protocol with continuum dao (the agent does this automatically when you ask about governance). They cover forum.continuumdao.org and Linea governance — same MPC loop as DeFi. Operator guide (plain language): AI managed governance and Forum. Area Cap"
+        },
+        {
+          "id": "repository-servers-on-continuum-mcp",
+          "title": "Repository servers on continuum-mcp",
+          "level": 3,
+          "excerpt": "These MCP servers are implemented in continuum node sdk and run in the continuum mcp sidecar inside the node app image ( http://continuum mcp:8446/... ). Catalog ids match MCP servers.json / MCP default servers.json . Catalog id Endpoint API key Typical use coinmarketcap public /mcp/cmc public None "
+        },
+        {
+          "id": "other-repository-catalog-entries-third-party-runtimes",
+          "title": "Other repository catalog entries (third-party runtimes)",
+          "level": 3,
+          "excerpt": "The same Add from repository flow activates servers defined in MCP servers.json that call external or npx/uv runtimes — for example: Category Example catalog ids Search / browser duckduckgo , brave search , google search , exa , tavily , kagi , serpapi , perplexity , mullvad browser , gecko , firefo"
+        },
+        {
+          "id": "related",
+          "title": "Related",
+          "level": 3,
+          "excerpt": "Configure the AI harness AI harness overview Compose transaction flow DeFi protocol support AI charting Plan mode AI managed governance Agent facing server reference: continuum node sdk agent mcp servers.md"
+        }
+      ],
+      "excerpt": "Every MPC node ships an AI agent harness that can call MCP servers — tool packs the agent loads for wallet actions, charts, research, Foundry, and more. This page covers ContinuumDAO repository MCP servers (built into the node image). Third party catalog entries (Brave Search, Tavily, Alpaca, and si",
+      "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/AIHarness/McpServers"
+    },
     {
       "path": "ContinuumDAO/MPAWallet/AIHarness/Overview",
       "title": "Overview",
@@ -905,6 +1088,7 @@
         "How you talk to it",
         "What it can do",
         "Chat and Plan modes",
+        "AI-managed governance (ContinuumDAO)",
         "Built-in MCP (wallet)",
         "Built-in DeFi / web3 protocols",
         "Charting and technical analysis",
@@ -939,19 +1123,25 @@
           "id": "what-it-can-do",
           "title": "What it can do",
           "level": 3,
-          "excerpt": "Interactive chat for questions and actions. Plan mode lets the agent propose multi step work, then execute when you approve. The built in continuum MCP server exposes wallet and node tools: groups, KeyGens, sign requests, messaging, and related management actions. Protocol interactions (swaps, lendi"
+          "excerpt": "Interactive chat for questions and actions. Plan mode lets the agent propose multi step work, then execute when you approve. See Plan mode. With veCTM voting power, your agent can list new and live proposals , read the Forum , post Ideas and Governance threads, draft and check proposals against the "
         },
         {
           "id": "chat-and-plan-modes",
           "title": "Chat and Plan modes",
           "level": 4,
-          "excerpt": "Interactive chat for questions and actions. Plan mode lets the agent propose multi step work, then execute when you approve."
+          "excerpt": "Interactive chat for questions and actions. Plan mode lets the agent propose multi step work, then execute when you approve. See Plan mode."
+        },
+        {
+          "id": "ai-managed-governance-continuumdao",
+          "title": "AI-managed governance (ContinuumDAO)",
+          "level": 4,
+          "excerpt": "With veCTM voting power, your agent can list new and live proposals , read the Forum , post Ideas and Governance threads, draft and check proposals against the Constitution, explain what is on chain, and recommend votes from your policy — then prepare propose/vote sign requests under your MPC thresh"
         },
         {
           "id": "built-in-mcp-wallet",
           "title": "Built-in MCP (wallet)",
           "level": 4,
-          "excerpt": "The built in continuum MCP server exposes wallet and node tools: groups, KeyGens, sign requests, messaging, and related management actions."
+          "excerpt": "The built in continuum MCP server exposes wallet and node tools: groups, KeyGens, sign requests, messaging, Forum and governance , and related management actions. See MCP servers."
         },
         {
           "id": "built-in-defi-web3-protocols",
@@ -969,7 +1159,7 @@
           "id": "third-party-mcp-servers",
           "title": "Third-party MCP servers",
           "level": 4,
-          "excerpt": "Add other MCP servers under Node → AI Agent → MCP Servers (catalog or custom). Store their API keys in Variables ."
+          "excerpt": "Add other MCP servers under Node → AI Agent → MCP Servers (catalog or custom). Store their API keys in Variables . ContinuumDAO repository MCP servers (built in continuum , continuum mcp OHLCV/news/TA/VPN, and the full catalog) are documented in MCP servers."
         },
         {
           "id": "skill-files",
@@ -981,7 +1171,7 @@
           "id": "workspace-scripts-and-data",
           "title": "Workspace (scripts and data)",
           "level": 4,
-          "excerpt": "Node → AI Agent → Workspace lets you browse and manage the node user folder : create directories, add or edit files, and download copies locally. Use it to upload Foundry scripts , JSON inputs, and other artefacts the agent or Foundry MCP can run — see Foundry script — Workspace tab."
+          "excerpt": "Node → AI Agent → Workspace lets you browse and manage the node user folder : create directories, add or edit files, and download copies locally. Writes must go in a subtree (not the folder root). Put Foundry / Solidity work under evm/ ( foundry.toml , src/ , script/ , lib/ , out/ , broadcast/ ). Ot"
         },
         {
           "id": "cron-scheduled-jobs",
@@ -1005,12 +1195,65 @@
           "id": "related",
           "title": "Related",
           "level": 3,
-          "excerpt": "MPC Accept/Reject loop Configure the AI harness Telegram Mini App Default Ed25519 signer Trade ideas Overview Operator detail: Agent hooks"
+          "excerpt": "MPC Accept/Reject loop Configure the AI harness MCP servers Plan mode AI managed governance Telegram Mini App Default Ed25519 signer Trade ideas Overview Operator detail: Agent hooks"
         }
       ],
       "excerpt": "The MPA wallet is AI first , and every node includes a dedicated AI agent harness . You do not install a separate agent product — the harness is part of the node. Configuring it is optional . You can control Groups, KeyGens, and signing entirely from the node app UI. For most users, linking an LLM a",
       "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/AIHarness/Overview"
     },
+    {
+      "path": "ContinuumDAO/MPAWallet/AIHarness/PlanMode",
+      "title": "Plan mode",
+      "section": "AI harness",
+      "headings": [
+        "Plan mode",
+        "Plan mode vs ordinary chat",
+        "What it is good for",
+        "How to use it",
+        "After a plan runs",
+        "Related"
+      ],
+      "sections": [
+        {
+          "id": "plan-mode",
+          "title": "Plan mode",
+          "level": 2,
+          "excerpt": "Plan mode is for work that takes several steps — research a market, compare yield options, sketch a trade idea, review a portfolio, or explore a governance topic — before anything runs on your wallet. You and the agent draft the plan together in a private Plan chat. When you are happy with it, you E"
+        },
+        {
+          "id": "plan-mode-vs-ordinary-chat",
+          "title": "Plan mode vs ordinary chat",
+          "level": 3,
+          "excerpt": "You can ask the agent to do almost anything in ordinary Agent chat — including work that spans multiple sessions , each with its own context . For example, you might say “research this today and we’ll pick it up tomorrow in a new chat,” or ask the agent to split a large task into separate threads. T"
+        },
+        {
+          "id": "what-it-is-good-for",
+          "title": "What it is good for",
+          "level": 3,
+          "excerpt": "Plan type Examples Market / trade “Research ETH perps and draft a trade suggestion with risk notes.” Yield “Compare lending venues for USDC on Linea and outline steps.” Research “Summarize recent news and chart context before we decide.” Portfolio “Review positions and suggest rebalancing themes.” D"
+        },
+        {
+          "id": "how-to-use-it",
+          "title": "How to use it",
+          "level": 3,
+          "excerpt": "1. Start a plan — in Agent chat, choose New plan and pick a starter (market, yield, research, portfolio, DAO, or custom). On Telegram you can start a plan from New plan beside New chat . 2. Describe the goal — talk through what you want in plain language. The agent turns that into a readable plan yo"
+        },
+        {
+          "id": "after-a-plan-runs",
+          "title": "After a plan runs",
+          "level": 3,
+          "excerpt": "Continue the conversation — use After orchestration → Continue in Orchestrator chat to follow up on the same run (for example adjust gas, sign, or schedule the next step). Plan follow on — start a new plan that builds on an earlier run without re explaining everything from scratch. Find past runs — "
+        },
+        {
+          "id": "related",
+          "title": "Related",
+          "level": 3,
+          "excerpt": "AI harness overview Configure the AI harness MPC Accept/Reject loop AI managed governance Telegram Mini App"
+        }
+      ],
+      "excerpt": "Plan mode is for work that takes several steps — research a market, compare yield options, sketch a trade idea, review a portfolio, or explore a governance topic — before anything runs on your wallet. You and the agent draft the plan together in a private Plan chat. When you are happy with it, you E",
+      "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/AIHarness/PlanMode"
+    },
     {
       "path": "ContinuumDAO/MPAWallet/AIHarness/TelegramMiniApp",
       "title": "Telegram Mini App",
@@ -1020,6 +1263,7 @@
         "What you need",
         "Setup (high level)",
         "Free vs paid ngrok",
+        "Operator notifications and cron",
         "Using the Mini App",
         "Related"
       ],
@@ -1048,6 +1292,12 @@
           "level": 3,
           "excerpt": "Basic usage does not require a paid ngrok plan. A free Agent Endpoint is enough for bot chat. Capability Free ngrok Paid ngrok (reserved domain) Bot chat, analysis menus, trade ideas / builds Yes Yes Chart preview in chat (text / sparkline) Yes Yes Interactive Open chart Telegram Mini App No — ngrok"
         },
+        {
+          "id": "operator-notifications-and-cron",
+          "title": "Operator notifications and cron",
+          "level": 3,
+          "excerpt": "Besides inbound bot chat, your node can send Telegram messages to you : Mechanism Use send telegram message (continuum MCP) Agent sends a proactive DM from chat (e.g. alert, summary) Cron telegramNotify: true After a successful cron turn, the host DMs the final assistant message to your operator cha"
+        },
         {
           "id": "using-the-mini-app",
           "title": "Using the Mini App",
@@ -1058,12 +1308,160 @@
           "id": "related",
           "title": "Related",
           "level": 3,
-          "excerpt": "AI harness overview Configure the AI harness AI charting Technical analysis Trade ideas Default Ed25519 signer Operator guide: Telegram webhook via ngrok"
+          "excerpt": "AI harness overview Configure the AI harness AI managed governance Plan mode AI charting Technical analysis Trade ideas Default Ed25519 signer Operator guide: Telegram webhook via ngrok"
         }
       ],
       "excerpt": "Talk to your node’s built in AI agent from Telegram on your phone. This is the same harness as Agent chat in the node app — not a separate agent. Harness overview: AI harness overview. Finish Configure the AI harness (at least LLM + preferred KeyGen) before relying on Telegram for wallet actions. A ",
       "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/AIHarness/TelegramMiniApp"
     },
+    {
+      "path": "ContinuumDAO/MPAWallet/AgentProvision",
+      "title": "Agent provision and configure",
+      "section": "Further reading (operators / APIs)",
+      "headings": [
+        "Agent provision and configure",
+        "How an AI agent discovers this page",
+        "0. Ask which topology before renting anything",
+        "Option A — 2/2 vs extra nodes for safety",
+        "1. One-shot VPS install (as root)",
+        "1b. Set the `mpcnode` login password (required before the tunnel)",
+        "2. Tunnels: mesh setup vs wallet control",
+        "3. Configure peers, MQTT, and signer (each node you provisioned)",
+        "4. Topology playbooks (after oneshot)",
+        "5. Hand-off to the user",
+        "Related"
+      ],
+      "sections": [
+        {
+          "id": "agent-provision-and-configure",
+          "title": "Agent provision and configure",
+          "level": 2,
+          "excerpt": "If you are an AI agent (Claude, Cursor, Grok, or similar) asked to create an MPC node , install a node , provision a VPS , or fully configure a Continuum MPA node, this page is the playbook . Do not start from the long manual Running an MPC Node page. Humans installing interactively should use Insta"
+        },
+        {
+          "id": "how-an-ai-agent-discovers-this-page",
+          "title": "How an AI agent discovers this page",
+          "level": 3,
+          "excerpt": "1. Call search continuum docs with queries such as provision node , create mpc node , install node agent , or configure peers MQTT . 2. Follow the hit for this page: get continuum doc with path ContinuumDAO/MPAWallet/AgentProvision . 3. Crawlers and other clients: start at llms.txt and llm index.jso"
+        },
+        {
+          "id": "0-ask-which-topology-before-renting-anything",
+          "title": "0. Ask which topology before renting anything",
+          "level": 3,
+          "excerpt": "Do not default to “rent two VPS from the same provider.” Continuum does not buy machines (no x402 / Hetzner / DigitalOcean integration here). After the user picks a topology, tell them to rent the matching Ubuntu or Debian VPS count with public IPv4 and ssh root@ . Recommend redundancy plus diversit"
+        },
+        {
+          "id": "option-a-2-2-vs-extra-nodes-for-safety",
+          "title": "Option A — 2/2 vs extra nodes for safety",
+          "level": 4,
+          "excerpt": "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 po"
+        },
+        {
+          "id": "1-one-shot-vps-install-as-root",
+          "title": "1. One-shot VPS install (as root)",
+          "level": 3,
+          "excerpt": "On each new Ubuntu/Debian VPS, run the one shot installer as root ( ssh root@… ). Full flags and restore notes: CREATE NODE ONESHOT.md. bash curl fsSL \"https://raw.githubusercontent.com/ContinuumDAO/mpc config/main/scripts/install node debian ubuntu.sh\" \\ bash s \\ node mgt key \"0xYour40HexCharacters"
+        },
+        {
+          "id": "1b-set-the-mpcnode-login-password-required-before-the-tunnel",
+          "title": "1b. Set the `mpcnode` login password (required before the tunnel)",
+          "level": 3,
+          "excerpt": "Oneshot creates OS user mpcnode ( adduser disabled password , sudo + docker group). It does not set a login password (passwords must not go through curl bash). Until the user sets one, ssh mpcnode@… will fail. Immediately after oneshot succeeds , give this copy paste line (substitute the VPS IPv4). "
+        },
+        {
+          "id": "2-tunnels-mesh-setup-vs-wallet-control",
+          "title": "2. Tunnels: mesh setup vs wallet control",
+          "level": 3,
+          "excerpt": "You may MCP each node you provisioned , but only for host mesh setup . Do not Accept Group, KeyGen, or spends on more than one node. That would let one agent complete the threshold and cancel MPC. Allowed on every node you oneshot Never on a second node Peers ( set configured nodes ) create group re"
+        },
+        {
+          "id": "3-configure-peers-mqtt-and-signer-each-node-you-provisioned",
+          "title": "3. Configure peers, MQTT, and signer (each node you provisioned)",
+          "level": 3,
+          "excerpt": "Activate tool group node config ( activate tool group ). Read peers with get configured node keys . Tool detail lives on the node as MCP resource node config docs . Walk the nodes one tunnel at a time (relay first): 1. set configured nodes with the same peers: [relayIpv4, ...otherIpv4] on each. Defa"
+        },
+        {
+          "id": "4-topology-playbooks-after-oneshot",
+          "title": "4. Topology playbooks (after oneshot)",
+          "level": 3,
+          "excerpt": "A1 — 2/2 (only if they accept no spare): oneshot on two VPS in different regions , ideally different providers . Sequential tunnels: peers + MQTT + new signer on both . Then stay on the relay . Originate Group both node id s and KeyGen gate: 2 . User Accepts on the other node in the wallet website. "
+        },
+        {
+          "id": "5-hand-off-to-the-user",
+          "title": "5. Hand-off to the user",
+          "level": 3,
+          "excerpt": "Do not stop after peers / MQTT / restart and point them at the long docs. Say the remaining wallet steps out loud (a short checklist). After §3, leave the tunnel on the home node (relay). Originate Group and KeyGen there only . The user Accepts on every other node in the wallet website. When the hom"
+        },
+        {
+          "id": "related",
+          "title": "Related",
+          "level": 3,
+          "excerpt": "Install a node — humans (node map) + short agent pointer CREATE NODE ONESHOT.md — VPS install script only Configured Nodes Groups KeyGens Attach your node Configure the AI harness — optional, after KeyGen"
+        }
+      ],
+      "excerpt": "<! agent: task: provision and configure mpc node audience: [ai agent] oneshot script: https://raw.githubusercontent.com/ContinuumDAO/mpc config/main/scripts/install node debian ubuntu.sh oneshot doc: https://github.com/ContinuumDAO/mpc config/blob/main/docs/CREATE NODE ONESHOT.md agents md: https://",
+      "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/AgentProvision"
+    },
+    {
+      "path": "ContinuumDAO/MPAWallet/AssetManagement",
+      "title": "Asset management",
+      "section": "Using an MPA wallet",
+      "headings": [
+        "Asset management",
+        "Asset rows (Assets tab)",
+        "Protocol modals — unified experience",
+        "Tokens dialog (add / remove assets)",
+        "Example — add USDT on Ethereum",
+        "AI flow",
+        "Related"
+      ],
+      "sections": [
+        {
+          "id": "asset-management",
+          "title": "Asset management",
+          "level": 2,
+          "excerpt": "After you configure chains on your node, register the tokens and NFTs you want to see and use on the Assets tab. Token config is stored on each node locally (not propagated to other Group members) — the same model as chain registry. The node app and the AI agent use the management API ( POST /addTok"
+        },
+        {
+          "id": "asset-rows-assets-tab",
+          "title": "Asset rows (Assets tab)",
+          "level": 3,
+          "excerpt": "Open the Assets tab and select a chain in the chain selector. Each asset row shows balance, symbol, and actions you can take with that token on this node. Action What it does Transfer Opens the Compose transaction flow with this token pre selected — build an ERC 20 transfer (or equivalent) and submi"
+        },
+        {
+          "id": "protocol-modals-unified-experience",
+          "title": "Protocol modals — unified experience",
+          "level": 3,
+          "excerpt": "Click a protocol shortcut on an asset row (for example Aave on a USDC row) to open that protocol’s modal. Every supported protocol uses the same interaction pattern : 1. Choose action (supply, withdraw, swap, bridge, stake, and so on — depends on the pack) 2. Review amounts, slippage, and health fac"
+        },
+        {
+          "id": "tokens-dialog-add-remove-assets",
+          "title": "Tokens dialog (add / remove assets)",
+          "level": 3,
+          "excerpt": "To manage the token registry without starting from an asset row, open the Tokens dialog from the icon to the right of the Assets heading . Tabs by token type — ERC20 , ERC721 , CTMERC20 , CTMRWA1 each have their own tab Configured tokens for the selected chain appear in the active tab Add — click th"
+        },
+        {
+          "id": "example-add-usdt-on-ethereum",
+          "title": "Example — add USDT on Ethereum",
+          "level": 3,
+          "excerpt": "1. Select Ethereum in the Assets chain selector (chain must exist — see Chain management). 2. Open Tokens (icon beside Assets ). 3. Open the ERC20 tab and click + . 4. Enter contract details: Contract address — USDT on Ethereum mainnet: 0xdAC17F958D2ee523a2206206994597C13D831ec7 Name / symbol — e.g."
+        },
+        {
+          "id": "ai-flow",
+          "title": "AI flow",
+          "level": 3,
+          "excerpt": "With the AI harness and continuum MCP server enabled, you can manage tokens from Agent chat instead of the Tokens dialog. List assets on a chain: What assets do I have configured on Ethereum? The agent calls get token registry (optionally filtered by chainType / chain id ) and lists symbols, contrac"
+        },
+        {
+          "id": "related",
+          "title": "Related",
+          "level": 3,
+          "excerpt": "Contact management — named recipients for Compose transfers Chain management — configure networks before assets DeFi protocol support — protocol capabilities and API keys Compose transaction flow — Transfer from an asset row MPC Accept/Reject loop Configure the AI harness Overview Operator detail: A"
+        }
+      ],
+      "excerpt": "After you configure chains on your node, register the tokens and NFTs you want to see and use on the Assets tab. Token config is stored on each node locally (not propagated to other Group members) — the same model as chain registry. The node app and the AI agent use the management API ( POST /addTok",
+      "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/AssetManagement"
+    },
     {
       "path": "ContinuumDAO/MPAWallet/AttachYourNode",
       "title": "Attach your node",
@@ -1191,9 +1589,136 @@
       "excerpt": "Every MPA node has a bootstrap Ed25519 key pair. The public half is PublicMgtKey in the node config. With deterministic node identity enabled (normal installs), the node’s public Node Key is derived from that bootstrap material. That is how other Group members recognise “you” after a rebuild: same b",
       "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/BackupAndRestoration"
     },
+    {
+      "path": "ContinuumDAO/MPAWallet/Bitcoin",
+      "title": "Bitcoin",
+      "section": "Using an MPA wallet",
+      "headings": [
+        "Bitcoin",
+        "SegWit and Taproot — two KeyGen types",
+        "Why MPC for BTC",
+        "Storing and receiving BTC",
+        "Sending BTC (Compose)",
+        "AI flow",
+        "Related"
+      ],
+      "sections": [
+        {
+          "id": "bitcoin",
+          "title": "Bitcoin",
+          "level": 2,
+          "excerpt": "The MPA wallet supports fully decentralized self custody of BTC without a single recoverable private key on any device — the same MPC model as EVM assets in Overview. You run your own nodes ; ContinuumDAO does not hold shares in a vendor database and there is no hardware wallet registration (no name"
+        },
+        {
+          "id": "segwit-and-taproot-two-keygen-types",
+          "title": "SegWit and Taproot — two KeyGen types",
+          "level": 3,
+          "excerpt": "Bitcoin uses KeyGen type , not the EVM chain registry. Pick the KeyGen that matches the address format you want to receive and spend from: Style KeyGen type MPC protocol Typical address Notes SegWit (P2WPKH) secp256k1 CGGMP24 (threshold ECDSA) bc1q… mainnet Same KeyGen family as Ethereum / EVM. SegW"
+        },
+        {
+          "id": "why-mpc-for-btc",
+          "title": "Why MPC for BTC",
+          "level": 3,
+          "excerpt": "No hardware wallet vendor dependency — custody is threshold shares on nodes you deploy, not a USB device tied to one person’s recovery seed in a manufacturer cloud. No registration gate — unlike some institutional or hardware flows, you are not required to submit personal information to a third part"
+        },
+        {
+          "id": "storing-and-receiving-btc",
+          "title": "Storing and receiving BTC",
+          "level": 3,
+          "excerpt": "1. Create a multi agree KeyGen ( secp256k1 for SegWit, or bitcoin taproot for Taproot) in your Group — KeyGens. 2. After KeyGen completes, open Keys (or KeyGen details) and copy the Bitcoin address : SegWit: bc1q… ( bitcoinp2wpkhmainnet on the KeyGen result) Taproot: bc1p… ( bitcoinp2trmainnet on a "
+        },
+        {
+          "id": "sending-btc-compose",
+          "title": "Sending BTC (Compose)",
+          "level": 3,
+          "excerpt": "1. Open Compose , select the Bitcoin KeyGen (secp256k1 for SegWit or bitcoin taproot for Taproot) and the Bitcoin network (mainnet / testnet / signet as exposed in the app). 2. Build a Bitcoin transfer step: recipient address (or pick a saved contact), amount in BTC. 3. Set Purpose text so peers on "
+        },
+        {
+          "id": "ai-flow",
+          "title": "AI flow",
+          "level": 3,
+          "excerpt": "With the AI harness and continuum MCP server enabled: Send Tom 0.1 BTC The agent: 1. Resolves Tom from the address book ( get address book registry ) — or asks you for a bc1… address if Tom is not saved. 2. Selects the correct Bitcoin KeyGen (SegWit secp256k1 or bitcoin taproot , matching how you cu"
+        },
+        {
+          "id": "related",
+          "title": "Related",
+          "level": 3,
+          "excerpt": "KeyGens — create secp256k1 or bitcoin taproot keys Chain management — Bitcoin network selection Contact management — named recipients for sends Compose transaction flow MPC Accept/Reject loop Eject to Private Key — export after threshold eject Overview What is MPC? — CGGMP24 and FROST (Lockness)"
+        }
+      ],
+      "excerpt": "The MPA wallet supports fully decentralized self custody of BTC without a single recoverable private key on any device — the same MPC model as EVM assets in Overview. You run your own nodes ; ContinuumDAO does not hold shares in a vendor database and there is no hardware wallet registration (no name",
+      "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/Bitcoin"
+    },
+    {
+      "path": "ContinuumDAO/MPAWallet/ChainManagement",
+      "title": "Chain management",
+      "section": "Using an MPA wallet",
+      "headings": [
+        "Chain management",
+        "View configured chains (Assets tab)",
+        "Configure blockchains (add, edit, remove)",
+        "EVM chains — gas fields (optional)",
+        "Bitcoin (SegWit and Taproot)",
+        "Solana and other non-EVM chains",
+        "AI agent flow",
+        "Related"
+      ],
+      "sections": [
+        {
+          "id": "chain-management",
+          "title": "Chain management",
+          "level": 2,
+          "excerpt": "Before you can compose transactions, import Foundry batches, or run DeFi protocol flows, your node needs chain configuration : RPC endpoints, explorers, and optional gas defaults. Chain config is stored on each node locally (not propagated to other Group members). Every node that will simulate, sign"
+        },
+        {
+          "id": "view-configured-chains-assets-tab",
+          "title": "View configured chains (Assets tab)",
+          "level": 3,
+          "excerpt": "Open the Assets tab and use the chain selector at the top. It lists every network already configured on this node. Balances, token lists, and compose chain pickers all draw from this registry. <img src=\"/ media/chain management assets chain selector.png\" alt=\"\" /"
+        },
+        {
+          "id": "configure-blockchains-add-edit-remove",
+          "title": "Configure blockchains (add, edit, remove)",
+          "level": 3,
+          "excerpt": "1. From the header, click Configure blockchains using the icon to the right of the wallet connect box. 2. The modal shows configured chains on this node and presets you can add with one click (most popular EVM mainnets and testnets ship in the app — Arbitrum, Base, Polygon, Linea, and many others). "
+        },
+        {
+          "id": "evm-chains-gas-fields-optional",
+          "title": "EVM chains — gas fields (optional)",
+          "level": 3,
+          "excerpt": "For EIP 1559 chains you do not need to fill in optional fee fields such as Base fee or Priority fee for normal operation. That is the recommended setup: leave them empty and let the node fetch current gas parameters from the RPC gateway when building a proposal and again at Get Sig on the Execute ta"
+        },
+        {
+          "id": "bitcoin-segwit-and-taproot",
+          "title": "Bitcoin (SegWit and Taproot)",
+          "level": 3,
+          "excerpt": "Bitcoin custody is documented in Bitcoin. Summary: Style KeyGen type Address SegWit (P2WPKH) secp256k1 bc1q… Taproot (P2TR) bitcoin taproot (not ed25519) bc1p… You cannot spend Bitcoin from an ed25519 KeyGen or EVM Compose steps meant for ERC 20 transfers."
+        },
+        {
+          "id": "solana-and-other-non-evm-chains",
+          "title": "Solana and other non-EVM chains",
+          "level": 3,
+          "excerpt": "The node stores non EVM network config separately ( POST /postNonEvmChainDetails ). Supported chainType values include solana , near , sui , ton , and stellar . Identity is (chainType, chainId) — for example Solana mainnet is chainType: solana , chainId: mainnet beta . Solana (supported now): add vi"
+        },
+        {
+          "id": "ai-agent-flow",
+          "title": "AI agent flow",
+          "level": 3,
+          "excerpt": "With the AI harness you can manage chains from Agent chat instead of the modal. List what is configured: What chains do I have configured on my node? The agent calls get chain registry and returns name, chain id, RPC, and gas defaults for each EVM entry (and can list non EVM configs when your build "
+        },
+        {
+          "id": "related",
+          "title": "Related",
+          "level": 3,
+          "excerpt": "Asset management — register tokens after chains are configured Bitcoin — SegWit and Taproot custody MPC Accept/Reject loop — Use Custom Gas on create and fee override on Execute Compose transaction flow — chain must exist before compose / Foundry import KeyGens — secp256k1, ed25519, bitcoin taproot "
+        }
+      ],
+      "excerpt": "Before you can compose transactions, import Foundry batches, or run DeFi protocol flows, your node needs chain configuration : RPC endpoints, explorers, and optional gas defaults. Chain config is stored on each node locally (not propagated to other Group members). Every node that will simulate, sign",
+      "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/ChainManagement"
+    },
     {
       "path": "ContinuumDAO/MPAWallet/ComposeTransactionFlow",
-      "title": "KeyGen address from Compose tab; RPC from Configure blockchains",
+      "title": "From user_folder/evm/ (or: forge script … with cwd evm/)",
       "section": "Using an MPA wallet",
       "headings": [
         "Compose transaction flow",
@@ -1205,13 +1730,22 @@
         "Submit — OK creates the multi-sign request",
         "Foundry script",
         "Upload scripts and data (Workspace tab)",
+        "Workspace rules",
         "1. Write the script",
         "2. Dry-run with forge (no broadcast)",
+        "From user_folder/evm/ (or: forge script … with cwd evm/)",
         "3. Import into Compose",
         "Agent / API path (no file upload)",
         "Example command summary",
-        "KeyGen address from Compose tab; RPC from Configure blockchains",
-        "No --broadcast → import broadcast/.../dry-run/run-latest.json in the node app",
+        "From user_folder/evm/ — KeyGen address from Compose tab; RPC from Configure blockchains",
+        "No --broadcast → import evm/broadcast/.../dry-run/run-latest.json in the node app",
+        "EIP-712 typed-data signatures",
+        "Select KeyGen and chain",
+        "Add one or more EIP-712 steps",
+        "Validate",
+        "Submit — OK creates the multi-sign request",
+        "Execute — deliver signatures",
+        "Agent / API path",
         "Bump / remove — mempool transactions",
         "Bump",
         "Remove",
@@ -1234,7 +1768,7 @@
           "id": "select-keygen-and-chain",
           "title": "Select KeyGen and chain",
           "level": 4,
-          "excerpt": "1. Choose the KeyGen that will sign (must be multi agree for MPA custody). 2. Choose the blockchain (network) for this request. 3. Optionally set Purpose text and Custom Chain config (gas profile, RPC gateway, gas multiplier) — peers see these on Join ; see Creating a multi sign request."
+          "excerpt": "1. Choose the KeyGen that will sign (must be multi agree for MPA custody). 2. Choose the blockchain (network) for this request. 3. Optionally set Purpose text and Custom Chain config (gas profile, RPC gateway, gas multiplier) — peers see these on Join ; see Creating a multi sign request. For transfe"
         },
         {
           "id": "add-one-or-more-transaction-steps",
@@ -1270,7 +1804,13 @@
           "id": "upload-scripts-and-data-workspace-tab",
           "title": "Upload scripts and data (Workspace tab)",
           "level": 4,
-          "excerpt": "Node → AI Agent → Workspace manages the node’s writable user folder (on the host this is the user folder/ directory beside your node config; in the container it is /app/user folder ). Use it to add or edit scripts and data on the node without SSH: Browse — skills/ , scripts/ , data/ , plans/ , and o"
+          "excerpt": "Node → AI Agent → Workspace manages the node’s writable user folder (on the host this is the user folder/ directory beside your node config; in the container it is /app/user folder ). Use it to add or edit files on the node without SSH. Do not put loose files at the user folder root — writes must la"
+        },
+        {
+          "id": "workspace-rules",
+          "title": "Workspace rules",
+          "level": 4,
+          "excerpt": "The node jails all agent and UI writes to allowed subtrees under user folder : Rule Detail No root files Paths must be under skills/ , scripts/ , plans/ , data/ , memory/ , evm/ , solana/ , near/ , stellar/ , ton/ , sui/ , .foundry/ , .svm/ , or .mcp foundry workspace/ — not loose files at user fold"
         },
         {
           "id": "1-write-the-script",
@@ -1282,7 +1822,13 @@
           "id": "2-dry-run-with-forge-no-broadcast",
           "title": "2. Dry-run with forge (no broadcast)",
           "level": 4,
-          "excerpt": "Run the script against a live RPC for the target chain. Set sender to the KeyGen’s Ethereum address (shown on the Compose tab). Do not pass broadcast — MPC signing and broadcast happen later on Execute , not from Foundry. bash export MPC ADDRESS=0xYourKeyGenEthereumAddress forge script script/Deploy"
+          "excerpt": "Run the script against a live RPC for the target chain. Set sender to the KeyGen’s Ethereum address (shown on the Compose tab). Do not pass broadcast — MPC signing and broadcast happen later on Execute , not from Foundry. bash export MPC ADDRESS=0xYourKeyGenEthereumAddress"
+        },
+        {
+          "id": "from-user-folder-evm-or-forge-script-with-cwd-evm",
+          "title": "From user_folder/evm/ (or: forge script … with cwd evm/)",
+          "level": 1,
+          "excerpt": "cd evm forge script script/DeployAndConfigure.s.sol:DeployAndConfigure \\ rpc url https://your chain rpc.example \\ sender \"$MPC ADDRESS\" Foundry writes the simulation output to: evm/broadcast/<ScriptFile /<chainId /dry run/run latest.json (Foundry MCP writes the same shape under .mcp foundry workspac"
         },
         {
           "id": "3-import-into-compose",
@@ -1294,7 +1840,7 @@
           "id": "agent-api-path-no-file-upload",
           "title": "Agent / API path (no file upload)",
           "level": 4,
-          "excerpt": "The AI agent can skip the upload dialog and call the continuum MCP tool create forge multi sign request with the parsed broadcast JSON, KeyGen id, purpose, and optional overrideSender / startingNonce . Longer sequences can be merged with create joined multi sign request (chain Foundry output with ma"
+          "excerpt": "The AI agent can skip the upload dialog and call the continuum MCP tool import forge dry run multi sign request with dryRunFilePath under evm/broadcast/.../dry run/run latest.json (or .mcp foundry workspace/broadcast/... when Foundry MCP ran the script). Prefer that file import tool over create forg"
         },
         {
           "id": "example-command-summary",
@@ -1303,16 +1849,58 @@
           "excerpt": "bash"
         },
         {
-          "id": "keygen-address-from-compose-tab-rpc-from-configure-blockchains",
-          "title": "KeyGen address from Compose tab; RPC from Configure blockchains",
+          "id": "from-user-folder-evm-keygen-address-from-compose-tab-rpc-from-configure-blockchains",
+          "title": "From user_folder/evm/ — KeyGen address from Compose tab; RPC from Configure blockchains",
           "level": 1,
           "excerpt": "forge script script/MyScript.s.sol:MyScript \\ rpc url <RPC \\ sender <KeyGen Eth address"
         },
         {
-          "id": "no-broadcast-import-broadcast-dry-run-run-latest-json-in-the-node-app",
-          "title": "No --broadcast → import broadcast/.../dry-run/run-latest.json in the node app",
+          "id": "no-broadcast-import-evm-broadcast-dry-run-run-latest-json-in-the-node-app",
+          "title": "No --broadcast → import evm/broadcast/.../dry-run/run-latest.json in the node app",
           "level": 1,
-          "excerpt": "<! Screenshot placeholder: replace media/mpc compose foundry import.png <img src=\"/ media/mpc compose foundry import.png\" alt=\"Import from Foundry broadcast — run latest.json loaded into Compose batch (screenshot pending)\" / Separate from composing a new sign request, the node app supports bump and "
+          "excerpt": "In this example, the script sends USDC to 94 addresses. The script has been used before, so the initial nonce and those that follow must be set to the new nonce value: <img src=\"/ media/mpc compose foundry import 1.png\" alt=\"\" / And now you see that in this example, there are 94 transactions importe"
+        },
+        {
+          "id": "eip-712-typed-data-signatures",
+          "title": "EIP-712 typed-data signatures",
+          "level": 3,
+          "excerpt": "Some protocols authorize actions with an EIP 712 typed data signature instead of an unsigned EVM transaction at sign time. The MPC KeyGen signs a 32 byte digest derived from structured data ( domain , types , primaryType , message ). Delivery to the protocol or chain happens later on Execute — or no"
+        },
+        {
+          "id": "select-keygen-and-chain",
+          "title": "Select KeyGen and chain",
+          "level": 4,
+          "excerpt": "Same starting point as manual compose: 1. Choose the KeyGen that will sign (must be multi agree for MPA custody; EIP 712 uses the KeyGen’s secp256k1 / Ethereum address). 2. Choose the blockchain (network) for context and delivery. 3. Optionally set Purpose text — peers see this on Join alongside a h"
+        },
+        {
+          "id": "add-one-or-more-eip-712-steps",
+          "title": "Add one or more EIP-712 steps",
+          "level": 4,
+          "excerpt": "Each step is one typed data digest (one MPC signature) in the eventual batch — not an unsigned transaction with calldata and gas fields. Single step — one permit, one Hyperliquid action, one governance typed message, and similar. Multiple steps — add further steps to batch several EIP 712 signatures"
+        },
+        {
+          "id": "validate",
+          "title": "Validate",
+          "level": 4,
+          "excerpt": "Before OK creates the multi sign request, run checks on the current step or on the whole batch (as the UI offers): Action What it does Validate Local and node side checks: required typed data fields present, well formed JSON, digest recomputation matches the stored hash, KeyGen type matches the chai"
+        },
+        {
+          "id": "submit-ok-creates-the-multi-sign-request",
+          "title": "Submit — OK creates the multi-sign request",
+          "level": 4,
+          "excerpt": "When every step validates, confirm OK (or Create sign request ). The originator management signs the submission. The node creates a multi sign request with signRequestKind: eip712 and publishes it to the KeyGen. From here the flow continues on Join. Peers review the whole batch once. On agree, each "
+        },
+        {
+          "id": "execute-deliver-signatures",
+          "title": "Execute — deliver signatures",
+          "level": 4,
+          "excerpt": "After threshold Accept and MPC signing on Execute , the originator delivers each signature according to that step’s delivery hint (the delivery block is not part of the signed payload): Delivery kind What Execute does none Export or copy the signature — no automatic POST or broadcast hyperliquid exc"
+        },
+        {
+          "id": "agent-api-path",
+          "title": "Agent / API path",
+          "level": 4,
+          "excerpt": "The AI agent can call create compose eip712 multi sign request (continuum MCP, mpc compose group) with typed data legs built by @continuumdao/ctm mpc defi ( buildEip712Multisign and protocol adapters). Prefer that over hand rolling digests when a protocol adapter exists. See MCP servers — built in c"
         },
         {
           "id": "bump-remove-mempool-transactions",
@@ -1342,12 +1930,66 @@
       "excerpt": "This page describes how an originator builds a multi sign request (single transaction or batch ) before it enters the MPC Accept/Reject loop. The same loop applies no matter how the request was created. How the originator creates the request Typical use Manual compose Hand built transfers, custom co",
       "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/ComposeTransactionFlow"
     },
+    {
+      "path": "ContinuumDAO/MPAWallet/ContactManagement",
+      "title": "Contact management",
+      "section": "Using an MPA wallet",
+      "headings": [
+        "Contact management",
+        "Open Contacts (header)",
+        "Add or edit a contact",
+        "Using contacts in Compose",
+        "AI flow",
+        "Related"
+      ],
+      "sections": [
+        {
+          "id": "contact-management",
+          "title": "Contact management",
+          "level": 2,
+          "excerpt": "The address book (contacts) stores named recipients and contract addresses on this node only — the same local registry model as chains and assets. Contacts are not propagated to other Group members. The node app and AI agent use the management API ( POST /addKnownAddress , GET /getKnownAddresses ). "
+        },
+        {
+          "id": "open-contacts-header",
+          "title": "Open Contacts (header)",
+          "level": 3,
+          "excerpt": "Click the body / person icon in the app header to open Contacts . From here you can: Browse saved names and addresses Add a new contact ( + ) Edit name, chain scope, or contract flag Remove an entry (node registry only — nothing on chain changes) Management signing (MetaMask EIP 191 or Ed25519 ) is "
+        },
+        {
+          "id": "add-or-edit-a-contact",
+          "title": "Add or edit a contact",
+          "level": 3,
+          "excerpt": "When adding a contact, set: Field Purpose Name Label shown in Contacts and in Compose pickers (for example Tom , Treasury , USDC contract ) Address EVM address ( 0x… ) — wallet (EOA) or smart contract Chain scope Which networks this entry applies to (see below) Is contract Enable when the address is"
+        },
+        {
+          "id": "using-contacts-in-compose",
+          "title": "Using contacts in Compose",
+          "level": 3,
+          "excerpt": "After contacts exist, they surface in the Compose transaction flow: 1. Open Compose , select KeyGen and chain. 2. Add a step (for example ERC 20 transfer or a custom contract call). 3. In recipient or to fields, open the contact picker (or type to filter) — saved names appear alongside raw address e"
+        },
+        {
+          "id": "ai-flow",
+          "title": "AI flow",
+          "level": 3,
+          "excerpt": "With the AI harness and continuum MCP server enabled, manage contacts from Agent chat . List contacts: What contacts do I have? The agent calls get address book registry and returns names, addresses, chain scope, and contract flags. Add a contact: Add a new contact called Tom with address 0x563751cE"
+        },
+        {
+          "id": "related",
+          "title": "Related",
+          "level": 3,
+          "excerpt": "Compose transaction flow — pick contacts as recipients Asset management — tokens for transfers Chain management — networks must be configured first MPC Accept/Reject loop Backup and restoration — contacts are included in node backups Configure the AI harness Overview Operator detail: API Implementat"
+        }
+      ],
+      "excerpt": "The address book (contacts) stores named recipients and contract addresses on this node only — the same local registry model as chains and assets. Contacts are not propagated to other Group members. The node app and AI agent use the management API ( POST /addKnownAddress , GET /getKnownAddresses ). ",
+      "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/ContactManagement"
+    },
     {
       "path": "ContinuumDAO/MPAWallet/DeFiProtocolSupport",
       "title": "DeFi protocol support",
       "section": "Using an MPA wallet",
       "headings": [
         "DeFi protocol support",
+        "Protocol modals — unified experience",
         "Supported protocols",
         "Notes",
         "Related"
@@ -1359,6 +2001,12 @@
           "level": 2,
           "excerpt": "MPA wallet can interact with selected web3 / DeFi protocols directly — through the node app multi sign UI and through the built in AI agent (continuum MCP: load a protocol pack, then use that protocol’s tools). On chain actions still go through your Group’s MPC KeyGen and multi agree threshold — the"
         },
+        {
+          "id": "protocol-modals-unified-experience",
+          "title": "Protocol modals — unified experience",
+          "level": 3,
+          "excerpt": "Every supported protocol opens in the same modal pattern in the node app. You do not jump out to separate dApp sites or relearn a new layout for each venue — swaps, lending, staking, bridges, and perps all follow one wallet native flow. How to open a protocol Assets tab — click a protocol shortcut o"
+        },
         {
           "id": "supported-protocols",
           "title": "Supported protocols",
@@ -1369,13 +2017,13 @@
           "id": "notes",
           "title": "Notes",
           "level": 3,
-          "excerpt": "AI agent: load a protocol with continuum MCP ( list defi protocols / load defi protocol ), then use that pack’s tools. Preferred KeyGen and default Ed25519 signer still apply for management signed steps — see Configure the AI harness. Node app: open the multi sign / protocol UI for the same packs (n"
+          "excerpt": "Unified UI first: prefer protocol shortcuts on the Assets tab or the shared modal flow above — the table below is the capability reference, not a separate product surface per protocol. AI agent: load a protocol with continuum MCP ( list defi protocols / load defi protocol ), then use that pack’s too"
         },
         {
           "id": "related",
           "title": "Related",
           "level": 3,
-          "excerpt": "MPC Accept/Reject loop Compose transaction flow Overview Install a node AI harness overview Configure the AI harness Trade ideas KeyGens"
+          "excerpt": "Asset management — protocol shortcuts from the Assets tab MPC Accept/Reject loop Compose transaction flow Overview Install a node AI harness overview Configure the AI harness Trade ideas KeyGens"
         }
       ],
       "excerpt": "MPA wallet can interact with selected web3 / DeFi protocols directly — through the node app multi sign UI and through the built in AI agent (continuum MCP: load a protocol pack, then use that protocol’s tools). On chain actions still go through your Group’s MPC KeyGen and multi agree threshold — the",
@@ -1494,7 +2142,7 @@
       "headings": [
         "Install a node",
         "Start here",
-        "For AI agents — one-shot VPS script",
+        "For AI agents — full provision and configure",
         "Choose where the node runs",
         "Remote VPS",
         "Your own PC",
@@ -1508,6 +2156,7 @@
         "One node is not enough for a KeyGen address",
         "Tell your node about its peers (Configured Nodes)",
         "Then create a Group and a KeyGen",
+        "MPA billing",
         "Related"
       ],
       "sections": [
@@ -1524,10 +2173,10 @@
           "excerpt": "1. Open https://mpa.continuumdao.org/node map. 2. Click the + button. 3. Walk through the installer options: where the node should run (remote VPS or your own PC), management keys, and the public IPv4 address peers will use to reach you. 4. When the installer finishes, attach the node (see Attach yo"
         },
         {
-          "id": "for-ai-agents-one-shot-vps-script",
-          "title": "For AI agents — one-shot VPS script",
+          "id": "for-ai-agents-full-provision-and-configure",
+          "title": "For AI agents — full provision and configure",
           "level": 3,
-          "excerpt": "To create a node programmatically on Ubuntu/Debian, use the one shot installer (not the long manual page): Script install node debian ubuntu.sh Agent guide CREATE NODE ONESHOT.md Repo entry AGENTS.md bash curl fsSL \"https://raw.githubusercontent.com/ContinuumDAO/mpc config/main/scripts/install node "
+          "excerpt": "If you are an AI agent asked to provision or configure a node, start here: Agent provision and configure (topology, oneshot, SSH tunnel to :8446 , peers / MQTT, Group, KeyGen, hand off). Discover it with search continuum docs ( provision node / create mpc node ) then get continuum doc path Continuum"
         },
         {
           "id": "choose-where-the-node-runs",
@@ -1581,7 +2230,7 @@
           "id": "attach-your-node",
           "title": "Attach your node",
           "level": 3,
-          "excerpt": "Your browser talks to your node. ContinuumDAO does not relay that control path. Three attach options on the hosted SPA: Browser HTTPS , Node hosted app (local PC) , and Node hosted app (SSH tunnel) . Geo restricted users see only the two node hosted options. Full walkthrough with screenshots: Attach"
+          "excerpt": "Your browser talks to your node. ContinuumDAO does not relay that control path. Three attach options on the wallet website (mpa.continuumdao.org): Browser HTTPS , Node hosted app (local PC) , and Node hosted app (SSH tunnel) . Geo restricted users see only the two node hosted options. Full walkthrou"
         },
         {
           "id": "post-install-steps",
@@ -1607,11 +2256,17 @@
           "level": 3,
           "excerpt": "1. Confirm Configured Nodes are healthy → Configured Nodes 2. Create or join a Group → Groups 3. Create a KeyGen (shared address) → KeyGens You can keep using the wallet from the node app alone. The MPA wallet is AI first , so most users will also want the optional Configure the AI harness steps aft"
         },
+        {
+          "id": "mpa-billing",
+          "title": "MPA billing",
+          "level": 3,
+          "excerpt": "Before the first register on Linea for a KeyGen, claim withdraw authority on that node. Full setup — withdraw authority, register, top up, month activation, and veCTM waiver: MPA billing ."
+        },
         {
           "id": "related",
           "title": "Related",
           "level": 3,
-          "excerpt": "Overview Backup and restoration Configured Nodes Groups KeyGens Configure the AI harness CREATE NODE ONESHOT.md — AI agent one shot VPS install Running an MPC Node — advanced / manual path"
+          "excerpt": "Overview Backup and restoration Configured Nodes Groups KeyGens MPA billing Configure the AI harness AI managed governance Plan mode Agent provision and configure — AI agent full VPS provision + mesh CREATE NODE ONESHOT.md — AI agent one shot VPS install Running an MPC Node — advanced / manual path"
         }
       ],
       "excerpt": "<! agent: task: create mpc node audience: [human, ai agent] oneshot script: https://raw.githubusercontent.com/ContinuumDAO/mpc config/main/scripts/install node debian ubuntu.sh oneshot doc: https://github.com/ContinuumDAO/mpc config/blob/main/docs/CREATE NODE ONESHOT.md agents md: https://github.com",
@@ -1678,12 +2333,86 @@
           "id": "related",
           "title": "Related",
           "level": 3,
-          "excerpt": "Compose transaction flow Overview KeyGens DeFi protocol support Trade ideas Default Ed25519 signer Eject to Private Key"
+          "excerpt": "Chain management Compose transaction flow Overview KeyGens DeFi protocol support Trade ideas Default Ed25519 signer Eject to Private Key"
         }
       ],
       "excerpt": "Every on chain spend from a multi agree KeyGen runs through the same multi sign request flow: one node (the originator ) proposes one or more transactions; the other KeyGen nodes Accept or Reject until the KeyGen threshold is met or the round times out. Only then does the originator run MPC signing ",
       "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/MPCAcceptRejectLoop"
     },
+    {
+      "path": "ContinuumDAO/MPAWallet/MpaBilling",
+      "title": "MPA billing",
+      "section": "Using an MPA wallet",
+      "headings": [
+        "MPA wallet billing",
+        "Billing setup order",
+        "Withdraw authority",
+        "What it is",
+        "How to claim (node app)",
+        "Important rules",
+        "Register on Linea",
+        "Pay for the month",
+        "Related"
+      ],
+      "sections": [
+        {
+          "id": "mpa-wallet-billing",
+          "title": "MPA wallet billing",
+          "level": 2,
+          "excerpt": "MPA wallet usage is metered on Linea through a DAO governed fee contract . Each KeyGen you use for multi sign must be registered there before billable signatures count against your balance. You either pay monthly (stablecoin or CTM credits) or qualify for a veCTM subscription waiver — see veCTM on y"
+        },
+        {
+          "id": "billing-setup-order",
+          "title": "Billing setup order",
+          "level": 3,
+          "excerpt": "For a new KeyGen on a node, work through these steps once: 1. Claim withdraw authority (this page) — bind this node to the KeyGen as its billing operator. 2. Register the KeyGen on Linea — enroll the shared address on the fee contract. 3. Fund or waive — top up credits, activate the billing month, o"
+        },
+        {
+          "id": "withdraw-authority",
+          "title": "Withdraw authority",
+          "level": 3,
+          "excerpt": "Withdraw authority answers one question: which KeyGen address may operate billing for this node? — register, deposit, sync the month, attach veCTM, and related fee contract actions for that KeyGen. You must claim withdraw authority on this node before the first register on Linea for that KeyGen. It "
+        },
+        {
+          "id": "what-it-is",
+          "title": "What it is",
+          "level": 4,
+          "excerpt": "An off chain signature (typed data), not a normal on chain transaction — same compose sign request flow as Forum sign in. Non billable — it does not consume signature credits. The node proves control with its P 256 node key ; the result is recorded on Linea as claimNodeWithdrawAuthority for the chos"
+        },
+        {
+          "id": "how-to-claim-node-app",
+          "title": "How to claim (node app)",
+          "level": 4,
+          "excerpt": "1. Attach to your node and open Multi Sign . 2. Select the secp256k1 KeyGen that should own billing for this node. 3. In the MPA wallet status strip, choose Claim authority (or use Compose if the UI prefills a claim step). 4. Peers Accept on Join ; the originator Execute s. Or ask in Agent chat : “C"
+        },
+        {
+          "id": "important-rules",
+          "title": "Important rules",
+          "level": 4,
+          "excerpt": "Claim before register — complete withdraw authority before the first register on Linea for that KeyGen. Do not batch claim and register in one multi sign request — run claim first, then register in a separate request after claim succeeds. One authority per KeyGen on this node — veCTM attach and deta"
+        },
+        {
+          "id": "register-on-linea",
+          "title": "Register on Linea",
+          "level": 3,
+          "excerpt": "After withdraw authority is claimed for the selected KeyGen: 1. From the authority KeyGen , compose register on Linea (Multi Sign status strip or Compose). 2. Accept and Execute through your Group. Until registered, billable wallet actions for that KeyGen will not accrue correctly against your accou"
+        },
+        {
+          "id": "pay-for-the-month",
+          "title": "Pay for the month",
+          "level": 3,
+          "excerpt": "Situation What to do Month not activated From the authority KeyGen, Activate on Linea (sync billing month) before heavy signing on other chains. Low balance Top up credits in stablecoin or CTM via the billing compose flows. Over free limit Pay overage or attach more veCTM / subscribe per DAO rules. "
+        },
+        {
+          "id": "related",
+          "title": "Related",
+          "level": 3,
+          "excerpt": "veCTM on your node Overview — Subscription through staking Install a node Compose transaction flow — EIP 712 MPC Accept/Reject loop"
+        }
+      ],
+      "excerpt": "MPA wallet usage is metered on Linea through a DAO governed fee contract . Each KeyGen you use for multi sign must be registered there before billable signatures count against your balance. You either pay monthly (stablecoin or CTM credits) or qualify for a veCTM subscription waiver — see veCTM on y",
+      "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/MpaBilling"
+    },
     {
       "path": "ContinuumDAO/MPAWallet/Overview",
       "title": "Overview",
@@ -1746,13 +2475,13 @@
           "id": "subscription-through-staking",
           "title": "Subscription through staking",
           "level": 3,
-          "excerpt": "MPA wallet access can be paid via a monthly subscription , or — for node operators who stake veCTM on their node — through subscription through staking : free use of the wallet up to a governance set free signature limit . Attach veCTM from the staking panel after your node is running; limits and an"
+          "excerpt": "MPA wallet access can be paid via a monthly subscription , or — for node operators who attach veCTM to their node — through subscription through staking : free use of the wallet up to a generous governance set free signature limit . Limits and any overage fees are set by DAO voting. Why attach, how "
         },
         {
           "id": "related",
           "title": "Related",
           "level": 3,
-          "excerpt": "Attach your node MPC Accept/Reject loop Compose transaction flow Install a node Backup and restoration Configure the AI harness KeyGens Eject to Private Key Joining the Continuum — optional cross chain signer role"
+          "excerpt": "Attach your node veCTM on your node MPA billing Chain management Asset management Contact management Bitcoin MPC Accept/Reject loop Compose transaction flow Install a node Backup and restoration Configure the AI harness KeyGens Eject to Private Key Joining the Continuum — optional cross chain signer"
         }
       ],
       "excerpt": "The MPA wallet is an AI first wallet: people and AI agents jointly control a single wallet address using Multi Party Computation (MPC). Every node ships with a built in AI agent harness — the natural way to propose trades, run analysis, and drive DeFi flows — while a rich frontend (mpa.continuumdao.",
@@ -1886,12 +2615,93 @@
           "id": "related",
           "title": "Related",
           "level": 3,
-          "excerpt": "Technical analysis AI charting DeFi protocol support MPC Accept/Reject loop Configure the AI harness Overview — 2/2 human in the loop Accept Telegram Mini App"
+          "excerpt": "Technical analysis AI charting DeFi protocol support Bitcoin MPC Accept/Reject loop Configure the AI harness Overview — 2/2 human in the loop Accept Telegram Mini App"
         }
       ],
       "excerpt": "Technical analysis does more than describe the chart. When an analysis finds a clear setup, the node can turn it into one or more trade ideas — concrete long/short (or spot) levels the AI agent can use to build a real multi sign request for agreement by the other nodes in your KeyGen. 1. Load OHLCV ",
       "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/TradeIdeas"
     },
+    {
+      "path": "ContinuumDAO/MPAWallet/VeCTMOnYourNode",
+      "title": "veCTM on your node",
+      "section": "Using an MPA wallet",
+      "headings": [
+        "veCTM on your node",
+        "Why attach veCTM?",
+        "Governance without locking a huge balance",
+        "Attach is yours — detach needs governance",
+        "Before you attach",
+        "Get veCTM (lock CTM)",
+        "Attach veCTM to your node",
+        "Request detach",
+        "Managing voting power",
+        "Related"
+      ],
+      "sections": [
+        {
+          "id": "vectm-on-your-node",
+          "title": "veCTM on your node",
+          "level": 2,
+          "excerpt": "veCTM is ContinuumDAO’s voting escrow token: you lock CTM for a chosen period and receive an veCTM NFT that carries governance voting power . When you attach that NFT to your MPA wallet node, you unlock two practical benefits — DAO participation and free wallet use — while accepting that removing it"
+        },
+        {
+          "id": "why-attach-vectm",
+          "title": "Why attach veCTM?",
+          "level": 3,
+          "excerpt": "Benefit What you get Governance Voting power for ContinuumDAO — Forum access at holder thresholds, on chain proposals, and votes. With the AI harness configured, your agent can help research, draft, and vote; your Group still Accept s every on chain step. Free wallet signatures Subscription through "
+        },
+        {
+          "id": "governance-without-locking-a-huge-balance",
+          "title": "Governance without locking a huge balance",
+          "level": 4,
+          "excerpt": "You do not need to lock an enormous CTM balance into the KeyGen’s own veCTM NFT for DAO governance . Holders with veCTM in other wallets can delegate voting power to the KeyGen address — the same address that holds the attached NFT — so Forum access, proposals, and votes can use delegated power as w"
+        },
+        {
+          "id": "attach-is-yours-detach-needs-governance",
+          "title": "Attach is yours — detach needs governance",
+          "level": 3,
+          "excerpt": "This asymmetry is deliberate. Attaching is under your control . You choose the veCTM NFT, submit the attach through your node, and your MPC Group agrees through the normal Accept/Reject loop. Detaching is not. While veCTM is attached to a node it is locked there : You cannot detach, transfer, split,"
+        },
+        {
+          "id": "before-you-attach",
+          "title": "Before you attach",
+          "level": 3,
+          "excerpt": "1. Install and attach to your node in the browser. 2. Create a Group and a secp256k1 KeyGen → Groups, KeyGens. 3. Add Linea in Chain management. 4. Complete MPA billing setup for that KeyGen on Linea — including withdraw authority before the first registration. 5. Hold a veCTM NFT at the KeyGen addr"
+        },
+        {
+          "id": "get-vectm-lock-ctm",
+          "title": "Get veCTM (lock CTM)",
+          "level": 3,
+          "excerpt": "If you already hold veCTM elsewhere, you can transfer it to your KeyGen first (only while it is not attached to any node). To create a new lock from the node app: 1. Open Multi Sign , select your KeyGen, and open the Assets tab on Linea . 2. Add CTM and veCTM if they are not listed — see Asset manag"
+        },
+        {
+          "id": "attach-vectm-to-your-node",
+          "title": "Attach veCTM to your node",
+          "level": 3,
+          "excerpt": "From the node app (with your authority KeyGen selected): 1. On Assets , open ContinuumDAO on the veCTM NFT you want to attach. 2. Open the Attach tab, confirm the token id, and submit. 3. Peers Accept the sign request on Join ; the originator Execute s. Or ask in Agent chat : “Attach my veCTM to thi"
+        },
+        {
+          "id": "request-detach",
+          "title": "Request detach",
+          "level": 3,
+          "excerpt": "When you want veCTM back under your KeyGen’s full control: 1. Open ContinuumDAO on the attached NFT → Attach tab → Request detach (same authority KeyGen). 2. Accept and Execute through your Group. That records your request on chain. Governance must pass a proposal to complete detach. Until then, the"
+        },
+        {
+          "id": "managing-voting-power",
+          "title": "Managing voting power",
+          "level": 3,
+          "excerpt": "Goal What to do Vote or propose from this KeyGen Ensure enough voting power at the KeyGen address — from the attached NFT, from delegation sent to the KeyGen , or both. Proposers need at least 1000 veCTM or 0.1% of total power , whichever is higher (delegation counts). Add power without locking more"
+        },
+        {
+          "id": "related",
+          "title": "Related",
+          "level": 3,
+          "excerpt": "Overview — Subscription through staking Install — MPA billing AI managed governance MPC Accept/Reject loop White Paper — Staking as subscription"
+        }
+      ],
+      "excerpt": "veCTM is ContinuumDAO’s voting escrow token: you lock CTM for a chosen period and receive an veCTM NFT that carries governance voting power . When you attach that NFT to your MPA wallet node, you unlock two practical benefits — DAO participation and free wallet use — while accepting that removing it",
+      "url": "https://docs.continuumdao.org/ContinuumDAO/MPAWallet/VeCTMOnYourNode"
+    },
     {
       "path": "ContinuumDAO/MPC/BetterSecurity",
       "title": "Better Security",
@@ -2361,10 +3171,10 @@
           "id": "related",
           "title": "Related",
           "level": 3,
-          "excerpt": "Install a node — preferred node map installer (humans) + AI one shot links CREATE NODE ONESHOT.md — AI agent VPS one shot Backup and restoration Overview Configured Nodes Joining the Continuum mpc config README · AGENTS.md"
+          "excerpt": "Install a node — preferred node map installer (humans) + AI one shot links Agent provision and configure — AI agent full VPS provision + mesh CREATE NODE ONESHOT.md — AI agent VPS one shot Backup and restoration Overview Configured Nodes Joining the Continuum mpc config README · AGENTS.md"
         }
       ],
-      "excerpt": "For almost all users, follow the user guide Install a node (node map + button at https://mpa.continuumdao.org/node map). You can create a node on a laptop or PC, or on a remote VPS (Linux / Windows 11 / macOS). This page is the advanced / manual path. AI agents creating a greenfield Ubuntu/Debian VP",
+      "excerpt": "For almost all users, follow the user guide Install a node (node map + button at https://mpa.continuumdao.org/node map). You can create a node on a laptop or PC, or on a remote VPS (Linux / Windows 11 / macOS). This page is the advanced / manual path. AI agents creating or configuring a greenfield U",
       "url": "https://docs.continuumdao.org/ContinuumDAO/RunningInstructions/NodeRunningInstruction"
     },
     {
@@ -2377,11 +3187,14 @@
         "About ContinuumDAO",
         "Why Does Having Open Public Infrastructure Matter?",
         "Why is the ContinuumDAO Mission Important?",
-        "Lack of  Open Cross-Chain Fabrics",
-        "Security Relies on ‘Staking’ Alone",
-        "The Number of Chains in a Network is not Scaleable",
-        "Technical Challenges in Expanding the Cross-Chain Network",
-        "Lack of Protocol Level Security",
+        "On-Chain Finance Needs Trustworthy Self-Custody",
+        "AI Must Not Spend Alone",
+        "AI-First DAO Governance",
+        "Fragmented Chains and DeFi Silos",
+        "Fully Decentralized MPC Custody",
+        "The Wallet Must Work Without ContinuumDAO",
+        "Cross-Chain dApps Need Open, MPC-Secured Infrastructure",
+        "Cross-Chain Signing Must Scale Beyond Multi-Sig and zkProof Relayers",
         "How is ContinuumDAO Different?",
         "The Current Situation",
         "ContinuumDAO Roadmap",
@@ -2391,6 +3204,7 @@
         "DAO incentive system",
         "The ContinuumDAO Token",
         "Vested Token Model",
+        "Staking as Subscription — the Primary Use of CTM / veCTM",
         "The MPC Network and the MPA Wallet",
         "Nodes — the core building block",
         "The Multi-Party Agent (MPA) wallet",
@@ -2407,67 +3221,85 @@
           "id": "continuumdao-white-paper",
           "title": "ContinuumDAO White Paper",
           "level": 1,
-          "excerpt": "15th August 2026"
+          "excerpt": "17th August 2026"
         },
         {
           "id": "welcome-to-continuum",
           "title": "Welcome to Continuum",
           "level": 1,
-          "excerpt": "An open public cross chain network secured by Multi Party Computation — and the Multi Party Agent (MPA) wallet , an AI first flagship MPC product (with a rich frontend for full manual control) for custody without a Private Key , AI assisted trading , and optional cross chain signing rewards — run as"
+          "excerpt": "An AI first DAO and wallet, with humans in the loop . ContinuumDAO’s Multi Party Agent (MPA) wallet extends that model from custody to DAO governance — AI agents can propose , debate on the Forum, evaluate proposals, and vote on chain, alongside humans who retain control through MPC threshold signin"
         },
         {
           "id": "about-continuumdao",
           "title": "About ContinuumDAO",
           "level": 2,
-          "excerpt": "ContinuumDAO is a community that is collectively building a future in which all blockchains are linked, to enable the integration of decentralized blockchain ledgers for all dApps. We realise that the entirety of finance and other ‘trust’ based networks will transition to web3 in the next few years "
+          "excerpt": "ContinuumDAO is a community building the infrastructure for the next phase of on chain finance. Traditional financial assets, trading, and trust networks are moving on chain. Regulatory frameworks are maturing — the EU’s MiCA regime and evolving approval paths in the US are opening the door to insti"
         },
         {
           "id": "why-does-having-open-public-infrastructure-matter",
           "title": "Why Does Having Open Public Infrastructure Matter?",
           "level": 2,
-          "excerpt": "A better question is why would anyone who wishes to create a multi chain dApp rely on an infrastructure that wasn’t completely decentralized, or which was owned by a company, knowing that this could disappear at anytime? ContinuumDAO has sophisticated DAO governed smart contracts that do not rely on"
+          "excerpt": "A better question is why would anyone who wishes to create a multi chain dApp — or operate an MPA wallet for serious on chain asset management — rely on infrastructure that wasn’t completely decentralized, or which was owned by a company, knowing that this could disappear at any time? ContinuumDAO h"
         },
         {
           "id": "why-is-the-continuumdao-mission-important",
           "title": "Why is the ContinuumDAO Mission Important?",
           "level": 2,
-          "excerpt": "The existing landscape of web3 is confusing for new and even existing users. Continuum will solve some of the biggest pain points how to utilize AI safely for on chain trading and how decentralized applications (dApps) securely communicate between any blockchain that supports a contract based system"
+          "excerpt": "Web3 is confusing and risky for both newcomers and experienced users moving real assets on chain. ContinuumDAO addresses the custody, AI safety, multi chain access, and agentic governance problems that block mainstream adoption — with a public MPC network whose flagship product is the MPA wallet , a"
+        },
+        {
+          "id": "on-chain-finance-needs-trustworthy-self-custody",
+          "title": "On-Chain Finance Needs Trustworthy Self-Custody",
+          "level": 3,
+          "excerpt": "As financial assets and trading move on chain under evolving regulatory frameworks, users need custody that matches the seriousness of the assets they hold. Vendor MPC wallets that store key shares in company databases, hardware wallets that tie recovery to email addresses and home addresses, and si"
+        },
+        {
+          "id": "ai-must-not-spend-alone",
+          "title": "AI Must Not Spend Alone",
+          "level": 3,
+          "excerpt": "Much on chain asset management will be driven by AI agents, but agents must not be able to spend alone. A typical personal setup pairs an AI assisted node with a human circuit breaker node under 2/2 threshold control: the agent can analyze markets, propose DeFi actions, and compose trades, but canno"
         },
         {
-          "id": "lack-of-open-cross-chain-fabrics",
-          "title": "Lack of  Open Cross-Chain Fabrics",
+          "id": "ai-first-dao-governance",
+          "title": "AI-First DAO Governance",
           "level": 3,
-          "excerpt": "Existing cross chain architectures are sometimes ‘black boxes’, so that no one is aware of who is signing transactions on destination chains. Others are secured by nodes run by a few individuals, often team members. They do not allow anyone to contribute to cross chain signing. They are not ‘public’"
+          "excerpt": "ContinuumDAO is built for a future in which AI agents govern alongside humans . An MPA wallet with veCTM attached to its node can act as a Citizen of the DAO: with enough voting power, its agent can write proposals , vote on Treasury, Admin, Decision, and Constitution matters, and evaluate proposal "
         },
         {
-          "id": "security-relies-on-staking-alone",
-          "title": "Security Relies on ‘Staking’ Alone",
+          "id": "fragmented-chains-and-defi-silos",
+          "title": "Fragmented Chains and DeFi Silos",
           "level": 3,
-          "excerpt": "When a cross chain messaging system relies on node runners staking on their nodes alone, then the issue, as the volume grows, is that the value of the staking would become low compared to the value of the traffic itself. There is not a good enough incentive to avoid foul play. Cross chain signing mu"
+          "excerpt": "Users need uniform access to the most important web3 DeFi protocols across chains — not a patchwork of browser extensions, key exports, and opaque bridges. The MPA wallet supports Bitcoin (SegWit and Taproot), Ethereum and other EVM compatible assets , and — as the network expands — many Ed25519 cha"
         },
         {
-          "id": "the-number-of-chains-in-a-network-is-not-scaleable",
-          "title": "The Number of Chains in a Network is not Scaleable",
+          "id": "fully-decentralized-mpc-custody",
+          "title": "Fully Decentralized MPC Custody",
           "level": 3,
-          "excerpt": "Sometimes (and this includes some of the most popular bridges) the cross chain signing relies on multi signature wallets. The issue here is that multiple signatures are costly. It is hard to upgrade every node to include a new chain that they must sign on. This will prevent support for all but a few"
+          "excerpt": "Threshold shares and encrypted wallet state live only on nodes deployed by users . The wallet software is self contained on each node ; the sole on chain dependency for fees is a DAO governed smart contract . Operators can back up encrypted node data, share custody among family or friends via higher"
         },
         {
-          "id": "technical-challenges-in-expanding-the-cross-chain-network",
-          "title": "Technical Challenges in Expanding the Cross-Chain Network",
+          "id": "the-wallet-must-work-without-continuumdao",
+          "title": "The Wallet Must Work Without ContinuumDAO",
           "level": 3,
-          "excerpt": "Systems secured by zkProofs are difficult to expand. The zkProof is computationally expensive and requires expensive hardware, which can be challenging for most node runners to implement. Generating a zkProof from an EVM to a non EVM is difficult (impossible?) to achieve."
+          "excerpt": "MPA wallet node software is installed and run by users themselves. ContinuumDAO is not required for day to day custody, signing, DeFi, or AI assisted flows — all of that runs on the operator’s nodes. ContinuumDAO provides optional software updates and a DAO governance framework to organise fee contr"
         },
         {
-          "id": "lack-of-protocol-level-security",
-          "title": "Lack of Protocol Level Security",
+          "id": "cross-chain-dapps-need-open-mpc-secured-infrastructure",
+          "title": "Cross-Chain dApps Need Open, MPC-Secured Infrastructure",
           "level": 3,
-          "excerpt": "Systems that use zkProofs and relayers of those proofs do not have protocol level security. It is up to the dApp to choose the relayer and they can switch at any time from within their frontend to an insecure or malicious relayer, unbeknown to the users of those dApps."
+          "excerpt": "Existing cross chain architectures are often ‘black boxes’ where no one knows who signs on destination chains, or they are run by a few team members behind a company that could disappear. When security relies on staking alone , the value at stake falls behind the value of traffic as volume grows. Sy"
+        },
+        {
+          "id": "cross-chain-signing-must-scale-beyond-multi-sig-and-zkproof-relayers",
+          "title": "Cross-Chain Signing Must Scale Beyond Multi-Sig and zkProof Relayers",
+          "level": 3,
+          "excerpt": "Multi signature bridges are costly — multiple on chain signatures consume gas and are hard to upgrade for new chains. zkProof systems are computationally expensive, require expensive hardware, and struggle to expand from EVM to non EVM chains. An MPC signature is a single signature with limited gas "
         },
         {
           "id": "how-is-continuumdao-different",
           "title": "How is ContinuumDAO Different?",
           "level": 2,
-          "excerpt": "Our cross chain network, called the Continuum, is run by a DAO and designed for autonomous operation. All critical operations and financial transactions depend on on chain voting. There is no central ‘team’. The MPA wallet is a core MPC product: an AI first wallet with a rich frontend for complete m"
+          "excerpt": "The MPA wallet is ContinuumDAO’s flagship MPC product: an AI first wallet with a rich frontend for complete manual operation — fully decentralized self custody of BTC (SegWit and Taproot), Ethereum / EVM assets , and (in rollout) Ed25519 chains such as Solana and NEAR — without a Private Key , with "
         },
         {
           "id": "the-current-situation",
@@ -2485,13 +3317,13 @@
           "id": "governance",
           "title": "Governance",
           "level": 2,
-          "excerpt": "The adoption of a DAO for Continuum is not just a governance choice; it is a strategic necessity to unlock the full potential of multi chain dApps. By leveraging the DAO model, we ensure that the services remain decentralized and transparent. Here’s why a DAO is the ideal structure to control permis"
+          "excerpt": "The adoption of a DAO for Continuum is not just a governance choice; it is a strategic necessity to unlock the full potential of multi chain dApps — and to pioneer AI first, human overridable governance . By leveraging the DAO model, we ensure that the services remain decentralized and transparent w"
         },
         {
           "id": "why-have-we-built-a-dao",
           "title": "Why Have we Built a DAO?",
           "level": 3,
-          "excerpt": "The adoption of a DAO for Continuum is not just a governance choice; it is a strategic necessity to unlock the full potential of multi chain dApps. By leveraging the DAO model, we ensure that the services remain decentralized and transparent. Here’s why a DAO is the ideal structure to control permis"
+          "excerpt": "The adoption of a DAO for Continuum is not just a governance choice; it is a strategic necessity to unlock the full potential of multi chain dApps — and to pioneer AI first, human overridable governance . By leveraging the DAO model, we ensure that the services remain decentralized and transparent w"
         },
         {
           "id": "governance-model",
@@ -2509,19 +3341,25 @@
           "id": "the-continuumdao-token",
           "title": "The ContinuumDAO Token",
           "level": 2,
-          "excerpt": "ContinuumDAO has implemented its token model on Linea mainnet. Any holder of ContinuumDAO’s token (called CTM) can stake them into an NFT called veCTM (see the code on github). There will be a buy pressure for CTM, since it is used as a payment token by dApps for cross chain services. This will coun"
+          "excerpt": "ContinuumDAO has implemented its token model on Linea mainnet. Any holder of ContinuumDAO’s token (called CTM) can stake them into an NFT called veCTM (see the code on github). Staking as subscription is the main use of CTM . Operators who attach veCTM to their MPA wallet node receive free MPA walle"
         },
         {
           "id": "vested-token-model",
           "title": "Vested Token Model",
           "level": 3,
-          "excerpt": "ContinuumDAO has implemented its token model on Linea mainnet. Any holder of ContinuumDAO’s token (called CTM) can stake them into an NFT called veCTM (see the code on github). There will be a buy pressure for CTM, since it is used as a payment token by dApps for cross chain services. This will coun"
+          "excerpt": "ContinuumDAO has implemented its token model on Linea mainnet. Any holder of ContinuumDAO’s token (called CTM) can stake them into an NFT called veCTM (see the code on github)."
+        },
+        {
+          "id": "staking-as-subscription-the-primary-use-of-ctm-vectm",
+          "title": "Staking as Subscription — the Primary Use of CTM / veCTM",
+          "level": 3,
+          "excerpt": "Staking as subscription is the main use of CTM . Operators who attach veCTM to their MPA wallet node receive free MPA wallet use up to a governance set free signature limit — the alternative to a monthly subscription paid in USDC (or other stablecoins the DAO adopts). Heavier use, or nodes without s"
         },
         {
           "id": "the-mpc-network-and-the-mpa-wallet",
           "title": "The MPC Network and the MPA Wallet",
           "level": 2,
-          "excerpt": "ContinuumDAO’s MPC network, Multi Party Agent (MPA) wallet , and staking control panel are currently being built. Through the control panel, anyone will be able to see which nodes are signing cross chain messages and claim CTM rewards for qualified participation. ContinuumDAO is the first public MPC"
+          "excerpt": "ContinuumDAO’s flagship Multi Party Agent (MPA) wallet and public MPC network — including the staking control panel — are currently being built. Through the control panel, anyone will be able to see which nodes are signing cross chain messages and claim CTM and ETH rewards for qualified participatio"
         },
         {
           "id": "nodes-the-core-building-block",
@@ -2533,13 +3371,13 @@
           "id": "the-multi-party-agent-mpa-wallet",
           "title": "The Multi-Party Agent (MPA) wallet",
           "level": 3,
-          "excerpt": "The MPA wallet (docs) is ContinuumDAO’s flagship MPC product — AI first , with a rich frontend for full manual use: AI first control — a built in AI agent harness on every node proposes trades, runs technical analysis, and invokes DeFi protocol tools; humans (or other nodes) Accept or Reject before "
+          "excerpt": "The MPA wallet (docs) is ContinuumDAO’s flagship MPC product — AI first , with a rich frontend for full manual use: AI first control — a built in AI agent harness on every node proposes trades, runs technical analysis, invokes DeFi protocol tools, and participates in DAO governance (propose, Forum d"
         },
         {
           "id": "fully-decentralized-custody",
           "title": "Fully decentralized custody",
           "level": 3,
-          "excerpt": "Many MPC wallets rely on vendor hosted databases to store key shares. The MPA wallet does not : threshold shares and encrypted wallet state live only on nodes deployed by users . The wallet software is self contained on each node ; the sole on chain dependency for fees is a DAO governed smart contra"
+          "excerpt": "Many MPC wallets rely on vendor hosted databases to store key shares. The MPA wallet does not : threshold shares and encrypted wallet state live only on nodes deployed by users . Users install and run the node software themselves — on a home machine or VPS. The wallet software is self contained on e"
         },
         {
           "id": "public-mpc-nodes-and-rewards",
@@ -2569,16 +3407,16 @@
           "id": "utility",
           "title": "Utility",
           "level": 3,
-          "excerpt": "MPA wallet — AI first MPC self custody on user run nodes , with a rich frontend for full manual control (no vendor database of key shares), direct web3 protocol trading without a Private Key, encrypted backup / recovery, optional eject to a standard private key wallet, and AI assisted workflows C3Ca"
+          "excerpt": "Staking as subscription — veCTM attached to your node unlocks free MPA wallet use up to the free signature limit (alternative to monthly USDC subscription); the primary use of CTM , locking an increasing share of total supply as adoption grows Agentic DAO governance — attached veCTM grants voting po"
         },
         {
           "id": "ecosystem-development",
           "title": "Ecosystem Development",
           "level": 1,
-          "excerpt": "There will be a grant program for new projects using Continuum. This could be either a grant of CTM, or other tokens from the treasury, or a time limited reduction in fees for usage of Continuum. The DAO will assist new projects that wish to use Continuum. This will be in the form of coding support,"
+          "excerpt": "At the discretion of the DAO, there will be a grant program for new projects using Continuum. This could be either a grant of CTM, or other tokens from the treasury, or a time limited reduction in fees for usage of Continuum. The DAO will assist new projects that wish to use Continuum. This will be "
         }
       ],
-      "excerpt": "15th August 2026 An open public cross chain network secured by Multi Party Computation — and the Multi Party Agent (MPA) wallet , an AI first flagship MPC product (with a rich frontend for full manual control) for custody without a Private Key , AI assisted trading , and optional cross chain signing",
+      "excerpt": "17th August 2026 An AI first DAO and wallet, with humans in the loop . ContinuumDAO’s Multi Party Agent (MPA) wallet extends that model from custody to DAO governance — AI agents can propose , debate on the Forum, evaluate proposals, and vote on chain, alongside humans who retain control through MPC",
       "url": "https://docs.continuumdao.org/ContinuumDAO/WhitePaper"
     },
     {
@@ -2587,7 +3425,7 @@
       "section": "",
       "headings": [],
       "sections": [],
-      "excerpt": "<h1 ContinuumDAO</h1 Meet the ContinuumDAO A trustless Secure Multi Party Computation node network called the Continuum and run worldwide by a DAO. <! <span style=\"color:green;font weight:700;font size:20px\" markdown color font styles </span",
+      "excerpt": "<h1 ContinuumDAO</h1 Meet the ContinuumDAO An AI first DAO and Multi Party Computation wallet, with humans in the loop. <! <span style=\"color:green;font weight:700;font size:20px\" markdown color font styles </span",
       "url": "https://docs.continuumdao.org/README"
     }
   ]