Subblocks in Ergo
Testing faster provisional inclusion feedback with input blocks while ordering blocks preserve final settlement.
TLDR
Under the 2026 Matrix devnet/test stream, Ergo is testing a split between input blocks (sub-blocks) and ordering blocks. The design targets provisional transaction-inclusion feedback in roughly 1-2 seconds while preserving ordering blocks for final settlement, which would make user feedback about 60× faster than a 2-minute block interval and failure detection up to roughly 180× faster than a 6-minute wait.
What Are Sub-blocks and Ordering Blocks?
Sub-blocks (Input Blocks)
These are block candidates generated with a lower difficulty threshold than full blocks. They are produced approximately once per second and carry most transaction data. This allows transactions to propagate and confirm much faster.
Ordering Blocks
These are the traditional full blocks of Ergo's proof-of-work system, now renamed as ordering blocks. They are generated roughly every 2 minutes and maintain the overall consensus and security of the blockchain.
Note: The naming "input blocks" (or sub-blocks) and "ordering blocks" was proposed in detail in this document.
Enhanced User Experience
Rapid Onchain Confirmations
Everyday transactions—such as receiving tokens from DEX swaps or wallet-to-wallet transfers—are intended to receive provisional inclusion feedback in approximately 1-2 seconds once sub-block support is active. These input blocks are produced roughly every second and carry transaction data, allowing dApps and wallets to detect transaction inclusion almost instantly.
However, this does not change the overall 2-minute block time for ordering blocks, which are still required for final settlement and consensus. As a result, existing dApps that rely on ordering blocks for confirmation will continue to behave as before.
While some tools may treat sub-block inclusion as sufficient for faster user feedback, more security-sensitive applications—such as centralized exchanges or specific dApps handling large-value transactions—will still wait for a set number of ordering blocks to reduce the risk of chain reorganizations or 51% attacks.
Faster Failure Detection
Instead of waiting up to 6 minutes to detect a transaction failure, the new system is designed to detect failures in about 2 seconds, an improvement of up to roughly 180× in responsiveness.
A More Cooperative Mempool
The design shift transforms the mempool from a competitive (PvP) environment into a cooperative, multiplayer-like system, enhancing overall network responsiveness.
In a Nutshell
Ergo's input-block / ordering-block design is intended to improve transaction processing speed and reliability without changing the security role of ordering blocks. The 2026 Matrix implementation is still in devnet/test rollout, so production users should treat sub-blocks as active protocol R&D until release notes state otherwise.
For a deep dive into the technical details behind these changes, see the technical details.
Current Rollout Status
In 2026 the input-block work moved under the Matrix implementation and devnet test stream. The latest public notes describe devnet seed-node APIs, Matrix candidate-line merges, miner-facing API work, and remaining serialization, sync, peer-ban, Stratum proxy, and broader testing caveats.
Practical takeaway: wallets and dApps can prepare for faster provisional feedback, but final production guidance should follow the Ergo node release notes and miner rollout status.