LITHOS Protocol

Lithos Panel is live! Deploy your node, client, and miner all from one panel with direct sync to your API. Makes it super easy to start from scratch. Give it a try and let us know if you come across any issues github.com/Lithos-Protoco…

Lithos Client v4 =====PlasmaDex: - Added PlasmaDex LP contract, a new AMM Liquidity Pool which collects constant fees that are not subject to impermanent loss - Added off-chain code for deposits, swaps, redemptions, fee withdrawals and fee claims - Added corresponding API calls on Lithos Client Docs (localhost:9000/assets) - Added initial ERG / LIT PlasmaDex Liquidity Pool - Added synchronization process for PlasmaDex dictionary - Added historical synchronizer for PlasmaDex dictionary in order to claim fees =====Emissions: - Added emission contract for LIT token - Enabled token distribution for Lithos rollups - Modified self-collateralization to use emission contract to create collateral boxes =====Bug Fixes: - Fixed bug where change values less than 1000000 nERG were not added onto the miner fee - Fixed bug where self-collateralization caused abnormally large amounts of double spend errors - Fixed stratum bug causing job ids to not increment properly

Lithos is a decentralized, on chain mining pool protocol for Proof of Work blockchains. It moves the entire pool operation, share verification and payouts directly onto the blockchain using smart contracts. No trusted operators or off chain middlemen

@Armeanio’s essay perfectly diagnoses the pathology of modern crypto: much of what the industry celebrates as "protocol revenue" is simply digital corporatism, a technocratic rebranding of traditional Payment for Order Flow (PFOF). Lithos is the exact structural antidote required to democratize the PoW base layer. But if we follow this logic to its natural conclusion, we must confront the next frontier of rent extraction: Layer 2 rollups. The broader industry has accepted centralized L2 sequencers as a "necessary evil" for scaling. But this centralization isn't a temporary cultural failing; it is a matter of architectural determinism. The EVM Account Model relies on a global, synchronous state. When thousands of users interact with a smart contract, they are fighting to overwrite the exact same shared ledger. To prevent a chaotic collision of concurrent transactions, the architecture strictly requires a centralized arbiter to act as a traffic cop and organize the queue. By design, that arbiter becomes the ultimate Order Flow King. They are granted total visibility over the mempool and an exclusive monopoly on MEV extraction. This is where Ergo’s architecture moves from a technical nuance to a structural necessity. The eUTXO model fundamentally alters the physics of execution. Because state is local, perfectly partitioned into isolated, independent boxes rather than a shared global whiteboard, transactions are inherently asynchronous. They do not naturally collide. Consequently, an L2 built on Ergo doesn’t strictly need a monopolistic sequencer to dictate order. If an intermediary ever attempts to extract rent, censor a user, or sandwich a trade, the eUTXO architecture natively allows that user to generate their own local state transition, bypass the middleman entirely, and settle permissionlessly on L1. You cannot be a King of Order Flow if your users can mathematically walk around your tollbooth. But here is the critical synthesis that most modular theorists miss: an L2 "escape hatch" is purely theatrical if the underlying Layer 1 is controlled by a builder cartel. A malicious L2 sequencer will simply bribe the L1 cartel to censor your exit. This is why these pieces must exist together. Lithos immunizes the L1 base layer against capture. eUTXO immunizes the L2 execution layer against monopoly. You cannot build a non-extractive L2 on a shared-state EVM, and you cannot enforce a fair L2 on a captured L1. Ergo is quietly assembling the only complete, mathematically rigorous immune system left in the space.

Lithos Updates: - Moved towards a global sync state for the Lithos client. In general it has been easy to make and is significantly more robust than having individual sync processes. - Made initial LP offchain code take advantage of the new sync process - LP AVL tree now holds NFT ids - Small changes to contracts to reflect NFT change

Proof of work is neat as it is permission less to join and mine. There is no internal limit enforced on the optimal amount of block builders in proof of work. But mining pools add a layer of trust and also a point of external attack, which limits this base property. Lithos removes the layer of economic trust from mining pools, without altering the group efficiency pools offer. Plus it distributes the block production capacity back to each miner. That I believe creates the most resilient foundation for distributed block production.

PlasmaDex is an AVL based LP fee management system built for Ergo. It allows miners or lenders to track their positions as unique NFTs that represent dynamic liquidity claims. An NFT is just a unique identifier. Here you can look at is as an account number, representing a position that is collecting fees. The idea is to track, manage and payout fees creating a new form of use driven revenue. It transforms liquidity positions into an unique asset with some form of fee driven revenue that can become fungible on secondary markets. These could then be traded on Ergo or even or fractionalized on NFT marketplaces. It’s kind of reminiscent of how Uniswap V3 uses NFTs for concentrated liquidity positions, but leveraged with Ergo's for more efficient, provable ownership and LP royalties. This is going to be built into the Lithos Client. Decentralized Mining + New Primitives for Defi on Ergo.

