Version | Change log |
Bitcoin Portable 30.0 Oct 13, 2025 |
Policy: The maximum number of potentially executed legacy signature operations in a single standard transaction is now limited to 2500. Signature operations in all previous output scripts, in all input scripts, as well as all P2SH redeem scripts (if there are any) are counted toward the limit. The new limit is assumed to not affect any known typically formed standard transactions. The change was done to prepare for a possible BIP54 deployment in the future. (#32521) -datacarriersize is increased to 100,000 by default, which effectively uncaps the limit (as the maximum transaction size limit will be hit first). It can be overridden with -datacarriersize=83 to revert to the limit enforced in previous versions. (#32406) Multiple data carrier (OP_RETURN) outputs in a transaction are now permitted for relay and mining. The -datacarriersize limit applies to the aggregate size of the scriptPubKeys across all such outputs in a transaction, not including the scriptPubKey size itself. (#32406) The minimum block feerate (-blockmintxfee) has been changed to 0.001 satoshi per vB. It can still be changed using the configuration option. This option can be used by miners to set a minimum feerate on packages added to block templates. (#33106) The default minimum relay feerate (-minrelaytxfee) and incremental relay feerate (-incrementalrelayfee) have been changed to 0.1 satoshis per vB. They can still be changed using their respective configuration options, but it is recommended to change both together if you decide to do so. (#33106) Other minimum feerates (e.g. the dust feerate, the minimum returned by the fee estimator, and all feerates used by the wallet) remain unchanged. The mempool minimum feerate still changes in response to high volume. Note that unless these lower defaults are widely adopted across the network, transactions created with lower fee rates are not guaranteed to propagate or confirm. The wallet feerates remain unchanged; -mintxfee must be changed before attempti |
Bitcoin Portable 29.0 Apr 15, 2025 |
P2P and network changes: Transactions of non-witness size 65 bytes and above are now allowed by mempool and relay policy. This is to better reflect the actual afforded protections against CVE-2017-12842 and open up additional use-cases of smaller transaction sizes. (#26265) New RPCs: The scanblocks RPC returns the relevant blockhashes from a set of descriptors by scanning all blockfilters in the given range. It can be used in combination with the getblockheader and rescanblockchain RPCs to achieve fast wallet rescans. Note that this functionality can only be used if a compact block filter index (-blockfilterindex=1) has been constructed by the node. (#23549) Updated RPCs: All JSON-RPC methods accept a new named parameter called args that can contain positional parameter values. This is a convenience to allow some parameter values to be passed by name without having to name every value. The python test framework and bitcoin-cli tool both take advantage of this, so for example: bitcoin-cli -named createwallet wallet_name=mywallet load_on_startup=1 Can now be shortened to: bitcoin-cli -named createwallet mywallet load_on_startup=1 The verifychain RPC will now return false if the checks didn’t fail, but couldn’t be completed at the desired depth and level. This could be due to missing data while pruning, due to an insufficient dbcache or due to the node being shutdown before the call could finish. (#25574) sendrawtransaction has a new, optional argument, maxburnamount with a default value of 0. Any transaction containing an unspendable output with a value greater than maxburnamount will not be submitted. At present, the outputs deemed unspendable are those with scripts that begin with an OP_RETURN code (known as ‘datacarriers’), scripts that exceed the maximum script size, and scripts that contain invalid opcodes. The testmempoolaccept RPC now returns 2 additional results within the “fees” result: “effective-feerate” is the feerate including fees and siz |
Bitcoin Portable 28.0 Oct 5, 2024 |
P2P and network changes: Transactions of non-witness size 65 bytes and above are now allowed by mempool and relay policy. This is to better reflect the actual afforded protections against CVE-2017-12842 and open up additional use-cases of smaller transaction sizes. (#26265) New RPCs: The scanblocks RPC returns the relevant blockhashes from a set of descriptors by scanning all blockfilters in the given range. It can be used in combination with the getblockheader and rescanblockchain RPCs to achieve fast wallet rescans. Note that this functionality can only be used if a compact block filter index (-blockfilterindex=1) has been constructed by the node. (#23549) Updated RPCs: All JSON-RPC methods accept a new named parameter called args that can contain positional parameter values. This is a convenience to allow some parameter values to be passed by name without having to name every value. The python test framework and bitcoin-cli tool both take advantage of this, so for example: bitcoin-cli -named createwallet wallet_name=mywallet load_on_startup=1 Can now be shortened to: bitcoin-cli -named createwallet mywallet load_on_startup=1 The verifychain RPC will now return false if the checks didn’t fail, but couldn’t be completed at the desired depth and level. This could be due to missing data while pruning, due to an insufficient dbcache or due to the node being shutdown before the call could finish. (#25574) sendrawtransaction has a new, optional argument, maxburnamount with a default value of 0. Any transaction containing an unspendable output with a value greater than maxburnamount will not be submitted. At present, the outputs deemed unspendable are those with scripts that begin with an OP_RETURN code (known as ‘datacarriers’), scripts that exceed the maximum script size, and scripts that contain invalid opcodes. The testmempoolaccept RPC now returns 2 additional results within the “fees” result: “effective-feerate” is the feerate including fees and siz |
Total downloads
55
Last month's downloads
1
Last week's downloads
1
... and user access controls to keep sensitive information secure. Overall, Cash Register is a must-have tool for any business ... recommend only the top software solutions, and add Cash Register to your toolbox today. ...
Finance Explorer Portable, developed by Portableapps, is a top-tier personal finance software that is a must-have for anyone looking to manage their finances on the go. This software is a perfect ... and investments. One of the standout features of Finance Explorer Portable is its portability. As the name ...
If you are looking for a reliable cash counting software, Multiicon Cash Counter is the answer. Developed by Multiicon, a ... is ideal for any business that deals with cash frequently. With its intuitive interface, you can count cash with ease and accuracy. The program also allows ...