Solid ground for building on Lithosphere
Lithosphere's mainnet works, but it launched without the basics developers expect on an EVM chain. There's no multisig and no wrapped LITHO, and the contracts that wallets and app libraries look for aren't there. Outcrop puts them in place for everyone.
See what's missingCross-section of the plan. Each layer is a phase, oldest at the bottom. Lithosphere mainnet is at block reading….
What's missing, checked live
This page asks Lithosphere mainnet directly every time it loads, so nothing below is a screenshot. When Outcrop ships, these rows change on their own.
| What | Why it matters | Where tools expect it | On mainnet now | |
|---|---|---|---|---|
| Safe multisig | Checking… | Shared wallets where funds move only when enough people sign | 0x29fc…C762 | Checking… |
| Wrapped LITHO | Checking… | LITHO as a standard token that apps and DEXes can hold | No address yet | Checking… |
| Multicall3 | Checking… | Batches reads. viem and wagmi look for it at this address | 0xcA11…CA11 | Checking… |
| Permit2 | Checking… | One-signature approvals for swaps and payments | 0x0000…8BA3 | Checking… |
| CREATE2 deployer | Checking… | Same contract, same address on every chain | 0x4e59…956C | Checking… |
| EVM version | Checking… | Default Solidity settings target Cancun and fail to deploy here | Chain setting | Checking… |
Asking Lithosphere mainnet…
The plan, layer by layer
Read it like rock: the oldest layer is at the bottom, and it gets built first. Each layer above it is planned once the one below has shipped.
Agent payments
LaterIdentity, spending limits and pay-per-call for AI agents, settled in LITHO. Open contracts that anyone can build on.
Sentinel
LaterAutomatic safety checks on every new token and contract on Lithosphere, written up in plain English. Agents can ask it before they trade.
Data and AI access
NextA data API for Lithosphere, plus an MCP server so assistants like Claude and ChatGPT can read the chain and prepare transactions for a person to sign.
Foundations
Building nowThe plumbing every EVM developer assumes is already there. About four weeks, starting on the Makalu testnet, and free for everyone.
- A hosted Safe multisig. Teams, DAOs and the foundation can hold LITHO together, and nothing moves until enough people sign.
- Wrapped LITHO, so DEXes, escrow and payment apps can hold it like any other token.
- Multicall3, Permit2 and a CREATE2 deployer, the contracts that wallets and app libraries expect to find.
- A starter kit: Foundry and Hardhat templates and a short guide that already know Lithosphere's quirks.
- Listings in viem, Safe's registry, the Multicall3 list and a token list, so common tools recognise the chain without extra setup.
Lithosphere mainnet. The chain itself, live since 13 October 2026.
Start on the testnet today
Makalu has the same gaps as mainnet, but test LITHO is free. Here are the details the docs don't keep in one place.
- Network name
- Lithosphere Makalu Testnet
- RPC URL
- https://rpc.litho.ai
- Chain ID
- 700777
- Cosmos chain ID
- lithosphere_700777-2
- Explorer
- makalu.litho.ai
- Faucet
- makalu.litho.ai/faucet1, 2 or 5 test LITHO per wallet, once a day
[profile.default]evm_version = "shanghai" [rpc_endpoints]makalu = "https://rpc.litho.ai"litho = "https://rpc-mainnet.litho.ai"
One setting to know about. Lithosphere runs the Shanghai version of the EVM. Recent Solidity compilers target Cancun by default, and the deploy fails with “invalid opcode”. Set the EVM version once, as above, and you won't hit it again.