Lithos Client v3.1.0-test is live. Added self-collateralization so the client can create a collateral UTXO if none exist. Fixed diff-commitment update + scoring bugs. Tested with Ergo node 6.0.3 candidate. Release notes: github.com/Lithos-Protoco…

This would make Ergo mining dramatically more flexible and developer friendly starting with 6.0.3. Please help with reviewing and testing. It’s a big step for Lithos and mining on the network generally. Now any standard Ergo node can be used as a tool for a mining backend. Mining pool operators can point their pool software at any node and issue per miner requests with the payout public key. Solo miners or small pools can run a lightweight stratum server that talks directly to the node. Developers can build custom mining clients, or test tools more easily. Completely decentralizes the mining stack the node is now just a candidate generator + validator.

As institutions re-enter crypto and PoW gains attention, the focus is on price and scale But infrastructure decides who holds power Lithos builds for miner sovereignty with on-chain coordination, local nodes, fewer control points Growth is good. Decentralization is better ⛏️

Lithos Updates: - Finishing up the work that was started on new LP contracts - Shelved some lower-level efficiency changes for later, am focusing on getting emissions working and ready for mainnet - Getting some smaller fixes in for 3.1 that have been accumulating over time, mostly small bugs related to diff commitments - Some API additions to allow diff commitments via API panel Additionally: - Finished Appkit 6.0, doing testing now then will release

Lithos is about closing the gap between miners and the protocol. Run infrastructure locally. Verify everything on-chain. Coordinate without giving up control. When miners own the full stack, decentralization stops being a slogan and starts being real.

As mining trends toward larger operators and thinner margins, the real question isn’t hashpower, it’s who has control…. Lithos is built around miner-run infrastructure, local nodes, and on-chain coordination. Mining shouldn’t just scale up. It should scale out. #Ergo

Want to join Lithos miners but not sure where to start? Running the Lithos Panel makes it seamless. Deploy your node, Lithos panel and miner all from one panel making it that much easier to qualify for mainnet airdrops. Further details below👇

As for being ready for launch with @LithosProtocol here is the latest. - Next big upgrade will be about emissions and implementing some tokens uses into current Lithos contracts - After that plan on having audit all of the contracts, just to be sure we haven't missed anything - We can do last bits of testing on testnet regarding emissions stuff. Should be relatively simple, but maybe different token usages will need more testing. Still looking at the needs, tradeoffs and discussing incentives. - Started writing a script to collect test net participants addresses, so should be easy to pull out all the miners and reward them correctly. Not really active yet but hallucinating about PlasmaDex also, a new framework for reward handling and distribution based on LP's percentages and fees. Part of me thinks it would be cool to just support that in the Lithos client, just build it around the mining client, but also cool ideas can be a lot of work.

A local HTML wizard that helps you: Download recent versions from GitHub (Ergo Node, Lithos Client, Rigel Miner) Generate/update config files via form inputs Deploy to a local apps/ folder Start/stop processes in separate terminal windows (output is shown there) Query Lithos API endpoints for basic stats

Lithos Panel is live! 🔥 Deploy your node, client, and miner all from one panel with direct sync to your API. ✅github.com/Lithos-Protoco… #Ergo $ERG @LithosProtocol

Testnet 3.0.0 release for @LithosProtocol github.com/Lithos-Protoco… #Ergo2Top10 #Ergo

The latest Lithos update makes this a great time to jump in. Spin up a node, mine on the Lithos testnet, and help stress-test the new safety checks, sync improvements, and miner workflows. Real miners make better protocols. #Ergo

Some important notes when upgrading to Lithos V3 - This update is consensus-critical, you *MUST* update to continue having your airdrop rewards tracked - You also have to delete the .lithos folder when updating. You should not save it at all, as NISP formatting has changed and any old data inside of that folder will be unusable. - This update enforces difficulty commitments, meaning that the difficulty you mine at will be locked in according to whatever you have posted on the blockchain. - When you initially start the client, a new AVL Tree (called MinerDictionary) which keeps track of miners and their commitments will be synced. Once synced, your miner will post the current difficulty set in the config on to the blockchain. If you'd like to play around with your diff value before posting it, set disableTransforms in your config to true. This option disables all transactions sent from the client. - If you have autoCommit enabled in your config (it is on by default), your client will automatically post a new commitment to the blockchain whenever it finds that your config diff and blockchain diff do not match. To disable this, you can set autoCommit to false. - Commitments take 320 blocks to take effect. - Once you have posted your initial commitment to the blockchain, your data box NFT will be saved in the .lithos folder. Once this happens, you will no longer have to sync the MinerDictionary. github.com/Lithos-Protoco…