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 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…

Lithos Client v3.0.0 (testnet) is live ⛏️ This release focuses on hardening the protocol and improving miner experience, expanding fraud proofs, tightening sync logic, and laying groundwork for more flexible reward and coordination mechanics. Release 👇 github.com/Lithos-Protoco…

Updates @LithosProtocol After this 3.0 update, we can work on emissions and then Lithos is ready for mainnet. It would be good to get miner feedback here. 3.0 coming soon. - Finished all new Fraud Proofs added for security purposes. In general Lithos is resistant against all critical attacks. There is however one class of attack we are trying to see if viable. - Finished sync process for Miner Dictionary. This is a separate dictionary which is storing information about miners, balances, and options (can be extended in the future). - Lithos uses EIP-3 addresses now, mostly for more clarity for newer miners - Lithos now uses a smaller NISP_WINDOW parameter, reduced down to about 2 hours before a block is mined. This means miners must be mining within 2 hours of a block being found in order to be rewarded properly. The impact of this is that each miner's ideal diff value has changed. - Updates to docs involving miner voting parameters, along with some additional NISP information - All contracts have token distribution capabilities now, which will be used later when we decide emission parameters and discuss it a bit more. -Fixing a sync bug with Miner Dictionary now then can release 3.0 after that's done. There are still many improvements that can be made, however most of them are client-side improvements (more robust tx processing, persistent dbs for rollups and miner dictionary, pulling boxes from mempool, better stratum code, etc) and do not require consensus changes.

Mining secures the network. Infrastructure decides who controls it. If miners don’t own the coordination layer, someone else will. Building PoW infrastructure that keeps control local isn’t optional, it’s how decentralization survives. #Ergo