LithosDocs
ProtocolPayoutsTokenStatsDocs
Start mining
Documentation home
Protocol
  • Lithos Protocol
  • LFSM
    • Rollups
    • NISPs
    • Emissions
    • Mining on Lithos
    • Candidate building
    • Ergo Voting
  • LithosDex
    • Trading with orders
    • Providing liquidity
Run Lithos
  • Startup guide
    • Setting up an Ergo testnet node
  • Configuration
    • Node connection and security
    • Stratum and difficulty
    • Block packages
    • Batching and orders
    • Collateral and emission
    • Wallet and consolidation
    • Statistics and web panels
    • Synchronization and storage
    • Tasks and dispatchers
    • Failure modes
    • Reporting issues
Client API
  • Overview
    • getLithos client information
    • getList UTXO ids for blocks
    • getUTXO ids by block height
    • getBlock info by UTXO id
    • postBlock info for multiple UTXO ids
    • getGet a block's miner set
    • getList all pool blocks
    • getGet Lithos payouts
    • getStatistics overview
    • getMining and payment totals
    • getMining statistics by hour or day
    • getEstimate Lithos hashrate
    • getNetwork difficulty by epoch
    • getThis client's own hashrate
    • getThis client's hashrate over time
    • getThis client's payouts and claims
    • getCollateral inventory
    • getLocal mining activity
    • getCollateral market snapshot
    • getList queue boxes
    • getList the active set
    • getPermit price history
    • getYour locked block rewards
    • postClaim unlocked block rewards
    • postQuote joining the queue
    • postJoin the collateral queue
    • getLithosDex pool state
    • getLithosDex fee vault state
    • getList your outstanding orders
    • postQuote a swap order
    • postPlace a swap order
    • postQuote a deposit order
    • postPlace a deposit order
    • postQuote a redeem order
    • postPlace a redeem order
    • postCancel an order
    • postQuote a swap
    • postQuote a swap by desired output
    • postExecute a swap
    • postQuote a liquidity deposit
    • postDeposit liquidity
    • postQuote a liquidity redemption
    • postRedeem liquidity
    • getList liquidity provisions
    • postClaim settled fees for a provision
    • postQuote a provision resize
    • postResize a provision
    • postCheck a pending fee flush
    • postFlush pending fees to the vault
    • getPool-wide fee history
    • getPool price history
    • getRecent pool activity
    • getFee history for one provision
    • getWallet balances and lending status
    • getGet Stratum information
    • getGet candidate settings
    • getGet difficulty commitment
    • postCommit a difficulty
    • getGet best NISP at height
Lithos

A decentralized mining pool protocol on Ergo. Miners build their own blocks; contracts pay them for proven work.

Live on Ergo mainnet
Protocol
  • How Lithos works
  • Mining on Lithos
  • NISPs
  • Emissions
  • LFSM contracts
Run Lithos
  • Startup guide
  • Configuration
  • LithosDex
  • Client API
  • Failure modes
Network
  • Live stats
  • Public stats API
  • Ergo Platform↗
  • SOAT Miner↗
Community
  • Telegram↗
  • X / Twitter↗
  • GitHub↗
Lithos
© 2026 Lithos Protocol. Open source under the MIT licence.λίθος — stone
Docs/Protocol

Lithos Protocol

What Lithos is, how a Lithos payout works, and where to start.

Standard7 min readFor anyone considering mining on Lithos. No Ergo or smart contract experience needed.

Lithos is a decentralized mining pool for the Ergo↗ blockchain. Miners combine their hashrate and are paid in proportion to the work they prove they did, which is what any pool offers. What differs is that Lithos has no operator. The payout rules are smart contracts on Ergo, every miner produces their own blocks, and no one ever custodies your rewards.

This page explains what Lithos does and how a payout reaches you. For installation, read the startup guide.

Info
Lithos currently runs on the Ergo testnet

Token IDs, contract addresses and economic parameters are not final and will change before mainnet. Values on this page are current testnet values unless marked otherwise.

How Lithos differs from a traditional pool#

The following table compares a Lithos pool against a conventional Ergo pool:

Traditional poolLithos
Who holds your rewards before payoutThe operator's walletNo one. A contract holds them
Who decides what you are paidThe operator's softwareA contract, from proofs you submit
Who builds the blocksThe operator's nodeYour node, from your own mempool
What you trustThat the operator pays honestly and stays onlineNothing. The rules are on-chain
FeeWhatever the operator setsA maximum of 3% of the block subsidy. You receive Lithos tokens, MEV, storage rent, and more in return.
If the pool disappearsYour unpaid balance goes with itNothing to disappear. Payouts are contract-driven

Two of those rows matter more than the rest.

No custody. Value destined for miners sits in a contract from the moment a block is found. There is no operator balance, no minimum payout threshold and no withdrawal step.

You build your own blocks. Every Lithos miner runs their own Ergo node and assembles their own block candidates. Nobody chooses your transactions for you, so the block-production centralization that comes with a large pool does not apply here.

How a payout works#

A Lithos payout runs in five stages. You take part in stage 2 and stage 3; the rest happens without you.

  1. A lender posts collateral. Someone locks 2.915 ERG into a collateral box, which any Lithos miner is allowed to spend when they find a block. Up to 100 of these boxes are live at any time. Lenders are often miners posting their own capital, but they do not have to be.
  2. A miner finds a block. Before the proof-of-work starts, the finder's client inserts a genesis transaction into the block candidate. That transaction spends a collateral box and produces a holding box carrying its value. Inserting it before the proof-of-work is what ties the block to Lithos: changing the transaction afterwards would change the block's hash.
  3. Miners submit proofs. For the next 360 blocks, any miner who worked during the window before that block submits one Non-Interactive Share Proof (NISP) to the holding box. A NISP is one score plus 10 super shares. It is a few kilobytes, and you submit it once, no matter how many shares you actually mined.
  4. Anyone can challenge a proof. For a further 360 blocks, anyone may submit a fraud proof against a NISP that does not hold up. A disproved NISP is removed and earns nothing.
  5. The box pays out. Every surviving miner receives total reward × your score ÷ total score, in both ERG and LIT.

