Feature Availability
Explicit supported and TBD feature matrix for Lithosphere publication.
Last reviewed: 2026-08-01
This page prevents planned, testnet, or third-party features from being presented as production Lithosphere capabilities. This includes design and roadmap items described in the Whitepaper v2.0, which documents Lithosphere's broader protocol vision and is not, by itself, evidence of a deployed Lithosphere feature.
| Topic | Current evidence | Public documentation decision |
|---|---|---|
| Mainnet network connection | Live endpoints and accepted explorer cutover | Publish |
| Wallet manual configuration | Standard EVM chain configuration | Publish |
| Native LITHO transfers | Enabled by Lithosphere | Publish with custody warnings |
| LEP100 fungible token standard | Reference implementation documented | Publish standard; do not publish unapproved token addresses |
| LEP100 NFT, royalty, marketplace, and bridge mint/burn standards (LEP100-6 to 13) | Whitepaper v2.0 specification only; no confirmed Lithosphere deployment | Do not claim support |
| LithoVM (native execution environment) | Whitepaper describes design; not documented as independently usable on Lithosphere outside EVM contracts | Do not claim standalone LithoVM contract support |
| AI-native hooks / AI service provider standard (LEP100-2, LEP100-5) | Whitepaper design/roadmap only | Do not claim support |
| Privacy-preserving account linking (LEP100-14, ZK) | Whitepaper design/roadmap only | Do not claim support |
| Mainnet full node | Complete guide; public signed binary URL still pending | Publish requirements with release-artifact warning |
| Exchange integration | Full technical package prepared | Publish as integration guidance, not listing approval |
| Mainnet MultX bridge | Disabled; independent audit/production launch pending | Do not publish a user bridging tutorial yet |
| Stock Tokens | No approved product, legal model, APIs, or Lithosphere registry | Client/product/legal approval required |
| Account abstraction | No verified Lithosphere ERC-4337 entry point, bundler, paymaster, or support policy | Do not claim support |
| Oracles and price feeds | No approved general Lithosphere oracle registry or SLA | Do not claim a production oracle service |
| Data Streams | No approved Lithosphere data-stream product or API | Do not claim support |
| General cross-chain messaging | No approved public Lithosphere arbitrary-message service | Do not claim support |
| Governance | Operator process exists | Publish after current Mainnet parameters and user flow are verified |
| Notices and upgrades | Internal processes exist; canonical public channel TBD | Client must designate official channel |
| Report an issue | No approved public support/security contacts in this content pack | Client must provide contacts |
litho.cool | Meaning and ownership not established in repository evidence | Client must clarify before linking |
Approval information needed
For each currently unsupported feature, obtain the product owner, accountable approver, production network and launch status, official endpoints and contract addresses, security evidence, limitations, SLA, legal wording where relevant, and support/incident/upgrade ownership.