Tokens and Contracts

Last reviewed: 2026-08-01

Native LITHO

LITHO is the native gas and value-transfer asset of Lithosphere. It is not an ERC-20 or LEP100 contract. Native balances are read with eth_getBalance, and native EVM transfers use a transaction value.

Tokenomics

Per the Whitepaper v2.0, LITHO's fixed 1,000,000,000-token maximum supply is distributed from a preallocated security reserve rather than open-ended minting:

Network rewards draw down this finite reserve. As transaction volume grows, fee revenue is intended to progressively replace emission-based rewards, while protocol-level fee burns reduce circulating supply — the whitepaper describes this as non-inflationary at the supply cap and deflationary as usage increases. Treat the allocation percentages as whitepaper-level design targets rather than a substitute for on-chain, address-level verification of actual distribution.

LEP100 fungible tokens

The reference LEP100 implementation is an EVM fungible token built from OpenZeppelin Contracts 5.x ERC20, ERC20Burnable, and Ownable.

The reference implementation provides standard transfer, transferFrom, approve, allowance, balanceOf, totalSupply, name, symbol, and decimals interfaces. It has no post-construction mint, pause, blacklist, transfer tax, rebase, proxy upgrade, or permit feature.

Every deployed token must still be reviewed independently. The name "LEP100" does not prove that a contract uses the unmodified reference implementation.

Mainnet asset identity must include all three fields:

network = lithosphere-mainnet
evm_chain_id = 9005
contract_address = 0x...

Never identify a token by its symbol alone, and never reuse a Kamet or Makalu contract address as a Lithosphere listing identifier.

The LEP100 standards family

The Whitepaper v2.0 defines LEP100 as a broader, extensible standards suite, not only the fungible-token interface described above:

Only the fungible-token reference implementation described above is confirmed deployed and documented for Lithosphere today. The remaining LEP100 numbers are protocol-level design specifications from the whitepaper; do not present any of them as a live Lithosphere contract or feature unless it is also listed as available in Feature Availability.

Mainnet token registry status

No public approved Lithosphere LEP100 registry is included in the current release package. Testnet token addresses must not be presented as production Lithosphere assets.

Before publishing a token address, record and verify:

• chain ID and checksummed contract address;
• deployment transaction and block;
• name, symbol, decimals, and total supply;
• verified source, compiler settings, and constructor arguments;
• runtime bytecode and source hashes;
• ownership and administrative controls; and
• issuer-approved metadata and logo.

Protocol contracts

Production protocol-contract addresses must be published as a versioned registry that includes chain ID, deployment block, transaction hash, source commit, bytecode hash, owner/admin controls, and status.

MultX Bridge and Swap are currently disabled on Lithosphere. Kamet DEX, DNNS, and MultX testnet addresses must not be listed as Lithosphere protocol contracts.

Stock tokens

There is no approved production Stock Token product or Lithosphere contract registry in the current technical package. LEP100 is a token standard; it does not by itself establish that a token represents regulated equity, a security, or another real-world asset.

A Stock Tokens page requires client/legal approval of the product description, issuer, jurisdiction, eligibility restrictions, custody/redemption model, contract addresses, disclosures, and API behavior before publication.