Contracts and native modules
Testnet
Monolythium’s design separates two execution surfaces:
- Native modules for protocol-owned behavior. The presence of a module name or SDK encoder does not prove release activation.
- Rust/RISC-V contracts for application-specific logic compiled into deterministic Mono RISC-V artifacts.
New applications should start with the verified read-only RPC and exact SDK release. This site does not currently publish a supported general state-changing native-module or application-contract deployment path. Do not infer one from internal source names or historical drafts.
- Native module catalog Locked — activation and unavailability boundaries; no module IDs or write ABI
- Dapp contracts with Mono DevKit Planned — no certified deploy/call pipeline
- Native module map Testnet — developer-facing module IDs and call model
- Name registry API Planned — name reads and writes unavailable
- CLOB native module Locked — market reads and writes unavailable
- Agent native module boundary Planned — planned and unavailable for economic execution