A Layer-1 project targeting Rust-to-RISC-V execution, deterministic finality, and ML-DSA-65 protocol signatures. The registered development RPC is reachable but stale; external interop and economic execution remain gated.
Monolythium is being built as a full-stack L1 for agent-native commerce. LythiumDAG-BFT (Starfish-C) targets deterministic finality with a four-second cadence. Execution, MRC assets, and protocol modules must be evaluated capability by capability; the stale development head is not finality evidence.
The protocol design uses ML-DSA-65 (FIPS-204) transaction and operator signatures, with a 7-of-10 bitmap multisig over independent keys. The in-tree bridge, confidential-value construction, emergency-key registry, and activated eight-primitive agent-commerce suite are not current capabilities. Stele targets public web discovery separately from those protocol goals, and app publication remains gated.
RPC values are labeled as reported snapshots. The latest known head is stale and does not demonstrate cadence, finality, or economic state.
Reproducible probes, architecture rationale, license posture, and public repositories. Current probes must surface degraded state instead of converting reachability into a pass.
The intended sovereign stack; each layer still requires release and activation evidence.
The launch model targets Rust-first contracts compiled to deterministic RISC-V artifacts, with MRC assets and agent-commerce capabilities released and activated individually.
target · native pathThe design moves common hot paths into separately reviewed and activated modules. Token, market, policy, privacy, and external-provider interop capabilities are not implied by this diagram.
target · MRC standardsStarfish-C is the intended uncertified-DAG consensus with linear payload growth, ML-DSA-65 round signatures, and deterministic finality. The stale public head is not performance evidence.
target · Starfish-CThe network design uses libp2p gossip. Any bridge or external-liquidity route requires a separately released provider or issuer integration; no in-tree bridge is claimed.
target · sovereign P2PThese are intended protocol properties, not claims about the currently stale development network.
The protocol targets round commitment after a 7-of-10 certificate using independent ML-DSA-65 signatures. Current public RPC staleness means cadence and finality remain unverified.
Starfish-C targets O(Mn) payload growth with erasure coding. The application layer targets cycle-metered Rust/RISC-V execution and separately priced state I/O.
The registered topology uses 10-member DVT clusters and a 7-of-10 certificate threshold. Open-seat admission, participation, and liquid-bonding behavior each require current activation evidence.
Mono is not EVM-compatible at execution. Any wrapped asset, swap, or bridge route must be separately released by a provider or issuer with explicit verification and risk controls.
The design specifies a 100,000,000 LYTH genesis supply, an 8% annual issuance cap, base-fee burning, and treasury funding from the genesis reserve. Final genesis and activated runtime state remain the authority.
The prior confidential-value construction was removed. Any future private denomination needs a new post-quantum design, conservation evidence, independent review, and explicit activation.
Attestation, consent, discovery, availability, escrow, arbiter, spending-policy, and reputation capabilities are tracked separately. Stele targets non-economic web discovery and draft workflows; application publication and the native suite remain gated.
Chain id 69420 identifies the v0.4.0 development network, but repeated checks on 16 July 2026 stayed at height 74,907 with latest timestamp 8 July. A reachable endpoint is not proof of advancement or finality.
The next network gate is an advancing head, consistent peer health, reproducible cadence checks, and current public status. Cluster-marketplace and economic claims remain design targets until activated.
Monolythium targets Rust/RISC-V contracts, MRC assets, and activated native modules. Solidity/EVM bytecode is not the launch target; any external liquidity route requires a separately released provider or issuer integration.
The 100-cluster marketplace is a target. The registered development topology is four 10-member clusters with 7-of-10 certificates; current RPC staleness means this page does not claim they are all participating. Open-seat admission needs separate activation evidence.
The public code and registered development identity are inspectable, but the RPC is currently stale. Read the status evidence, use local tooling, and do not treat development data as economic settlement.