The latest DigiByte Core update is now available, version 6.17.2.
This will be mostly of interest to pool-operators, as we prepare the way for hashing algorithm replacements. We need to get pool operators running DigiByte Core 6.17.2+ so that we can ensure a smooth transition down the road to Odocrypt and other algorithms.
At this point the Odocrypt algorithm is not included.
You can download the source code from:
Alternatively you can download binaries from:
The most notable changes in 6.17.2 are:
Preparation for Odocrypt
We’re getting ready for Odocrypt and so have made some adjustments to the way that we handle algorithm upgrades in the future. While there is no date set yet for the Odocrypt implementation, it’s important we get as many miners / pools on to Odocrypt as soon as we can to ensure a smooth and non-contentious transition.
Mine multiple algorithms on a single instance
This means that pool operators no longer need to run multiple instances of digibyted for each algorithm they want to support (having 5 copies of the blockchain running), they can simply update their pool software to pass the algo every time getblocktemplate is called.
If no changes are made, existing software will still function the same with algo= being passed in digibyte.conf
Under the Preferences you can limit the maximum storage that DigiByte Core will use to store the blockchain if you are severely limited on drive-space. Naturally where possible people should keep & seed the full blockchain, though this setting helps those who are unable to keep all the data:
Partial spend avoidance
The -avoidpartialspends flag has been added (this is not enabled by default) which will always spend existing UTXO to the same address together, even if it results in slightly higher fees. This is done to potentially increase privacy.
Partially Signed Transaction support
Implementation of BIP174
Scan TX output support
Additional documentation for the scantxoutset RPC call can be found here:
Transaction Indexing improvements
You can toggle -txindex on the fly. When disabling, txindex will not be deleted automatically, so it can be turned on later without needing a full resync.
The DigiByte testnet issues have been resolved and the testnet has been reset
32-bit architecture support sunset
At this stage, 32-bit architecture is not supported. This is predominantly due to the number of blocks the DigiByte blockchain has, which exceeds what the Bitcoin blockchain will have by the year 2100. Due to this, with current memory mapping, we are unable to support 32-bit Windows, Linux, and ARM CPU’s. Additional work is being done on the code-base to potentially support memory-limited devices, however any interested users can keep track of the progress over on GitHub:
Abnormal high memory usage · Issue #144 · digibyte/digibyte
I operate Powermining.pw pool and have 4 algorithms from DigiByte available, during last version(6.16.2) i noticed that…
For more information on the inclusions from upstream Bitcoin Core, you can read:
Bitcoin Core version 0.17.0 released
Bitcoin Core version 0.17.1 released
Note that the block database format also changed in version 0.8.0 and there is no automatic upgrade code from before…
If you are recreating the DigiByte Core builds with Gitian, the following are the hashes generated:
The full build-report can be found here: