# Monolythium

> Canonical public facts for LLMs and search systems. Last updated: 2026-07-16.

Monolythium is a Rust/RISC-V-native Layer-1 project for agent-native commerce. Development network 69420 is registered and its RPC is reachable, but repeated checks on 2026-07-16 remained at height 74,907 with latest block timestamp 2026-07-08T22:39:05Z. Treat it as degraded/stale, not as liveness or production-settlement evidence. Mainnet 69422 is reserved and is not running.

Canonical sources:
- Diligence: https://monolythium.com/diligence
- Docs diligence: https://docs.monolythium.com/diligence/
- Tokenomics: https://docs.monolythium.com/learn/economics-and-rewards/
- Network parameters: https://docs.monolythium.com/reference/network-parameters/
- Feature and design list: https://docs.monolythium.com/reference/features/
- Whitepaper: https://docs.monolythium.com/reference/whitepaper/2026-05-17/
- Machine-readable facts: https://monolythium.com/facts.json
- Full LLM context: https://monolythium.com/llms-full.txt

Current facts:
- Registered development chain id: 69420; observed stale, not a current public-network advancement claim
- Target initial-supply design (verify against finalized genesis state): 100,000,000 LYTH
- Native decimals: 18
- Execution: Target design: Rust source compiled to deterministic RISC-V artifacts. Public-network contract execution is not claimed as activated, and Monolythium is not EVM-compatible at execution.
- Consensus: Starfish-C; reference paper: https://nikitapolyanskii.com/writings/2025-44-starfish/preprint.pdf
- Cryptography posture: The protocol profile uses ML-DSA-65 signing and describes a custom ML-KEM-768 KEM-Noise IK-style transport handshake with a standard plaintext mempool. The handshake still requires independent cryptographic review, and the stale public head is not activation evidence. The in-tree bridge, SLH-DSA emergency registry, and confidential amount-transfer construction were removed. Application-layer proof verification remains disabled pending a new post-quantum design. This is not a claim that the entire stack is post-quantum.
- Governance: No on-chain governance voting or governance-adjustable inflation path.
- Browser-wallet boundary: The browser wallet uses standard BIP-39 mnemonic recovery to ML-DSA-65 and an Argon2id/XChaCha20-Poly1305 encrypted extension-local vault. PQM-1 was removed. A mnemonic stays in the wallet and is never entered into Stele or a hosted MCP service.
- Stele: Standalone web product with deployment still release-gated. Intended public catalog discovery does not require a wallet; browser-wallet approval is the authority boundary for user actions.
- Hosted Stele MCP tool names (exactly two): stele_search_services, stele_create_booking_draft
- Hosted Stele MCP: Hosted MCP is keyless and exposes exactly two non-economic tools: stele_search_services and stele_create_booking_draft. It cannot hold a wallet, construct arbitrary calls, sign transactions, or submit economic transactions.
- Local Stele MCP: The isolated local Stele MCP profile exposes exactly three read/status tools: connection, public search, and dedicated-wallet status. It has no Stele transaction tool.

Deprecated claims:
- Cosmos SDK chain as the current architecture.
- EVM-compatible execution or Solidity deployment as the launch identity.
- 8-decimal LYTH.
- On-chain governance voting or governance-adjustable inflation.
- Pre-May-2026 whitepaper versions as canonical public references.
- Public ADR pages as the public source of truth.
- An undated claim that development network 69420 is currently live or advancing.
- Confidential amount transfer as merely gated; its prior construction was removed.
- The eight-primitives agent-commerce suite as an activated public-network ABI.
- Stele as an embedded desktop-wallet marketplace.