DigiByte v9.26.4: A unique update with the arrival of DigiDollar

DigiByte Core 9.26.4: A targeted update

DigiByte Core 9.26.4 is a maintenance release following versions 9.26.2 and 9.26.3. It is not a complete protocol overhaul, but it introduces an important change for node operators: DigiDollar compatibility with pruned mode.

A pruned node validates blocks and transactions like a full node but does not necessarily store the entire blockchain history on its disk. It can delete old block files that are no longer needed for current operations while maintaining the data necessary for network validation.

Before version 9.26.4, the validation mechanisms for DigiDollar required a full transaction index, which prevented the use of pruned mode. The new version removes this constraint by allowing the node to retrieve the necessary information directly from the blocks kept since the minimum activation height of DigiDollar.

Reduced disk footprint for future DigiDollar nodes

The main novelty of DigiByte Core 9.26.4 concerns operators who wish to participate in network validation without storing over twelve years of full history.

The recommended configuration in the release notes uses the following option in the digibyte.conf file:

prune=2000

This value represents a target in mebibytes. However, it is not a permanent limit: after DigiDollar activation, the node must keep all blocks between the minimum activation height and the current chain tip. The space used will therefore continue to increase gradually.

Pruned mode primarily reduces storage dedicated to history prior to DigiDollar. It still allows for transaction validation, wallet usage, mining participation, and, according to the project's technical notes, the execution of functions necessary for DigiDollar.

A consensus rule to maintain node agreement

DigiByte Core 9.26.4 also introduces a targeted consensus rule. Outputs created before the minimum height scheduled for DigiDollar activation can never be considered valid DigiDollar collateral.

This distinction is essential to ensure that a full node and a pruned node always reach the same result when checking a refund or collateral release operation.

The software also adds several operational protections. A pruned node must keep all blocks belonging to the DigiDollar era. If this data is missing, unreadable, or inconsistent, the software must refuse to start normally rather than continue validation with incomplete information.

What the DigiByte Core 9.26 branch represents

The DigiByte Core 9 branch is based on Bitcoin Core 26.2. It modernizes a significant part of the DigiByte software foundation and integrates the code necessary for the deployment of DigiDollar.

The various versions of the 9.26 series have served distinct functions:

DigiByte Core 9.26.2

First major version intended for the DigiByte network with the DigiDollar deployment. It also restored a rule rejecting the old Groestl mining algorithm, which was removed during the Odocrypt activation.

DigiByte Core 9.26.3

Fixes a header synchronization issue encountered by some new nodes and enables the transaction index required for the DigiDollar implementation by default.

DigiByte Core 9.26.4

Adds compatibility between DigiDollar and pruned mode, removing the requirement to maintain a full transaction index when using pruning.

DigiDollar: A native asset backed by DGB

DigiDollar is presented by its designers as a native asset of the DigiByte blockchain intended to represent a reference value close to one US dollar.

Its architecture relies on locking DGB as collateral. In the model documented by the project, a user locks DGB to create DigiDollars. The system then uses DGB/USD price data provided by multiple oracles to determine the value of the collateral.

Unlike a stablecoin issued by a company holding dollars in a bank account, DigiDollar is designed to operate directly within the rules of the DigiByte protocol. It is not presented as a classic DigiAsset or a token managed on a separate blockchain.

The planned implementation uses locked UTXO outputs, mechanisms associated with Taproot, and MuSig2-type Schnorr signatures. The 9.26 branch notes describe a set of thirty-five oracle slots, seven of which are required for price data to be recognized by the consensus.

DigiDollar is not yet active on the mainnet

The release of DigiByte Core 9.26.4 does not mean that DigiDollar is immediately usable on the mainnet.

Its activation must occur via a BIP9 deployment using version bit 23. Miners must signal their compatibility during the period provided by the protocol. As long as the activation conditions are not met, the consensus rules, RPC commands, and network functions specific to DigiDollar remain inactive.

It is therefore more accurate to present DigiByte Core 9.26.4 as a version that prepares and secures the deployment of DigiDollar, rather than the definitive launch of an already operational stablecoin.

An ambitious mechanism that carries risks

DigiDollar constitutes an important evolution of the DigiByte protocol, but its operation does not automatically guarantee permanent parity with the dollar.

Like any asset based on cryptographic collateral and external price data, its operation will depend notably on the value of DGB, the quality of data transmitted by oracles, available liquidity, collateralization parameters, and the robustness of the implementation.

The term stablecoin here describes the economic goal of the protocol. It should not be interpreted as a financial, banking, or regulatory guarantee of permanent value maintenance at one dollar.

Should you update your DigiByte node?

Operators already using the 9.26 branch can install version 9.26.4 by properly stopping DigiByte Core, replacing the executables, and then restarting the service.

According to the release notes, a full node operating normally does not require reindexing when moving to version 9.26.4. However, the activation of pruned mode must be prepared with care, particularly by removing any txindex=1 configuration, which is incompatible with pruning.

Mining pools, exchanges, explorers, and other infrastructure must examine this version with particular attention, as it contains an additional rule participating in the consensus and prepares for the future activation of DigiDollar.

Conclusion

DigiByte Core 9.26.4 is primarily an infrastructure release. It reduces the storage constraints associated with the future operation of DigiDollar and ensures that full and pruned nodes apply the same validation rules.

This update does not yet launch DigiDollar on the mainnet. However, it provides a more accessible foundation for node operators and brings the project closer to its activation phase by miners.

DigiDollar represents an unusual attempt to integrate a dollar-pegged asset directly into a UTXO blockchain, without a centralized banking issuer or a separate sidechain. Its real value can be evaluated after its activation, once its operation, stability, and adoption have been observed under mainnet conditions.