DOCSEARCHbyAlgolia
Submit Docs

Monolythium Canonical Public Context

website·Indexed 32 days ago

https://docs.monolythium.com/

Documentation covering the Monolythium Canonical Public Context, including status and Registered Public-Testnet Identity.

Tokens
724
Snippets
2
Records
6
Agent score
0%

What's inside Monolythium

  1. Identify Deprecated Monolythium Claims

    The following claims are officially deprecated or stale and should not be used for current development:

    • Any architecture claiming Cosmos SDK or EVM compatibility.
    • Any claim of a live in-tree bridge or Foundation-operated production bridge.
    • Claims of an encrypted or private mempool.
    • Any protocore release other than v0.4.0-testnet for the public fleet.
    • Any agent commerce features (escrow, spending policies, hot-wallet autosigning).
    • Use of SLH-DSA accounts or emergency-backup paths.

  2. Understand Monolythium Network Architecture

    Monolythium uses a non-EVM compatible execution environment and a specific consensus mechanism:

    • Execution: Rust/RISC-V-native execution.
    • Consensus: Starfish-C DAG-BFT. The testnet profile uses four 10-operator clusters, requiring 7-of-10 ML-DSA-65 operator signatures for a cluster round certificate.
    • Timing: 4-second rounds and 18-second epochs.
    • Governance: No on-chain governance voting or adjustable inflation paths.

  3. Use Stele and the lyth_mcp Tool

    Stele is a public-web preview available at https://stele.monolythium.com/.

    Studio Features: Users can authenticate via Browser Wallet at https://stele.monolythium.com/studio to create, edit, preview, and delete private provider-listing drafts. These drafts are unpublished and non-transactable.

    MCP Integration:

    • A hosted OAuth MCP is available for Codex and Claude Code.
    • The stele_create_provider_listing_draft tool can be called if it appears in the authenticated tools/list response.
    • This operation is idempotent; replaying the call returns the same draft.
    • The local MCP is available as the lyth_mcp v0.1.0 GitHub prerelease.

  5. Monolythium Cryptographic Specifications

    Monolythium implements post-quantum cryptography for its core operations:

    • Account & Consensus Signing: Uses ML-DSA-65 for native transaction admission and operator signatures.
    • Transport: Uses ML-KEM-768 Noise transport.
    • Address Derivation: Domain-separated BLAKE3 over canonical public-key bytes, using typed bech32m HRPs.
    • Mempool: Plaintext; no encrypted or private mempool lanes exist.

  6. Connect to Monolythium Public Testnet

    Monolythium has a registered public development testnet. Note that as of 2026-07-16, the public RPC is reachable but the finalized state is observed as stale/degraded and the network should not be described as live. This is a value-less testnet where the Foundation may wipe and re-genesis without notice.
    {
  "network": "testnet-69420",
  "chainId": 69420,
  "rpc": "https://rpc.monolythium.com",
  "genesisHash": "0xe22733f4d7e013b93f0f825667fcf852cbf7ad1ca31a42a1bfcf1ab6d79c89a3",
  "release": "v0.4.0-testnet",
  "runtimeVersion": "0.4.0"
}