Headline changes since 1.0.7
- Support for creating double-spend enabled transactions; if a double-spend of an input is seen, a HTTP notification will be sent to a specified endpoint. (Please refer to here for further details)
- New getorphaninfo RPC.
- New verifyScript RPC.
- New getmerkleproof2 RPC consistent with latest TSC.
- maxstackmemoryusageconsensus parameter added to output of getsettings RPC.
- sendrawtransaction and sendrawtransactions RPC can be used with dontCheckFees even when a transaction is already known.
- sendrawtransaction and sendrawtransactions RPC modified to optionally return list of unconfirmed parents.
- New configuration parameter -dustlimitfactor available to define dust.
- Free consolidation transaction can be used to avoid dusting attack.
- Adjusted default maximum validation duration for async tasks to better handle chains and long graphs.
- Change algorithm for using ancestor height rather than ancestor count.
- Improve release rate from Oprhan pool.
- Better performance as a result of improvements to cs_main processing.
- Improved validation of chains.
- Transactions will not be accepted if the result is an in-mempool ancestor chain of height 10,000 or more. Previously this figure was 1000 transactions.
- The default value for the maxorphantxsize configuration parameter has been changed to 1GB
- The maxcollectedoutpoints configuration parameter is no longer used and has been removed.
- The STN is being reset.
Changes since 1.0.8.beta
- Fixed the dust return script condition in IsDustReturnScript. The previous version incorrectly contained an OP_4.
- Fixed a bug that caused double spend notifications to be skipped for previously detected but unreported double-spends.
- Fixed an issue that could cause mempool and journal inconsistencies during a reorg.
Other technical changes
- Remove all support for Tor.
- Configure docker images so that core dump is preserved.
- Include header files in CMAKE build.
- Make CBlockIndex thread safe to remove cs_main dependency.
- Encapsulate mapBlockIndex and remove cs_main dependency.
- Create leaky bucket for tracking peer suspension score.
- Remove non-ctor init function in networkprocessing.
- Soft block orphaning support (not used).
- Refactor NET logging category.
- Move lNodesAnnouncingHeaderAndIDs into BlockDownloadTracker.
- Replace rand with the facilities in .
- Allow parallel downloads of the same block from several peers.
- Error message can be of 'txid' instead of 'hash' at the beginning for incorrect txid value while executing getmerkleproof RPC as like verifymerkleproof RPC.
- GlobalConfig class is not thread safe.
- dev branch clang warning -Wdefaulted-function-deleted.
- Initialize class members where clang requires.
- Fix: P2P Messages In Multiple TCP Segments.
- Improve detection of longer chains.
- Improved orphan transaction processing.
- Reduce Logging Cost.
- Fix runtime errors in unit test (Windows os).
- Global thread-local interferes with address sanitizer.
- Remove libatomic dependency.
- Undefined behaviour sanitiser reporting vector out of bounds access in CBlockFileInfoStore::FlushBlockFile.
- Fix: St16invalid_argument displays many times on startup.
- Falsely logged error opening rev.dat in logs.
- Fix: coredump at shutdown within logging.
- Fix: failure in CTxMemPool::GetMemPoolChildrenNL.
- Fix: a possible false negative result during querying the PTV processing queue.
- Remove maxcollectedoutpoints configuration parameter.
- Improved stability when accepting transactions during the reorg.
Functional tests
- Fix: import-rescan.py - possible race condition during tip update signaling.
- Fix: bsv-factorMaxSendQueueBytes functional test fails on Windows.
- Remove test/test_bitcoin_fuzzy.cpp.
- Fix: failing functional test bsv-getdata.py.
- Add a new FT to test long chains of CPFP txs.
- Fix: bsv-magicbytes.py functional test failed.
- Fix: internittent failure in bsv-block-propagation-priority.py.
- Fix: Random failures of bsv_pbv_firstvalidactive.py functional test.
- Fix: Failing util tests on Windows.
- Fix for issue detected by bsv-dsreport.py and bsv-ds-bad-callback-service.py on Windows.
- Wait_for_getdata method is misused in functional tests.
Security
- Remove warnings from source code.
- Update out-of-date dependencies with known security issues.
- Lock consistency violations in WPUSMutex.
- CReeRate calculation of CPFP groups allows invalid amounts.
- Incorect usage of cs_main.
Scaling Test Network (STN) Reset
The Scaling Test Network has been reset at block height 5. This block has hash
00000000e9222ebe623bf53f6ec774619703c113242327bdc24ac830787873d6.
Additional notes
New command line option -dustlimitfactor available to define dust.
Until now, the minimum ratio between a transaction output amount and its corresponding fee is 3/1.
If this condition was not met, the transaction was considered “dust” and was rejected during validation.
This factor can now be configured via the new “-dustlimitfactor” option in percent, which still defaults
to 300% but can be set to any value between 300% and 0%.
If the -dustlimitfactor is set to zero, then no transaction output is regarded as dust.
The formula for calculating the dust threshold is as follows (integer arithmetic):
s = serialized size of transaction output
d = dustlimitfactor, percent value between 300 and 0, default: 300
r = dustrelayfee, default: default-minrelaytxfee, 250 as of v1.0.8
m = 148, minimum bytes of spendable input
d * (r * (s + m)/1000)) / 100
Note that the division by 100 as the dustlimitfactor specifies a percentage value.
A transaction exactly at the threshold passes. If one output is below the threshold, the transaction is rejected.
Example: For a typical transaction with an output of 34 bytes in size, the formula yields a threshold of 135 Satoshis.
s = 34
d = 300
r = 250
m = 148
Threshold = (300 * (250 * (34 + 148)/1000)) / 100 = 135
Note the same formula would give a threshold of 136.5 Satoshis if floating point arithmetic is used.
A typical transaction output, with the default parameter settings in 1.0.8, needs to be worth 135
Satoshis not to be considered dust. Note that due to rounding, the calculated dust threshold for the
example transaction becomes 0 if the dustlimitfactor and the dustrelayfee are very low.
Free consolidation transaction can be used to avoid dusting attack.
Transaction validation has now been relaxed to allow a new kind of transaction, the dust return transaction.
This new transaction type allows donating dust to miners via fees as a new way to counter wallet dusting attacks.
This is more economical for the network because it allows clearing the wallets and UTXO databases from otherwise
practically unspendable outputs, whilst completely removing the incentive to conduct dust attacks at all.
A transaction is considered a dust return transaction if the following conditions are met:
-
The transaction has a single output of zero value (zero amount).
-
The scriptPubKey is as follows:
OP_FALSE OP_RETURN OP_PUSHDATA ‘dust’.
All inputs must be standard inputs or the following node configuration parameter must be set:
-acceptnonstdconsolidationinput=1
The node must also be configured to accept non standard transactions. I.e. following configuration option must be set:
-acceptnonstdtx=1
Note that dust return transactions share two configuration parameters with consolidation transactions:
- -acceptnonstdconsolidationinput (default: 0)
- -minconsolidationfactor (default: 20. Setting consolidation factor to 0 disables consolidation transactions and dust return transactions as well)