
Ergo protocol reference client 6.0.4 released
6.1.4 (for RockDB) released as well

6.1.4 (for RockDB) released as well
A minimal multi-agent demonstration of a pure-credit joint economy built on Basis IOU notes. Three scripted agents exchange services and settle with signed off-chain notes through the basis-mcp MCP server. No reserves, collateral, or on-chain redemption are required — this demo focuses on the simplest possible credit-based payment flow.
https://github.com/BetterMoneyLabs/basis-tracker/tree/master/demo/agent_coop
A LETS is a local community where members create common credit money by accepting each other's IOU notes. On Basis:
basis-ui wallet.https://github.com/BetterMoneyLabs/basis-tracker/tree/master/demo/lets_tutorial
reposting from https://x.com/Armeanio/status/2084019274268787111
He who controls order flow is king.
What if we can grant that right in a fair way?
Lithos is a decentralized mining pool protocol built on Ergo. It replaces the traditional centralized pool operator with smart contracts that verify miner work through Non Interactive Share Proofs and handle payouts automatically.
Lenders can provide ERG as collateral to earn yield while enabling trustless block production. Miners connect via Stratum as usual yet retain the ability to insert necessary transactions directly into the blocks they themselves mine.
This removes any single party that could censor content or custody funds and raises the degree of decentralization in proof of work systems. The protocol is designed to be blockchain agnostic in principle though its first implementation targets Ergo.
Testnet clients already demonstrate collateral contracts transaction scheduling and the core insertion capability.
PlasmaDex forms the liquidity layer inside the Lithos ecosystem.
It is a specialized automated market maker that collects constant fees structured so the fee stream itself avoids the usual effects of impermanent loss. Liquidity positions are tracked with AVL trees and represented as unique NFTs. Each position therefore functions more like a tradable revenue generating asset than a conventional pool share.
Holders can claim accumulated fees and the positions themselves can move on secondary markets. An initial ERG LIT pool has been tested inside the Lithos client along with deposit swap redemption and fee claim flows.
PlasmaDex therefore gives miners and lenders an additional way to participate beyond pure mining or simple collateral provision while keeping all accounting efficient and verifiable on chain.
TwinPools is a dual liquidity design that sits on top of PlasmaDex and the Lithos mining layer. What it is can be stated simply. Two linked pools serve the same trading pair. The Primary Pool acts as a normal automated market maker and continuously sets the mid market or spot price.
Anyone may deposit into it or trade against it. The Secondary Pool holds reserved capital that only the miner of the current block is allowed to spend.
That capital exists only to enforce a hard maximum slippage band expressed as a virtual bid and ask around the Primary Pool price.
In a concrete case if the spot rate stands at one hundred LIT equal to one ERG and the maximum slippage sits at five percent then a market buy of one hundred LIT is guaranteed never to cost more than one point zero five ERG while a market sell is guaranteed never to receive less than zero point nine five ERG.
Why this type of solution is needed follows directly from the nature of order flow.
In every blockchain the party that assembles the block decides the sequence of transactions and therefore controls order flow.
On proof of work chains that party is the miner.
When the same miner can also insert transactions the power becomes complete.
In ordinary decentralized exchanges this power is left unconstrained.
The result is unpredictable slippage for traders and external extraction that benefits neither the liquidity providers nor the average user.
Large market orders move the price in ways no one can forecast in advance.
Sandwich style reordering can worsen the outcome still further.
Existing pool designs whether classic constant product concentrated range programmable hooks or proprietary market maker systems improve capital efficiency or tighten spreads yet they leave the underlying control of order flow either passive or closed.
None of them grant the right in a transparent rule bound and fee shared manner that keeps the system open.
TwinPools is needed because it converts that inevitable control into a limited compensated service that protects the trader with a hard price band while still rewarding the liquidity providers who supply the capital and the miners who enforce the band.
How TwinPools works follows a clear sequence.
The Primary Pool updates the spot price in the ordinary fashion. The protocol then publishes the virtual bid and ask derived from that spot price the chosen maximum slippage percentage and the relative sizes of the two pools.
A user market order enters the mempool. The miner observes every related transaction destined for the block.
Using only Secondary Pool capital the miner may construct any required counter transactions and place them in the precise order that keeps the user fill inside the published band.
Residual value captured inside the band remains limited by the spread itself.
Fees generated by Secondary activity are shared between the providers of that pool and the miner according to transparent rules. Deposits into the Secondary Pool stay open to ordinary users the protocol larger miners or lenders.
After the block any residual inventory can be rebalanced under protocol parameters.
Because Lithos already supplies the insertion right and PlasmaDex already supplies AVL tracked positions the entire mechanism stays native to the existing stack.
Relative to other designs TwinPools remains complementary.
A classic single pool leaves slippage unbounded and the miner passive.
Concentrated liquidity improves efficiency inside chosen ranges yet still offers no hard guarantee and leaves the miner passive.
Programmable hooks can optimize idle capital inside one open pool yet do not create a second reserved inventory controlled exclusively by the current miner.
Proprietary systems achieve tight spreads with closed capital.
TwinPools keeps Secondary deposits open and on chain.
Shared self custodial approaches avoid traditional deposits. TwinPools continues to use deposited pools while differentiating access rights and incorporating the native miner ordering privilege.
Any modern curve or range technique can serve as the Primary Pool while the Secondary Pool independently supplies the execution guarantee.
In this way TwinPools grants control of order flow under clear limits and shared rewards so that the power serves the network rather than extracting from it.
The virtual bid-ask already creates a clear, enforceable price band around the Primary Pool spot price.
The miner’s ability to insert and order transactions, combined with exclusive access to Secondary Pool capital, already lets the system fill market orders inside that band in a deterministic way.
Those two primitives (a reliable published bid-ask plus miner-driven filling) form the essential matching core of an order book.
To move from market-order guarantees to a full order-book DEX the following pieces would be added on top of the existing TwinPools framework:
Resting limit orders become first-class citizens.
Users post buy or sell orders at specific prices.
These orders sit in an on-chain or client-managed book that the miner can see when constructing the block.
Because the miner already controls transaction ordering and can draw on Secondary Pool liquidity, the miner can match incoming market orders or other limit orders against the resting book, using
Secondary capital only when needed to complete fills that stay inside or improve upon the published band.
Matching logic is executed by the miner inside the block.
The miner runs a simple price-time priority or pro-rata matching routine over the visible orders for that block, constructs the necessary settlement transactions, and inserts them in the correct sequence.
Secondary Pool capital acts as a backstop inventory so that partial fills or temporary imbalances can still be resolved without breaking the maximum-slippage promise for pure market orders.
Cancellations and updates are handled as ordinary transactions that the miner includes or sequences according to the same rules. Because everything settles atomically in the block the user posts to, the usual risks of partial execution across multiple blocks are reduced.
The Primary Pool continues to provide continuous price discovery and deep passive liquidity, while the Secondary Pool and the miner’s matching role supply the discrete, order-book-style execution layer.
Over time the published virtual bid-ask can tighten as Secondary liquidity grows, and the system can support more sophisticated order types (fill-or-kill, immediate-or-cancel, post-only) without changing the underlying dual-pool architecture.
In the Lithos setting this path is especially natural.
The protocol already gives miners the insertion and ordering rights that a centralized matching engine would otherwise hold.
TwinPools simply constrains those rights with transparent rules and fee sharing, then extends them from market-order protection to full book matching.
The result is an on chain order book that remains decentralized at the block production level, inherits PlasmaDex’s AVL-tracked positions and constant-fee model, and still offers the hard execution guarantees that pure AMMs lack.
Set up with clear matching rules, adequate Secondary depth, and client software that reliably surfaces the resting book to miners, the same mechanism that today guarantees a maximum slippage on market orders can grow into a complete order book DEX while preserving the open, fee shared character of the original design.
By CheeseEnthusiast:
" Vibecoded an ErgoScript LSP and IntelliJ 2026.2 plugin. Has support for type inference, suggestions, auto-complete, and special handling of prefixed variable names (for things like injected constants, context vars, etc.)
Attempts to make P2P cash over the Internet started before Bitcoin, see, for example, "Peer-to-peer money: free currency over the internet" by Kenji Saito from 2003, or original RipplePay idea and service by Ryan Fugger from 2005. Cryptocurrency space ignored earlier work and started own attempts to do p2p cash, such as Lightning / Cashu / Fedimint etc.
Thus we have two non-intersecting worlds: original p2p cash which is based on p2p trust, and cryptocurrency-backed which
does require for 100% backing with cryptocurrencies. We combine the best from two worlds in Basis:
* money issuance can be based purely on trust
* optionally, on-chain reserves on Ergo can back issued p2p cash
* it is up to a peer to demand for backing, to choose whom to trust, whom to blacklist etc
* thus this is providing self-sovereign control on what kind of money (and so risk) to accept
* we also call it free digital banking on steroids
Basis is a low-level framework which can be used in many monetary applications, such as:
* community currencies (LETS, local currencies etc)
* value transfer networks, informal (such as Hawala) and formal
* agentic economies
and so on
There could be multiple coexisting Basis based communities (using different instances of the same software). They can always have economic connections via on-chain reserves, it would be good to
explore more efficient options.
Whitepaper is at https://github.com/BetterMoneyLabs/chaincash/blob/master/docs/basis/basis.pdf
Offchain server (under public domain license) https://github.com/BetterMoneyLabs/basis-tracker
Everything is public-domain open-source, there is no token. Looking for contributors!
Working on a simple wallet now. Looking for communities willing to play with it!
Real-time dashboard for node & oracle runners.
Not another RPC table — something you can *see*.
Live
https://ergolumen.net
https://ergolumen.net/oracles
What you get
• 3D Network Orbit + World Map
• Blocks, mempool, metrics, real miners
• Oracles: ERG/USD · ERG/XAU
• Connect *your* node via Bridge (Docker, no open ports)
Code
https://github.com/from-ufa/lumen
---
Need testers
Node runners
Settings → Connect my node → Docker next to Ergo → switch to My Node
Oracle runners
Open /oracles → check LIVE/STALE, epoch, lag
Reportedly, first Firo to Ethereum and Firo to Ergo transfers done by Rosen bridge, we are happy that Ergo tech is used to tackle the issue of discrimination of PoW and privacy focused assets by centralized exchanges.
Let the liquidity flow with no masters!
-----------
# Transfer 4.0 Firo from Firo to Ethereum
## Event Details
Event ID:
047e93de3a5d45604d3a5c2dbb3e4979df7a7b870969a0272873718d9b3eb6d8
## Lock Transaction
https://explorer.firo.org/tx/fa3eccf428927cfb2d358fe2db5c3658992b4858a70eac2258623183c88e6cd7
----
## Watcher Commitments
[Commitment 1](https://explorer.ergoplatform.com/en/transactions/21240e090bbdeed1df29efc3996169dc0a925a5ca2121cbb752ae8ca5f19dc21)
[Commitment 2](https://explorer.ergoplatform.com/en/transactions/4499a993fdfdf60f08ca068e1058e7d5c8d708ade9db9b92ea467efd43ea46e1)
[Commitment 3](https://explorer.ergoplatform.com/en/transactions/72a3941a4f59f44ea9bcc6fb2e8382e8dc2f3079217cdd7d6e063e865b9bee28)
[Commitment 4](https://explorer.ergoplatform.com/en/transactions/e30cffbad6bf41572c9576a4f559d58bd8f6b4e387088d3a0d86e4e88f0f12e4)
[Commitment 5](https://explorer.ergoplatform.com/en/transactions/888899fa004ba4394162f67477d26133341f7f07669422865b95e566579a38d0)
## Trigger Transaction
https://explorer.ergoplatform.com/en/transactions/c8b0f8e98acd02df1edaf24460631738525019e68c2d02dd738e915d49963e02
## Payment Transaction
https://etherscan.io/tx/0xf0eef069b569d374cf99129a09e781a3cb374ff4f8d86b84641a01d34e1ba7af
## Reward Transaction
https://explorer.ergoplatform.com/transactions/fa2096116e7e39092226840a582cd067294216c763ac57b6864984945f77a0de
----
# Transfer 5.0 Firo from Firo to Ergo
## Event Details
Event ID:
b58145a59a7ba8ae3cd47c7473c67c0abc164c86dd0007a613227891feaec2b7
## Lock Transaction
https://explorer.firo.org/tx/de1d2b12dea99f56ce291b1a8f6784be161e5363d08587097b447b29bc45b2fd
----
## Watcher Commitments
[Commitment 1](https://explorer.ergoplatform.com/en/transactions/200b2363910a413b57ef2f9cc9d23b0a669e746d91aafa529a222e6f7ff1fa13)
[Commitment 2](https://explorer.ergoplatform.com/en/transactions/549ab84fea6002550f21541673e6db5973be8c17499651eeb5513b216446599c)
[Commitment 3](https://explorer.ergoplatform.com/en/transactions/85f5bade6677faa4c12e8e208ad09722d8e165246f9c1254b93ac1d6c4149a6d)
[Commitment 4](https://explorer.ergoplatform.com/en/transactions/8e4b792a47e73b76329b776c53e9c62f8b63e142dff1bf8eb867b129e904e4e0)
[Commitment 5](https://explorer.ergoplatform.com/en/transactions/9d06e77568d30afe90139a7a28900d8ec51774b3698b8e37033ce9325ec1c921)
## Trigger Transaction
----
## Payment & Reward Transaction
This release allows to play with ordering/input blocks design with fast confirmations in an experimental devnet network
https://github.com/ergoplatform/ergo/releases/tag/v6.5.0-RC3
Ergo reference client 6.0.3 (default release) https://github.com/ergoplatform/ergo/releases/tag/v6.0.3
Ergo reference client 6.1.3 (rocks db) https://github.com/ergoplatform/ergo/releases/tag/v6.1.3
- Bug fixes
- Improved send options
Two Ergo enthusiasts, kushti and Mad Spectator, successfully tested Basis note transfer over Meshtastic. In a forest with not Internet connection available, IOU note was passed, and the note is redeemable once Internet connection is there.
The assumption was that two participants Alice and Bob dont have Internet connection during trade, but can have it after. So Alice is signing a note and passing it as JSON to Bob over mesh network (Meshtastic powered)
There was issue with 200 bytes limit. In the test message was about 670 bytes and so I splitted JSON manually to send over mashtastic ui. But it is possible to optimize it and have it under 200 bytes.
With this note, also witnessed by basis tracker, redemption is possible when Internet available.
In a next test, a core assumption would be that both Alice and Bob do not have Internet connection and only tracker has permanent one. For starters, tracker is fully trusted, then we will relax trust by using NIPoPoWs / ergo headers distribution around mesh, Merkle proofs for submitted transactions etc. Then we can consider even more complex setting where even tracker has connection occasionally, so also on spv and/or nipopows
So there will be much more off the grid tests to cover all the real world off the grid scenarios but in many cases what is more or less done as PoC is okay. So we can start reach communities from now.
A paper on Basis got accepted into RAMICS'26 conference on alternative currencies and monetary studies, see accepted papers at https://drive.google.com/file/d/1FdbzbDSx-qHJqLva1_QWqoKiEm2tRS_H/view . The paper will be used as Basis whitepaper as well and will be published in coming days.