Native module map
Native modules are protocol-owned Rust surfaces. A symbol, encoder, reserved module ID, or type in an SDK package is not evidence that a module is active on the connected chain.
The public network is a value-less, resettable testnet. Do not use real funds. Before relying on any state-changing module, pin the chain identity and obtain activation evidence from the active release registry and the node itself. This documentation does not currently publish a supported state-changing native-module quickstart.
Current public boundaries
Section titled “Current public boundaries”| Surface | Documentation posture |
|---|---|
| Chain, round, peer, and runtime-provenance reads | Available through the verified read-only RPC subset |
| Token, name, CLOB, delegation, privacy, oracle, and other module writes | Not documented here as a supported integration contract; verify separately against the active release |
| Agent identity and agent-commerce modules | Planned / unavailable on a supported product path |
| Spending policy, booking, payment, escrow, dispute, and review | Planned / unavailable |
| In-tree bridge module or verifier | Removed / unavailable |
| SLH-DSA account, backup-key, or emergency-rotation module | Unreleased / unavailable |
The published @monolythium/[email protected] package contains some encoders and types for reserved, historical, gated, or unreleased surfaces. Treat them as serialization helpers only. They do not establish deployment, activation, audit status, wallet support, or permission to move value.
Safe discovery
Section titled “Safe discovery”Use the verified read-only methods in the typed RPC client to pin chain and runtime identity. Do not probe an unknown native module with a signed transaction, and do not infer activation from a successful local encoding operation.
No public Stele, browser-wallet, desktop-wallet, hosted-MCP, or local-MCP path currently supports agent custody, policy-controlled signing, submission, booking, payment, or escrow.