What Monolythium is

Testnet

Monolythium is a Rust/RISC-V-native Layer-1 under development. Its registered public development-network identity is the value-less, wipeable testnet-69420; mainnet is not running. On 2026-07-16 the public RPC matched that identity but its finalized state was stale/degraded, so the network must not be described as live. The long-term vision includes machine-assisted applications, but that vision is not evidence that agent custody or economic execution is available.

Verified registered shape

Network: chain ID 69420, full identity pinned by the chain registry and genesis.
Consensus: Starfish-C DAG-BFT with four ten-operator clusters. Seven independent ML-DSA-65 signatures form each cluster round certificate.
Signing: ML-DSA-65 for native account admission and consensus signing.
Transport: the registered profile uses ML-KEM-768 Noise.
Mempool: plaintext. There is no encrypted, sealed, private-send, or threshold-decrypted lane.
Execution: native Rust/RISC-V, not EVM-compatible execution.
Governance: no on-chain vote changes protocol state or controls an inflation parameter.

The exact registered release is v0.4.0-testnet; the full registry commit, genesis, runtime commit, binary digest, and separate point-in-time health observation are listed in Network parameters.

Explicitly unavailable

Agent-wallet custody, protocol spending policy, autonomous signing or submission, booking, payment, escrow, dispute, and review.
A supported CLOB market or other economic native-module write flow.
A private-denomination value path or confidential-transfer flow.
An in-tree bridge, bridge verifier, or Foundation-operated production route.
No supported SLH-DSA account, backup key, or emergency-rotation path.

Reserved module names, SDK types, source registrations, and historical whitepaper text are not activation evidence. The standalone Stele public-web preview is hosted at stele.monolythium.com with keyless reads; economic writes and hosted signing are disabled.

Public integration surface

The documented safe starting point is the exact @monolythium/[email protected] package, verified read-only RPC calls, typed bech32m address helpers, local deterministic signing tests, and wallet-auth verification. Authentication proves control for one challenge; it does not authorize a transaction.