MSG Chain
One entry for official docs, the whitepaper system, the machine-readable whitepaper layer, and stricter boundaries for indexer retention proof, explorer fail-closed, and WSS anchor handoff.
The public site layer carries concise product explanations, onboarding paths, and the latest outward-facing capability changes.
When a visitor needs stricter contract-runtime boundaries, canonical roles, economic-seconds review logic, indexer retention proof, explorer fail-closed, and WSS anchor boundaries, the whitepaper subsite is the next layer.
The dynamic graph keeps cross-module browsing available so runtime, registry, consensus, proof, and machine-entry relationships stay easy to trace.
The docs portal gives visitors a lightweight official entry while the whitepaper subsite carries the stricter topology, graph, proof chain, machine entry, and boundaries for indexer retention proof, explorer fail-closed, and WSS anchor handoff. Both follow the same content line with different narrative intensity.
Open the whitepaper home to inspect the executive summary, architecture map, proof chain, and verified boundaries such as wasm_migrate, reply_on, indexer retention proof, explorer fail-closed, and WSS anchor handoff.
Whitepaper Home Runtime BoundaryUse the dynamic graph to browse relationships across contract runtime, registry, DAR review timing, and the rest of the capability surface.
Knowledge Graph Knowledge BrowserKeep browsing technology, economics, governance, and developer entry points through the lighter public site layer, then dive into the strict layer when needed.
Technology DevelopersThe 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 HintsUse module exports and chunk indexes when an integration needs stable metadata, routing tags, public URLs, boundary clauses, and retrieval-friendly segments.
Module Exports Chunk IndexThird-party teams can start from the integration guide, Telegram crawl flow, RAG ingest flow, FAQ router template, and minimal demo clients before binding stricter indexer or explorer exports to production-candidate services.
Integration Guide Demo ClientsThe whitepaper strict layer now documents the `@msg-chain/sdk` alpha surface as a local-candidate entry, making its module boundary machine-readable without upgrading it into a signed public production SDK claim.
SDK Boundary SDK JSONA new machine-readable business example catalog now exposes contract-first example payloads for payment, micropayment, registry, oracle, routing, and receipt or event samples, while still keeping No-Go and fail-closed boundaries for public production usage.
Business Catalog Examples IndexA 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 IndexThe strict layer now exposes a source-backed formal contract and API index for schema discovery, core contract references, OpenAPI surfaces, and release-level manifests without upgrading them into a signed public production release claim.
Formal Contracts Core Contract JSONThe whitepaper now also publishes a dedicated sandbox strategy file to make the current testnet and faucet posture explicit: reserved where needed, but still fail-closed for public launch claims.
Sandbox Strategy Chain ConfigThe whitepaper now exposes a dedicated Web3 protocol page for AIPAY, micropayment, trust accounting, routing registries, oracle registry, bridge adapter boundaries, and their local Block1 or Q1Q2 evidence chain.
Open Web3 Protocols Atomic Modular Boundary