Dbcache bitcoin mining
These interface changes break compatibility with 0. Client software using these calls with named arguments needs to be updated. In this version, it now supports non-segwit clients even after activation, by removing all segwit transactions from the returned block template.
This allows non-segwit miners to continue functioning correctly even after segwit has activated. Due to the limitations in previous versions, getblocktemplate also recommended non-segwit clients to not signal for the segwit version-bit. Since this is no longer an issue, getblocktemplate now always recommends signalling segwit for all miners. This is safe because ability to enforce the rule is the only required criteria for safe activation, not actually producing segwit-enabled blocks.
Memory usage for the UTXO cache is being calculated more accurately, so that the configured limit -dbcache will be respected when memory usage peaks during cache flushes. The memory accounting in prior releases is estimated to only account for half the actual peak utilization. The default -dbcache has also been changed in this release to MiB. Users who currently set -dbcache to a high value e. Users on low-memory systems such as systems with 1GB or less should consider specifying a lower value for this parameter.
Additional information relating to running on low-memory systems can be found here: Detailed release notes follow. These interface changes break compatibility with 0. Client software using these calls with named arguments needs to be updated. In this version, it now supports non-segwit clients even after activation, by removing all segwit transactions from the returned block template.
This allows non-segwit miners to continue functioning correctly even after segwit has activated. Due to the limitations in previous versions, getblocktemplate also recommended non-segwit clients to not signal for the segwit version-bit.
Since this is no longer an issue, getblocktemplate now always recommends signalling segwit for all miners. This is safe because ability to enforce the rule is the only required criteria for safe activation, not actually producing segwit-enabled blocks. Memory usage for the UTXO cache is being calculated more accurately, so that the configured limit -dbcache will be respected when memory usage peaks during cache flushes. The memory accounting in prior releases is estimated to only account for half the actual peak utilization.
The default -dbcache has also been changed in this release to MiB. Users who currently set -dbcache to a high value e. Users on low-memory systems such as systems with 1GB or less should consider specifying a lower value for this parameter.
Additional information relating to running on low-memory systems can be found here: Detailed release notes follow.