Reference

Locked

This section is the catalog. It points to the public references that other docs derive from.

• Release references — diligence, whitepaper, and feature and design list.
• Reference catalogs — JSON-RPC methods, CLI boundaries, MCP release status, native module catalog, error codes, and network parameters.

When you’re searching for a fact, start here. When you’re learning a concept, start at /learn/.

Start here

The three load-bearing references everyone reaches for first:

• Diligence Locked — canonical facts, source posture, audit gates, and stale-claim warnings
• Whitepaper v5.1 (June 2026; historical) Superseded — archived status record; original present-tense body is not reproduced
• Network parameters Testnet — registered chain identity, topology, target timing, and display decimals

Release References

These pages describe the release shape at a higher level than the generated catalogs.

• Diligence Locked — current facts, observed health, source availability, and stale-claim warnings
• Whitepaper v5.1 (June 2026; historical) Superseded — reconciliation-only archive; historical body intentionally omitted
• Feature and design list Locked — public feature inventory and design posture
• Stele web app Preview — hosted at stele.monolythium.com, with private wallet-owned provider-listing drafts, publication and economic actions disabled, and explicit wallet/MCP trust boundaries

Reference catalogs

These describe surfaces. They mirror what’s in the code; if they drift, the code wins and the page is the bug.

• Network parameters Testnet — registered chain id 69420, identity pins, timing targets, topology, and display decimals
• Native module catalog Locked — module activation posture and caller guidance
• Genesis Locked — registered testnet identity 0xe22733f4…; mainnet TBD
• JSON-RPC Testnet — native lyth_* methods and gated diagnostics
• CLI boundary Locked — no generated, versioned public command catalog is certified
• MCP surface status Preview — live keyless hosted OAuth service with authenticated runtime discovery plus a separate public local exact-three prerelease
• Error codes Testnet — typed errors from the chain, indexed by code

Tooling references

Release-status pages for public tooling. A source file or page is not evidence of a package, deployment, or supported install path.

• Local lyth_mcp Stele profile Preview — v0.1.0 GitHub prerelease with exactly three read/status tools; no keys, signing, or transactions
• SDK (mono-core-sdk) Testnet — published TypeScript 0.6.8, source-pinned Rust, and wallet-auth v1
• Monarch OS Unavailable — planned node-appliance design; no certified public image or operator procedure

Vocabulary and history

• Glossary Locked — current terms and explicit release boundaries
• Audit history Locked — public audit-status boundary; no internal working material

Explorer

• Monoscan (explorer) Testnet — verified public explorer boundary; no agent-economic or native-market panes are claimed

License

• License Locked — binding terms come from each exact published artifact; mono-core remains unpublished

How to read this section

The reference pages are intentionally dry. They do not teach; they document. If you find yourself wanting more narrative, the corresponding /learn/ page is the right home for that material — file an issue if it’s missing or sparse.

When citing the docs in code reviews or external documents, prefer linking to the whitepaper or feature and design list for release posture, and to the catalogs for exact method names or flags.

If you’re …

An app developer chasing an RPC method, the JSON-RPC catalog is canonical; the /build/rpc/* pages add examples.

A node operator chasing a CLI flag, the CLI reference is canonical; the /operate/ pages add operational context.

An agent developer evaluating MCP access should start with the MCP surface status and its authority boundaries.

An exchange integrator chasing a signature scheme should start with the current feature and design list and network parameters. The v5 whitepaper is archived and non-normative.

A researcher chasing release posture, walk the Feature and design list.