The four stages of a Lithos rollup: a collateral box is spent, then Holding collects NISPs for 360 blocks, then Evaluation accepts fraud proofs for 360 blocks, then Payout pays each miner by score.

Every Lithos block starts one rollup, and every rollup ends in a payout.

Each phase is 360 blocks: about 4.5 hours on testnet at 45-second blocks, and about 12 hours on mainnet at 2-minute blocks.

What you get paid#

You are paid in two currencies:

  • ERG: the pooled block subsidy. Ergo pays a flat 3 ERG per block, of which at least 2.91 ERG is shared among the miners who proved work on that block.
  • LIT: the Lithos protocol token. Each Lithos block emits new LIT, and most of it is paid to miners alongside the ERG.

Your share of both is set by your score, not by how many shares you sent. Score is the difficulty value you commit to on-chain in advance, and it is the single number that decides your payout. The startup guide covers how to choose it.

What the genesis transaction pays out#

Everything a Lithos block distributes happens in one transaction, and you can read it on an explorer. The following is a real testnet genesis transaction. The collateral box goes in, and seven outputs come out:

The genesis transaction from testnet block 505,123. One collateral box holding 2.91515 ERG and 1,710 LIT is spent into seven outputs: the holding box that pays the miners takes 2.9109 ERG and 480 LIT, three founder boxes take 0.001 ERG each with 100, 25 and 15 LIT, the lender's permit return takes 0.001 ERG and 1,070 LIT, the finder takes 0.0001 ERG and 20 LIT, and the proof-of-spend box takes 0.00015 ERG and the collateral token. Of the 1,710 LIT, 640 is newly emitted and 1,070 is the returning permit.

Almost all of the collateral box reaches the miners, and the transaction balances to zero.

Three things to read out of it:

  • The miners' share is output 0. Of the 2.91515 ERG posted, 2.9109 ERG goes to the holding box that later pays miners by score. The rest funds the small boxes the other outputs need.
  • The lender's 1,070 LIT is not a reward. It is their own permit being returned, unchanged, now that the box has been used. Only 640 LIT is newly emitted here, and 480 of that goes to miners.
  • There is no fee output. The transaction is inserted into the block directly, so it pays no transaction fee at all.

Where the 3% goes#

The fee is not an operator's cut, because there is no operator. It is the gap between what the block subsidy is worth and what the lender had to post to claim it.

The lender posts 2.915 ERG on mainnet and receives the block's coinbase, which is the full 3 ERG subsidy plus every transaction fee in the block. Two consequences worth knowing before you compare Lithos against a pool's advertised fee:

  • 3% is a hard ceiling, enforced by contract. The contract refuses any collateral box below the principal floor, so no miner can ever be charged more than 0.09 ERG of a 3 ERG block.
  • Transaction fees in a Lithos block go to the lender, not to the miners. Lithos pools the block subsidy and nothing else. Fee futures markets enable transaction fee revenue to flow back to block miners indirectly through the genesis transaction.

Two ways to take part#

You can mine, lend, or do both.

Mining needs a synced Ergo node, the Lithos client, and mining software that supports Ergo's Autolykos 2 algorithm. You commit to a difficulty, mine, and the client submits your NISPs for you. Start with the startup guide.

Lending means placing collateral into the queue so miners can spend it. A position locks 2.915 ERG plus a permit, which is an amount of LIT held alongside the ERG. Both return to you when a miner spends the box, along with that block's coinbase. Neither can be withdrawn before then. The client's web interface handles this; see the collateral pages there.

Warning
A queued position cannot be cancelled

Once collateral is in the queue, the principal and permit are locked until a block spends the box. There is no withdrawal path, by design.

What you need to run Lithos#

The following are the minimum requirements for mining on the Lithos testnet:

RequirementMinimum
JavaJava 11
Ergo nodeVersion 6.0.4 or later, running on testnet, indexed and fully synced
Mining softwareAny Autolykos 2 miner. SOAT Miner↗ is open source, has no dev fee, and supports Lithos directly
GPU memoryAbout 2 GiB of free VRAM on testnet, growing with the chain height

The startup guide walks through each of these.

The client's API and web interface#

The Lithos client serves a local HTTP API and a web interface on http://localhost:9000. The interface shows your mined blocks, payments, stratum state, collateral positions and the LithosDex.

The same API is documented, and callable, from these docs. See Lithos API to read the endpoints and send test requests to your own client.

Danger
Do not expose the client's API

The Lithos client holds your node's API key and wallet password and can sign transactions. Keep port 9000 inside your local network.

Next steps#

  • Startup guide: install and run the client, from nothing to mining.
  • Mining on Lithos: how work is proven and scored.
  • LithosDex: trading ERG and LIT, and providing liquidity, from the client.
  • LFSM: the contract set that runs the protocol, for readers comfortable with smart contracts.
Edit this page on GitHubsynced from e0ca86a
Next →LFSM
On this page
  • How Lithos differs from a traditional pool
  • How a payout works
  • What you get paid
  • What the genesis transaction pays out
  • Where the 3% goes
  • Two ways to take part
  • What you need to run Lithos
  • The client's API and web interface
  • Next steps