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 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 keep the entire blockchain history. The new version can retrieve the required information from blocks retained since DigiDollar's minimum activation height.

Reduced disk footprint

The recommended configuration includes prune=2000. This is a target in mebibytes, not a permanent ceiling: after activation, the node must retain blocks belonging to the DigiDollar era.

A consensus rule to keep nodes aligned

Outputs created before the scheduled minimum height can never be considered valid DigiDollar collateral. This distinction ensures that full and pruned nodes reach the same result when validating collateral release.

DigiDollar: a native asset backed by DGB

DigiDollar is designed as a native DigiByte asset intended to represent a value close to one US dollar. Its architecture locks DGB as collateral and uses DGB/USD prices supplied by multiple oracles.

The planned implementation uses locked UTXOs, Taproot mechanisms, and MuSig2 Schnorr signatures. Branch notes describe thirty-five oracle slots, with seven signatures required for consensus.

DigiDollar is not active yet

Version 9.26.4 does not launch DigiDollar on mainnet. Activation must occur through a BIP9 deployment using version bit 23. Until the conditions are met, DigiDollar consensus rules, RPC commands, and network functions remain inactive.

Conclusion

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