Native module catalog
Locked
This catalog deliberately separates a named or encoded surface from a currently supported surface. The registered public development-network profile is value-less and resettable; registration does not assert liveness. Do not use real funds.
Availability rules
Section titled “Availability rules”- An SDK export, request shape, address, module ID, source file, or historical document does not prove chain activation.
- An unavailable-method error is not an invitation to bypass a release gate.
- A write path is supported only when the active release registry, runtime provenance, node capability response, wallet support, and current public documentation agree.
- This site currently verifies only a small read-only RPC subset. It does not publish a general native-module write contract.
Explicitly unavailable surfaces
Section titled “Explicitly unavailable surfaces”| Surface | Current posture |
|---|---|
| In-tree bridge, bridge verifier, route registry, and Foundation-operated route | Removed / unavailable |
| Agent commerce and agent identity execution | Planned / unavailable |
| Spending policy and delegated agent-wallet execution | Planned / unavailable |
| Booking, payment, escrow, dispute, and review | Planned / unavailable |
| SLH-DSA account, backup-key, and emergency-rotation path | Unreleased / unavailable |
The package @monolythium/[email protected] still exposes types or encoders associated with some historical, reserved, or unreleased designs. Those exports are not deployment or activation evidence and must not be used to claim a production path.
Integration rule
Section titled “Integration rule”Start with runtime identity checks. Do not construct or sign a native-module write from this page. For an integration that needs a state-changing module, require a separately versioned release statement and current activation evidence before implementation.