# Monolythium Canonical Public Context Registry facts pinned as of: 2026-07-07 Website: https://monolythium.com/ Docs: https://docs.monolythium.com/ ## Status A wipeable, value-less public development testnet identity is registered on chain id 69420. The public RPC is reachable, but its finalized state was observed stale/degraded on 2026-07-16 and must not be described as live. Mainnet is not running. ## Registered Public-Testnet Identity These are configured and provenance-reported identity pins, not a claim that the network is currently live. - Network: testnet-69420 - Chain id: 69420 - RPC: https://rpc.monolythium.com - Genesis hash: 0xe22733f4d7e013b93f0f825667fcf852cbf7ad1ca31a42a1bfcf1ab6d79c89a3 - Genesis SHA-256: 5e5e6e0301bf742e2b7e81794ac20ca3fb5f39fdadf54230e1e0c625f9bf2cbb - Release: v0.4.0-testnet - Runtime version: 0.4.0 - Runtime commit: da04f8f5e8391811f80e8d0511dff74311f4e811 - Binary SHA-256: 259c67c1c7fc8bc3f8ca22c82953ea7dc54a9e2ceaa02d0fe0879ab5192f8227 - Topology: 4 clusters x 10 operators; 7-of-10; 2 relays - Safety label: Registered development-testnet identity; Foundation-operated; wipe and re-genesis allowed without notice; do not store value. Registration does not assert current liveness. ## Observed Public-RPC Health - Observed at: 2026-07-16T14:25:32Z - Endpoint reachability: reachable - Registered identity matched: true - Overall health: degraded - Finalized-state liveness: stale - Latest finalized height: 74907 - Latest finalized timestamp: 2026-07-08T22:39:05Z - Interpretation: The public RPC is reachable and reports the registered chain and runtime identity, but finalized state is stale and observed round state is not progressing. Do not describe the network as live. ## Mainnet - Reserved chain id: 69422 - Status: Reserved only. No mainnet network, genesis hash, release, or launch date has been announced. ## Current Network Facts - Execution: Rust/RISC-V-native execution. Monolythium is not EVM-compatible at execution. - Consensus: Starfish-C DAG-BFT. The registered testnet profile specifies four ten-operator clusters; each cluster round certificate requires seven independent ML-DSA-65 operator signatures. - Governance: No on-chain governance voting or governance-adjustable inflation path. - Interop: No in-tree bridge stack or Foundation-operated production route is available. External-provider interoperability is under evaluation. - Timing targets: 4-second rounds; 18-second epochs under the registered profile ## Token Design (Not Active Economics) - Status: Locked design values only. No live issuance, burn, distribution, circulating-supply, reward, sale, or mainnet economic schedule is certified. - Symbol: LYTH - Design initial supply: 100,000,000 LYTH - Design decimals: 18 - Design atomic unit: lythoshi, 1e-18 LYTH - Design annual issuance cap: 8% - Design base-fee burn: 100% ## Cryptography - Account signing: ML-DSA-65 for native transaction admission. - Consensus signing: ML-DSA-65 individual operator signatures; seven of ten signatures form a cluster round certificate under the registered testnet profile. - Transport: ML-KEM-768 Noise transport under the registered testnet profile. - Mempool: Plaintext. There is no encrypted, sealed, threshold-decrypted, or private mempool lane. - Emergency signing: No supported SLH-DSA account, backup-key, or emergency-rotation path is released. - Address derivation: Domain-separated BLAKE3 over canonical public-key bytes, rendered with typed bech32m HRPs. ## Product Availability - Stele: A standalone public-web preview is available at https://stele.monolythium.com/. Its Browser Wallet-authenticated Studio at https://stele.monolythium.com/studio can create, edit, preview, and delete durable wallet-owned private provider-listing drafts; those drafts are unpublished, outside the public catalog, and non-transactable. Browser Wallet authentication proves control of the active address for the application session only; it does not certify provider identity or credentials. The keyless hosted OAuth MCP is live and interoperable with Codex and Claude Code; its authenticated tools/list response is authoritative for the runtime inventory. Only when the authenticated tools/list response includes the exact stele_create_provider_listing_draft name may a client call that tool. Each successful create operation produces exactly one new private, wallet-owned, unpublished provider-listing draft. An idempotent replay returns that same draft without creating another. If the name is absent, the operation is unavailable. It cannot list, read, update, delete, or publish an existing draft, and it cannot sign, submit, or settle a transaction. Production had 0 published services during release validation, so its separate booking-approval draft tool cannot yet produce a successful booking-approval draft. The local exact-three Stele MCP is published as the lyth_mcp v0.1.0 GitHub prerelease. Economic writes and hosted signing are disabled. - Agent commerce: Unavailable: agent-wallet custody, protocol spending policy, signing, submission, booking, payment, escrow, dispute, and review paths are not released. - Bridge: Unavailable: no in-tree bridge stack and no Foundation-operated production bridge route. ## Source And Audit Posture - Public repositories: Verify each public artifact through the monolythium GitHub organization and its exact release metadata; repository presence or source merge does not prove a package or deployment. - Core repository: mono-core is internal and unpublished. The public cannot inspect, clone, rebuild, or fork the current node implementation; source publication and external review remain diligence gates. ## Canonical Sources - Chain registry: https://github.com/monolythium/chain-registry/blob/master/chains/testnet-69420.toml - Chain-registry commit: d9e0f9ff0f7d10fc779ad3ffc11860e68d01ecdf - Network parameters: https://docs.monolythium.com/reference/network-parameters/ - Diligence: https://docs.monolythium.com/diligence/ - Features: https://docs.monolythium.com/reference/features/ - Historical whitepaper: https://docs.monolythium.com/reference/whitepaper/v5/ - PQ posture: https://docs.monolythium.com/learn/post-quantum-cryptography/ - JSON facts: https://docs.monolythium.com/facts.json ## Deprecated Or Stale Claims - Any prior testnet genesis presented as active instead of the full current 0xe22733f4…c89a3 pin. - Any protocore release older or newer than v0.4.0-testnet as the currently registered public fleet release. - Cosmos SDK or EVM-compatible execution as the current architecture. - An encrypted or private mempool lane. - A live in-tree bridge or Foundation-operated production bridge route. - Shipped agent commerce, escrow, spending policy, hot-wallet autosigning, or economic runbooks. - A released SLH-DSA account or emergency-backup path. - The archived v5.0 or v5.1 design records as the active runtime release instead of v0.4.0-testnet. - Pre-July-2026 whitepaper body text as current capability documentation.