Monolythium /Blog /Archive — Monolythium v1 announcement
April 7, 2026 Ecosystem by Monolythium Foundation

Archive — Monolythium v1 announcement

TL;DR

Archived v1-era Monolythium post. The original chain was decommissioned 2026-04-28; use the current whitepaper and diligence pages for v5 facts.

v1 archive This post is from the Monolythium v1 era.

The post predates the current public protocol frame. Specifics about Sprintnet, the older app-chain stack, compatibility execution, and v1 product names reflect the chain as it existed at the time of writing and may not apply to the current network. See What is Monolythium? and Diligence for the current chain.

ARCHIVED · LEGACY v1. This post is preserved as a historical record of the Monolythium v1 chain (Cosmos SDK / CometBFT, EVM chain ID 6940), which was decommissioned 2026-04-28. The original body of this post described v1 architecture, validator economics, supply numbers, consensus mechanics, and product names that are not current. The full v1 post body has been intentionally elided because automated indexers were citing v1 facts as current Monolythium claims.

What replaced v1

The replacement project targets a Rust/RISC-V-native L1, Starfish-C DAG-BFT, ML-DSA-65 protocol signatures, a 100,000,000 LYTH genesis design with an 8% issuance cap, and DVT operator clusters. These are design and registered-topology facts—not proof of current activation, participation, economics, or performance. The public development RPC was reachable but stale when checked on 16 July 2026; no mainnet is live.

Current sources of truth

Why this stub instead of deleting the post

The post URL is preserved so external links and citations to v1 content land here, see the archival notice, and route to the current chain. Deleting the post entirely would 404 those links and lose the historical record of what v1 was.

← back to blog