Lithosphere is moving into an important new phase.
The recent launch of Thanos.fi, the continued evolution of the Makalu testnet, preparations for the upcoming LITHO Token Generation Event (TGE), and a new wave of Layer 1 security work are bringing together several pieces of the ecosystem we have been building toward.
Our objective remains ambitious:
Deliver an AI-native Layer 1 combining LithoVM, Lithic, EVM compatibility, multi-VM execution, agentic infrastructure, LEP100 AI provenance, high-throughput architecture and post-quantum crypto agility.
But achieving that vision requires more than performance.
It requires security at every layer.
The Industry Is Giving L1s New Security Lessons
Recent blockchain incidents have reinforced an important reality: Layer 1 infrastructure remains an active security frontier.
Modern chains are complex systems involving consensus, virtual machines, networking, cross-chain messaging, cryptographic libraries, validators, bridges, parsers and continuous software upgrades.
A weakness in any one of these areas can have network-wide consequences.
Recent incidents across the industry have demonstrated several particularly important classes of failure:
• cross-domain messages or receipts being incorrectly authenticated or reused;
• different components interpreting the same data differently;
• software upgrades introducing consensus-critical edge cases;
• validator restart behavior exposing previously hidden state problems; • bridge and cross-layer assumptions becoming asset-creation vulnerabilities;
• network bugs escalating into chain halts.
For Lithosphere, these incidents are not simply news events.
They are engineering lessons.
We are using them to strengthen the assumptions underlying Lithosphere before substantially more economic activity moves onchain.
Security Before Scale
High throughput matters.
Fast finality matters.
Low transaction costs matter.
But none of those characteristics compensate for incorrect state.
Lithosphere’s security work is therefore increasingly centered around several fundamental invariants:
One authenticated message should have one canonical meaning.
One valid cross-domain event should execute at most once.
Every asset mint or credit should have an authenticated corresponding source event.
Every validator should derive the same result from the same state and transaction data.
Ambiguous or malformed inputs should fail closed.
Protocol upgrades should preserve deterministic execution across validators.
These principles are being applied across Lithosphere, LithoVM, cross-chain infrastructure and the broader developer stack.
Strengthening LithoVM
LithoVM sits at the heart of the Lithosphere execution architecture.
That makes deterministic behavior one of its most important properties.
We are strengthening the execution environment around stricter canonical serialization, deterministic cryptographic verification, explicit algorithm versioning, replay protection and improved validation of consensus-critical inputs.
The objective is simple:
The same byte sequence must have the same interpretation everywhere on the network.
Validators should never disagree because two implementations parsed an object differently.
Cross-VM infrastructure should never interpret the same authenticated message in two different ways.
And cryptographic verification should never silently change because a dependency or library changed underneath the protocol.
This becomes even more important as Lithosphere expands its multi-VM architecture.
Lithic: Security at the Programming-Language Layer
Lithic gives us another opportunity to move security closer to developers.
Instead of requiring every developer to correctly implement complex authorization and cryptographic logic manually, Lithic can provide higher-level security primitives that compile into deterministic LithoVM execution.
Our direction for Lithic includes support for stronger authorization policies, cryptographic typing, agent permissions and eventually first-class post-quantum security primitives.
Developers should ultimately be able to define policies such as:
without recreating the underlying cryptographic machinery for every application.
The long-term relationship is straightforward:
Lithic expresses policy.
LithoVM executes policy.
Lithosphere consensus enforces policy.
Preparing Lithosphere for the Post-Quantum Era
We are also expanding the Lithosphere security roadmap beyond the threats facing blockchains today.
Modern blockchain authentication relies heavily on elliptic-curve cryptography.
A sufficiently capable future quantum computer could threaten many of these public-key systems.
Waiting until such machines exist before beginning migration would be the wrong strategy.
Lithosphere is therefore being designed around post-quantum crypto agility.
The objective is not to claim that any blockchain can be permanently “quantum proof.”
The objective is to ensure that Lithosphere can evolve its cryptographic foundations without redesigning the network.
The Proposed PQ Architecture
Our current architecture is centered around standardized post-quantum primitives including:
ML-DSA — intended for post-quantum digital signatures.
SLH-DSA — a hash-based signature system that can provide an independent security and recovery mechanism.
ML-KEM — intended for post-quantum key establishment and future protection of network communications.
Rather than immediately abandoning existing cryptography, Lithosphere can transition through hybrid authentication.
An attacker would therefore need to defeat both cryptographic systems where the policy requires both.
Crypto Agility Is the Bigger Goal
The most important part of the architecture may not be ML-DSA itself.
It is the ability to replace ML-DSA someday.
Lithosphere is being designed around a protocol-level cryptographic registry capable of identifying and versioning supported algorithms.
Conceptually:
Algorithms can progress through states such as:
That gives Lithosphere an important capability:
Cryptographic algorithms can evolve while accounts, applications and the broader execution architecture remain intact.
If a weakness is discovered years from now, the network should have a migration mechanism rather than requiring an architectural reset.
Post-Quantum LithoVM
Post-quantum verification should also become a native LithoVM capability.
Instead of executing complex PQ cryptography as ordinary smart-contract bytecode, LithoVM can provide deterministic native verification primitives.
The architecture can support operations equivalent to:
These operations can be consensus-versioned, benchmarked and assigned predictable gas costs.
The same infrastructure can eventually be exposed to EVM applications through precompiles, allowing Solidity developers to build quantum-resistant smart accounts, multisigs, treasuries, bridges and DAOs while retaining Ethereum compatibility.
Post-Quantum Lithic
Lithic can take this further.
Post-quantum cryptography can become a native language concept rather than an opaque byte array.
Developers could eventually work with typed objects conceptually similar to:
Lithic could then prevent incompatible algorithms from being mixed at compile time.
Future security profiles could also allow developers to explicitly define contracts as:
A post-quantum contract could reject classical-only ownership or authorization during compilation.
That is significantly different from simply adding a PQ library.
It brings quantum-resistant security into the developer experience itself.
Validators Come First
Not every part of Lithosphere needs to migrate simultaneously.
Our priority is protecting the infrastructure where compromised cryptographic keys could have the greatest systemic consequences.
Validators are therefore a major focus.
The proposed validator architecture separates responsibilities between:
• operational consensus keys;
• post-quantum validator identity;
• network communication keys;
• governance credentials;
• independent recovery credentials.
PQ authentication can initially protect highly sensitive operations such as validator key rotation and identity changes before deeper consensus integration is activated.
This staged approach lets us measure performance without introducing unnecessary risk.
Protecting Bridges and Cross-Chain Infrastructure
Cross-chain systems deserve equally aggressive protection.
A future Lithosphere bridge should not rely on one reusable administrative key being the sole barrier between an attacker and unlimited asset creation.
Our direction combines:
source-state authentication + replay protection + canonical message identity + threshold authorization + post-quantum authentication.
A cross-chain message should incorporate its source network, destination network, originating transaction, event index, asset, amount, recipient and nonce into an authenticated identity.
Once executed:
It cannot execute again.
The consume operation and resulting state transition must be atomic.
These safeguards address not only future quantum threats but several classes of bridge attacks already occurring today.
Safer Network Upgrades
Another major focus is upgrade safety.
Blockchain software evolves continuously, but a validator network cannot afford inconsistent interpretation during an upgrade.
Our security process for Lithosphere is being expanded around:
• deterministic activation heights;
• reproducible builds;
• consensus test vectors;
• cross-platform validator testing;
• differential execution testing;
• validator restart simulations;
• malformed-input fuzzing;
• partial-upgrade scenarios;
• adversarial testnet testing;
• cryptographic version pinning;
• rollback and emergency procedures.
Makalu is critical here.
New consensus-sensitive capabilities should be attacked aggressively on testnet before they protect meaningful economic value.
Thanos.fi: The User Layer of the Ecosystem
The launch of Thanos.fi represents another major piece of this architecture coming online.
Thanos is being built as the wallet and access layer connecting users, applications and eventually autonomous agents with the Lithosphere ecosystem.
Self-custody remains fundamental.
But wallets are evolving.
The next generation of wallets will increasingly need to manage more than keys and balances.
They will manage permissions.
Agents.
Session credentials.
Spending policies.
Cross-chain activity.
Application authorization.
And eventually multiple cryptographic authentication mechanisms.
Thanos provides an opportunity to make these capabilities accessible without exposing users to the complexity underneath them.
Over time, we envision Thanos supporting the transition from:
Agentic Infrastructure Requires Different Security
Lithosphere is being built for an environment where blockchain participants will increasingly include machines.
Autonomous agents may execute transactions continuously, interact with applications, rebalance assets, purchase services, coordinate with other agents and operate across multiple networks.
Giving an autonomous system unrestricted access to a master private key is not an acceptable architecture.
Lithosphere’s agentic infrastructure is therefore moving toward programmable authorization.
An agent credential should be capable of carrying restrictions such as:
This makes security policy part of the execution environment rather than merely an application convention.
LEP100 and Verifiable AI
AI-native infrastructure also requires stronger provenance.
As AI systems increasingly initiate economically meaningful activity, networks need mechanisms for establishing:
• which model performed an operation;
• which provider executed it;
• what execution was authorized;
• what output was produced;
• what resources were consumed;
• what cryptographic identity attested to the event.
LEP100 is an important component of this architecture.
Post-quantum signatures can eventually extend this further by protecting long-lived AI provenance records against future cryptographic threats.
The result is infrastructure where AI activity can become not only executable but increasingly attributable, auditable and verifiable.
High Throughput Without Sacrificing Determinism
Lithosphere continues to pursue high-throughput blockchain infrastructure.
But PQ cryptography introduces new performance challenges.
Post-quantum signatures and public keys are generally much larger than traditional elliptic-curve equivalents.
That means PQ migration must account for:
• block size;
• validator bandwidth;
• transaction size;
• signature verification CPU;
• memory;
• mempool performance;
• block propagation; • mobile signing;
• state growth.
LithoVM can mitigate part of this through native verification and parallel processing.
PQ signatures can be validated across worker pools while preserving deterministic results before execution.
The goal is not simply:
Add PQ cryptography.
It is:
Add PQ cryptography without compromising the performance characteristics expected from Lithosphere.
The LITHO TGE Is Approaching
All of this work is taking place as another major milestone approaches:
The LITHO Token Generation Event.
The TGE represents the beginning of a new economic phase for the network.
LITHO is designed to sit at the center of the Lithosphere economy, supporting network activity including gas, staking, validators, governance and ecosystem incentives.
But the token is only one component.
The larger objective is the infrastructure surrounding it.
We are building toward an integrated stack:
AI-Native Layer 1
Infrastructure designed for human and autonomous participants.
LithoVM
Deterministic high-performance execution.
Lithic
An AI-native smart contract language compiling directly into LithoVM.
EVM Compatibility
Access to Ethereum’s developer ecosystem and application tooling.
Multi-VM Execution
An architecture capable of supporting multiple execution environments.
Agentic Infrastructure
Programmable permissions and infrastructure for autonomous systems.
LEP100 AI Provenance
Standards for AI execution, providers, accounting and verifiable provenance.
High Throughput
Infrastructure designed for high-volume applications and machine-driven activity.
Post-Quantum Crypto Agility
A cryptographic architecture capable of evolving beyond today’s public-key assumptions.
Building for What Comes Next
The blockchain industry has spent years competing over speed.
The next phase will require much more.
Networks will need to support AI systems operating autonomously.
They will need safer cross-chain infrastructure.
They will need stronger authorization models.
They will need deterministic execution across increasingly complicated architectures.
And they will eventually need to migrate beyond cryptography that was never designed for the quantum era.
Lithosphere is being built around that future.
We will continue learning from security failures across the broader blockchain industry and incorporating those lessons into the network before they become Lithosphere problems.
We will continue using Makalu to test assumptions aggressively.
We will continue expanding LithoVM and Lithic.
We will continue building Thanos as the user and agent access layer.
And we will continue preparing for the upcoming LITHO TGE.
Our commitment is clear:
Deliver an AI-native L1 + LithoVM + Lithic + EVM compatibility + multi-VM execution + agentic infrastructure + LEP100 AI provenance + high throughput + post-quantum crypto agility.
Thanos is live.
Makalu is evolving.
LITHO TGE is approaching.
Lithosphere is being built for what comes next.
