During the first week of August, an abnormally high network load was detected on the Dash network consisting of around a million 1 input 1 output transactions with a fee just higher than 1 duff per byte. After research, the artificial load on the Dash network was possibly a direct stress test organized by an outsider not involved in the team or an attempted attack on the network.
This phenomenon occurred over the course of 2 days, generating two large spikes in transactions:
- The first occurrence on Wednesday, 2019–08–07, between 00:00 and 08:30 (lasting 8.5 hrs) with around 650,000 transactions per second
- The second occurrence right after on Wed/Thu, 2019–08–07/08 between 23:00–02:30 (lasting 3.5 hrs), with an average amount of 300,000 transactions per second.After investigations led by the team
to analyse the Dash blockchain spikes as well as MN logs and their PoSe score, there have been multiple interesting discoveries all along.
Some pools are capped at only 1MB blocks
Mining pools will change this naturally once usage approaches 1MB to capture more fees and be more profitable. This is due to custom implementations.
Some pools seems not to be emptying the mempool and are often producing near empty blocks.
The dash team is currently in active talk with these pools in order to figure out what solutions can be used to prevent pools from including the transactions that appear to be spam (1 input, 1 output, very low fee) while ensuring the rest of transactions can pass freely.
Some Masternodes crashed due to not having enough storage space
This was a result of having to store the IS Lock for every transaction. This resulted in nodes running on minimal storage (around 15–20 GB) and not having enough space to store all the IS Locks. After 0.14.0.3 release, IS Locks will be removed as soon as they are confirmed via a ChainLock. This should reduce the size of the `llmq` directory significantly over time to improve overall performances.
Some Masternodes banned other Masternodes under high load when on the brink of a new quorum becoming active
In order to fix this, the team is currently investigating the reason in order to detect the exact situation and then re-verify failed sigs with the previous active set. This element will also be a part of the 0.14.0.3 release.
Some user transactions did not get included in a block quickly by using default fees
The fee selection algorithm and UI in the Dash Core wallet is being updated in 0.14.1 thanks to the backporting of Bitcoin 0.15. The fee selection algorithms in the mobile wallets are being reviewed as well to be modified as soon as possible. To address the discoveries outlined above, the 0.14.0.3 version is being released. The complete release includes various bug fixes and improvements. The upgrade is strongly recommended for all Masternode owners and for the entire community and partners.
Dash Core v0.14.0.3 Changes
- Database space usage improvements
- DKG and LLMQ signing failures fixed
- Signed binaries for Windows and MacOS disable AppNap during sync and mixing
-New RPC command: quorum memberof <proTxHash>
You can directly consult the release notes for information at: https://github.com/dashpay/dash/blob/v0.14.0.x/doc/release-notes.md