Documentation
One entry for official docs, the whitepaper system, AI constitution and communications surfaces, source autonomy and resource lifecycle pages, the machine-readable whitepaper layer, and stricter proof boundaries. Governance and authority rules follow the subject-neutral principle: they do not depend on whether the subject is human or AI. Signing, deployment and treasury actions still require human approval.
Official Documentation
The public site layer carries concise product explanations, onboarding paths, and the latest outward-facing capability changes.
dApp Developer Docs
148 site-hosted development references. Every catalog link points to a local copy, and the page states clearly that the chain is not launched, some content is still planned, and each document has not been independently verified.
Open dApp Docs
Whitepaper System
When a visitor needs stricter contract-runtime boundaries, canonical roles, economic-seconds review, the AI constitution, communications, resource lifecycle, source autonomy, future Node Manager and private-control semantics, plus indexer data-retention rules, how the explorer behaves when a lookup cannot be confirmed, and WSS anchor boundaries, the whitepaper subsite is the next layer.
Knowledge Graph
The dynamic graph keeps cross-module browsing available so runtime, registry, consensus, proof, and machine-entry relationships stay easy to trace.
MSG 公链开发史
Browse public development progress over time, event details, and how far each item has actually gotten.
打开开发史
白皮书发展史
Documentation Portal
The docs portal gives visitors a lightweight official entry, while the whitepaper subsite carries the stricter topology, graph, proof chain, and machine entry, plus guidance on the AI constitution, communications, resource lifecycle, source autonomy, future Node Manager, private control, and L4/L5/LX. It also covers indexer data-retention rules, how the explorer behaves when a lookup cannot be confirmed, and WSS anchors. Both follow the same content line, at different levels of detail.
Open Whitepaper System
Open the whitepaper home to see the executive summary, architecture map, proof chain, and boundaries such as contract migration (wasm_migrate), reply_on, indexer data-retention rules, how the explorer behaves when a lookup cannot be confirmed, and WSS anchors.
Whitepaper Home
Runtime Boundary
Open Dynamic Knowledge Graph
Use the dynamic graph to browse relationships across contract runtime, registry, DAR review timing, and the rest of the capability surface.
Knowledge Graph
Knowledge Browser
Read Official Docs
Keep browsing technology, economics, governance, and developer entry points through the lighter public pages, then open the whitepaper when you need to check the detail.
Technology
Developers
Chain Integration Facts
Before writing client code, read the stable integration facts: chain ID, umsg with 9 decimals, the 44-character non-bech32 address format, default ports and route ownership, the JSON types.Transaction model with Dilithium-5 signatures, the official SDK as the only signing client, and the fact that no public endpoint is published yet.
Integration Facts JSON
Developer Page
Machine Entry for AI & RAG
The whitepaper subsite now exposes a stable `agent_entry.json`, topic-routing hints, module exports, chunk indexes, and stricter indexer or explorer boundary references for external bots or RAG services.
Agent Entry JSON
Retrieval Hints
Machine-Readable Exports
When an integration needs stable metadata, routing tags, public URLs, boundary notes, and retrieval-friendly segments, it can use the module exports and chunk indexes directly.
Module Exports
Chunk Index
Integration Examples
Third-party teams can start from the integration guide, Telegram crawl flow, RAG ingest flow, FAQ router template, and minimal demo clients, then connect the stricter indexer and explorer exports and production-preparation endpoints as needed.
Integration Guide
Demo Clients
SDK Alpha Layer
The whitepaper now documents the `@msg-chain/sdk` alpha surface as a local-development candidate entry, with a machine-readable module boundary. This does not upgrade it into a signed public production SDK.
SDK Boundary
SDK JSON
Business Example Library
A new machine-readable business example catalog publishes contract-first samples for payment, micropayment, registry, oracle, routing, and receipt or event samples. These samples are for development reference and are not open to production use yet.
Business Catalog
Examples Index
AI Quick Start Pack
A new quick-start layer now gives external AI agents and developer teams a shorter path into MSG contract and dApp onboarding, while keeping the release process, approvals, and production boundaries explicitly guarded.
Quick Start JSON
Quick Start Index
Formal Contract Packs
The whitepaper now publishes a formal contract and API index tied to the source code, for schema discovery, core contract references, OpenAPI surfaces, and release-level manifests. This is still not a signed public release.
Formal Contracts
Core Contract JSON
Reject-by-Default Sandbox
The whitepaper provides machine-readable entries (agent_entry.json / developer_entry.json), quickstart packs, contract references and business example catalogs, so external AI can onboard quickly in the recommended order and start building dApps.
Sandbox Strategy
Chain Config
Web3 Contract-First Modules
The whitepaper now provides a dedicated Web3 protocol overview covering AIPAY, micropayment, trust accounting, routing registries, oracle registry, and bridge adapter, along with their local test evidence.
Open Web3 Protocols
Atomic Modular Boundary
Autonomy, Communications & Resource Surfaces
The whitepaper now splits the AI constitution, communications, resource lifecycle, and source autonomy into separate capability pages, and adds guidance for future products such as private control, Node Manager, and L4/L5/LX. Visitors can read the public overview first, then go deeper when needed.
AI Constitution
Source Autonomy
dApp Developer Docs
148 site-hosted guides for smart contracts, AI Agents, DeFi protocols, and dApps, with public safety screening done and the necessary boundary notes kept.
Open dApp Docs
AI & Automation Entry
The machine-readable entry map for AI and automated agents, with the six-step development path from onboarding to dApp delivery and topic-routing hints.
Agent Entry JSON
