# Monolythium Canonical Public Context

Last updated: 2026-07-16
Website: https://monolythium.com/
Docs: https://docs.monolythium.com/

## Status

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 and rewards: 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/
- Post-quantum cryptography posture: https://docs.monolythium.com/learn/post-quantum-cryptography/
- JSON facts: https://monolythium.com/facts.json

## Network

- Registered development chain id: 69420
- Mainnet chain id: 69422
- Target round time in the registered development profile: 4 seconds; current RPC is stale and does not demonstrate cadence
- Observed status: Degraded/stale as observed 2026-07-16: RPC reachable at height 74,907; latest timestamp 2026-07-08T22:39:05Z; no advancement during repeated checks.
- Finality: Target design: Starfish-C DAG-BFT with per-operator ML-DSA-65 (FIPS-204) round signatures and a 7-of-10 bitmap certificate over independent operator keys. The stale public head does not demonstrate cadence, finality, or active quorum.
- 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.
- Interop: No in-tree bridge is active. Any cross-chain route requires a separately released external-provider or issuer integration with its trust model shown to the user.
- Governance: No on-chain governance voting or governance-adjustable inflation path.

## Token

- Symbol: LYTH
- Target initial-supply design (verify against finalized genesis state): 100,000,000 LYTH
- Decimals: 18
- Atomic unit: lythoshi, 1e-18 LYTH
- Target annual issuance-cap design: 8% design ceiling
- Target base-fee burn design: 100% design rule

## Consensus

- Name: Starfish-C
- Public reference: Polyanskii, Muller, and Vorobyev 2025 Starfish paper
- Reference URL: 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.
- Native account signing: Protocol profile: ML-DSA-65 (FIPS-204) for native transaction admission; verify activation and network health separately.
- Consensus signing: Target certificate profile: ML-DSA-65 (FIPS-204) per-operator round signatures and a 7-of-10 bitmap over independent operator keys — no shared signing key, aggregate signature, or key ceremony. The current stale RPC is not quorum or finality evidence.
- Address derivation: BLAKE3(canonical_pubkey_bytes)[..20], rendered with typed bech32m HRPs.
- Residual classical assumptions:
  - The peer-to-peer transport still carries libp2p node-identity dependencies outside the consensus/state-signing path.
  - Application-layer proof verification remains disabled; the removed bridge and confidential-value constructions cannot be re-armed as current capabilities.

## Source And Audit Posture

- Public repositories: Docs, website, SDK, MCP, and ecosystem repositories are published through the monolythium GitHub organization as they become canonical.
- Core repository: mono-core is not fully public open source today. Core source access, external audits, benchmark harnesses, and adversarial simulations remain diligence gates.

## Wallet And Stele Boundaries

- Browser wallet: 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.
- Desktop wallet: Stele's product boundary is the standalone web application. Desktop embedding is being retired; an older or unreconciled desktop build may still show a disabled legacy Stele surface until that removal ships. Verify each client's release notes and never treat a desktop surface as hosted Stele availability.
- Stele product: 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 MCP tool names (exactly two): stele_search_services, stele_create_booking_draft
- Hosted 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 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.
- Gated capabilities: Standalone app publication, listing writes, settlement, escrow, disputes, reviews, E2EE collaboration, and mainnet execution remain gated until independently verified release evidence exists.

## Deprecated Or Stale Claims

The following claims are stale and should not be used as current Monolythium facts:
- 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.