English | 简体中文
dMsg is an ICPanda DAO product for private collaboration between people and agents. Start with the product overview and downloads, then choose the implementation or protocol guide below.
This index was reviewed against public source 9fd70dca on 2026-10-24. Documents describe source behavior unless they identify a specific release, deployment or measurement. Source changes, installable releases, production deployment and independent audits are separate facts. Internal design documents are located through AGENTS.md; their contents are not published here.
| Topic | Guide |
|---|---|
| Install and update | Downloads · Release scripts |
| Desktop workspace | Desktop app · Current design system |
| Credentials and file references | Desktop IDs, references, developer workflows and verification (简体中文) |
| Command line and MCP | CLI and daemon · Agent connector |
| Reusable Rust core | dmsg_client |
| Web and application integration | SDK · Account adapter example · Bridge page |
| Local verification | Integration tests · Client vectors · Agent vectors |
| Topic | Maintained documentation |
|---|---|
| Architecture, capacity and multiple instances | English · 简体中文 |
| Canister roles, upgrades and validation | English · 简体中文 |
| Protocol index, signatures and receipts | English · 简体中文 |
| Encryption and recovery boundaries | Encryption · Accounts and roots |
| Approved credential use and secret sharing | Secrets contract and verification |
| Multisig wallets | Product scope · Public contract · Desktop implementation |
| Legacy data and migration | Read-only inventory · Personal archives · Freeze evidence |
The protocol index also covers cloud delivery, channels, browser login, dmsg-connect, commerce 2, Agent Delegation and Mail events. Each canister README owns its detailed limits, measurements and operations; Candid and shared vectors define the executable interface.
- The main clients are the desktop app and CLI, sharing the Rust daemon. Web applications use dmsg-connect/1; the former browser extension is retired. There is no mobile app yet.
dmsg_useranddmsg_directoryalready contain production user data. Stable-layout changes require data-preserving upgrades and old-Wasm verification, never reinstallation.- Multisig wallet creation is paused in the desktop app. Existing wallets remain accessible; this does not change the CLI, daemon or hub's creation interfaces. Native secret-file mounts have separate OS, packaging and validation requirements.
- Legacy personal archives remain readable and importable. The old shared-channel inheritance workflow was removed from the public clients; the current channel protocol and legacy evidence formats still serve different purposes.
- The security audit report records the reviewed source, findings, fixes and verification results. Recorded local tests and capacity samples have explicit scopes and are not blanket production acceptance.
Completed design iterations and one-time investigations live in archived/docs/:
- Statement v3 rationale: English · 简体中文. Use the current protocol and CDDL for implementation.
- Desktop design and implementation record. Current component rules live beside the desktop source.
- 2026-10-22 unlock/performance investigation. Its samples and unrun checks retain their original scope.
Superseded daily canister increments are retained in Git history. New behavior belongs in its current topic section, with versioned evidence where needed; do not append a second, conflicting contract. Keep English/Chinese architecture section numbers aligned, update incoming links when moving a document, and regenerate protocol/integration.cddl from its script rather than editing it manually.
Every Markdown topic in this directory has an English name.md and Simplified Chinese name_zh.md counterpart with matching sections. Follow the language switch at the top of each page. CDDL files are shared machine-readable contracts; both languages link to the same definitions.