Learn Monolythium

Testnet

Monolythium has a registered Rust-native development-testnet profile with ML-DSA-65 account and consensus signing and clustered operators. Its mempool profile is plaintext. Registry identity is separate from the currently observed stale/degraded endpoint health. This section separates verified concepts from planned product surfaces.

Two postures govern everything below. First, the Foundation decides; it does not vote. On-chain governance was removed (see Governance — no on-chain Locked). Second, a concept, SDK type, reserved module name, or historical snapshot is not activation evidence. Only the explicitly verified testnet facts and read-only interfaces are current.

Start here

Three pages, in order, give you the load-bearing mental model:

• What Monolythium is Testnet — the bounded project and registered-testnet shape in plain prose
• Anchors, waves, vertices Testnet — the DAG commit model
• Consensus (Starfish-C) Testnet — the DAG-BFT scheme that finalizes anchors

Concepts in dependency order

Read in this order if you are new. Each concept assumes only what came before it.

#	Page	Why now
1	What Monolythium is	Frames the rest
2	Anchors, waves, vertices	Learn the native commit units
3	Consensus (Starfish-C)	How anchors finalize
4	Post-quantum cryptography	Where PQ applies and where classical residuals remain
5	Addresses and names	domain-separated BLAKE3-20 + bech32m + human-readable names
6	Clusters and DVT	Who actually produces anchors
7	Two denominations	Planned public/private model; no private-value path
8	Native CLOB	Locked spot-order-book design; no economic path
9	Agent commerce	Planned taxonomy; economic execution is unavailable
10	Economics and rewards	Locked design values; no active economic schedule
11	Governance — no on-chain	Why the Foundation decides, not the chain
12	Threat model	What can go wrong, and what we have planned

Architecture concepts

• Addresses and planned names Testnet — verified typed bech32m display; name transactions unavailable
• Clusters and DVT Testnet — active topology is four 10-operator clusters with 7-of-10 certificates
• Two denominations Planned — no private-value or conversion path is released
• Native CLOB Locked — no supported market or trade path is released
• Agent commerce Planned — roadmap taxonomy; no supported economic actions

Posture

• Economics and rewards Design — locked design values, not active economics or a yield promise
• Governance — no on-chain Locked — no on-chain voting or memo signal layer; public authority details remain bounded
• Bridges and interop Planned — no in-tree bridge; external providers under evaluation
• Hardware sovereignty (Monarch OS) Unavailable — planned appliance criteria; no public image or certified hardening profile
• Threat model Locked — stall, fork, double-sign, liquidation-cascade-during-halt
• Fork as exit Locked — why on-chain governance is rejected, why forking is legitimate dissent

Reference

• Glossary Locked — current terms and explicit release boundaries
• Whitepaper v5.1 (June 2026; historical) — superseded status record; original present-tense body is intentionally not reproduced
• Network parameters — registered identity pins, target timing, topology, and display decimals

If you’re …

An end user — your next stop is /use/. Wallets, names, sending and receiving LYTH.

An app developer — once the concepts above click, jump to /build/. SDK, RPC, contracts.

An agent developer — read the unavailable agent-commerce boundary, then use /agents/ for safe read-only MCP scope.

A node operator — read Clusters and DVT and Hardware sovereignty here, then go to /operate/.

An exchange integrator — read Post-quantum cryptography and Addresses and names here, then go to /exchanges/.

A researcher — start with Consensus (Starfish-C), then walk the Feature and design list.