Mainnet is not a switch that turns on a finished product. It’s the point where components that have been tested in controlled conditions start operating under real, adversarial, economically-consequential ones for the first time. Here is what changes, component by component.
“Mainnet launch” gets used as a single event, but it isn’t one. It’s the simultaneous transition of several distinct systems from pre-production to production, each carrying its own risk profile and its own definition of what “live” actually means. Understanding what goes live on October 13 requires looking at each piece separately, because they don’t all change in the same way.
Execution: Lithic and LithoVM
Lithic, the AI-native execution environment, and LithoVM, the layer that runs it under deterministic conditions, move from processing test transactions with no real economic weight to processing transactions where outcomes are final and value is real. The code doesn’t change at the moment of launch — the consequences of what it does change completely. An execution bug that produced an incorrect but harmless result on testnet produces an incorrect and costly result on mainnet. This is why canonical serialization and deterministic verification were built as core invariants rather than optimizations: they are the properties that have to hold under real conditions, not just controlled ones.
EVM compatibility goes live at the same time, under the same consensus guarantees. A Solidity developer deploying a contract on mainnet is relying on the same canonical serialization and deterministic execution that LithoVM provides natively — the two execution paths are not on different footing.
Identity and discovery: PPAL and DNNS
PPAL identity and DNNS routing move from a controlled set of test identities and known services to an open environment where any agent or application can establish identity and any service can register itself for discovery. This is the point where PPAL’s privacy-preserving verification and DNNS’s native resolution actually get tested against real variety — identities and services nobody specifically anticipated when the systems were designed.
Settlement: MultX
MultX’s cross-chain coordination moves from test-value transfers to transfers carrying real assets. The canonical message identity and atomic consumption mechanisms that prevent replay — source network, destination network, originating transaction, asset, amount, recipient, nonce, all authenticated together — are the same before and after mainnet. What changes is that a failure in this layer after launch has financial consequences a testnet failure never did.
Validators: a deliberately recruited genesis set, not an open free-for-all
Of everything transitioning on October 13, the validator set is the one Lithosphere has been most deliberate about shaping in advance, and it’s worth explaining why in more detail than the other components. Rather than opening validation to anyone willing to stake, Lithosphere ran a limited Genesis Validator Program — Cohort 01 — specifically recruiting professional infrastructure companies with existing operating experience on established networks: Cosmos Hub, Celestia, Osmosis, Injective, Sei, Noble, dYdX, Axelar, and Babylon within the Cosmos ecosystem, alongside operators from Solana, Avalanche, NEAR, Polygon, BNB Chain, Sui, Aptos, Ethereum, and Polkadot.
The logic behind that recruitment focus is explicit in how the program frames itself: proven operators, strong foundations, adding LITHO at genesis rather than starting from zero. A network’s validator set is the thing most directly responsible for consensus integrity, and Lithosphere chose to enter mainnet with operators who already know how to run that kind of infrastructure under real conditions, rather than treating genesis as a training ground for first-time validators.
The program’s structure reflects that same intent. Minimum self-stake is 10,000 LITHO, with a recommended range of 10,000 to 25,000 LITHO — a real capital commitment from each participating operator, not a token gesture. Foundation delegation then supplements that self-stake to boost effective voting power; in the program’s own illustrative example, a 15,000 LITHO validator self-stake combined with 100,000 LITHO in Foundation delegation produces an effective stake of 115,000 LITHO. That delegation is conditional and revocable, tied to uptime, successful upgrade participation, and operational performance — meaning the Foundation’s support is earned and maintained through actual network behavior, not granted unconditionally at genesis and left alone.
Genesis validators also receive a defined set of benefits beyond the delegation itself: an on-chain NFT or badge credential marking Genesis Validator designation, early access to network releases, upgrades, and governance participation from the start rather than after the fact, public listing on the Lithosphere Explorer, dedicated technical support and private validator channels, and consideration for ecosystem grants and future delegation. Onboarding runs through a single canonical destination, validators.litho.ai, rather than being scattered across informal channels — consistent with the broader pattern across Lithosphere’s launch infrastructure of giving each function one clear point of entry instead of several competing ones.
This program did not start from a blank slate on October 13 either. Validator infrastructure was already operating publicly during the Makalu testnet period, with its own validator explorer and public onboarding documentation available before mainnet existed. The transition on launch day is from a tested, documented validator process on Makalu to the same operators — plus additional Cohort 01 recruits — now securing real consensus with real economic stakes attached.
Access layer: Thanos Wallet and Ignite
Thanos Wallet and Ignite move from supporting test interactions to being the actual entry point real users and agents use to hold assets, authorize activity, and trade. This is the layer most people will interact with directly, and it’s where the rest of the stack’s guarantees — deterministic execution, persistent identity, native settlement — become something a user experiences rather than something that exists in documentation.
Developer infrastructure
Developer tooling and documentation shift from supporting testnet deployment, where a mistake costs nothing but time, to supporting mainnet deployment, where a contract deployed incorrectly may be deploying against real value from the first transaction. This is the point where developer infrastructure either does or doesn’t hold up to being used in earnest, by people who weren’t part of building it.
None of these components are new on October 13 — they were built, tested, and in several cases, hardened specifically through the Makalu testnet period before this date. What’s new is that they’re no longer operating under conditions anyone controlled in advance. Mainnet is the first time the entire stack, including the validator set securing it, has to hold up against whatever actually shows up, rather than what it was tested against.
Source: https://lithosphere.network/what-actually-goes-live-when-lithosphere-mainnet-launches/
