Changeset View
Changeset View
Standalone View
Standalone View
doc/release-notes.md
Show All 26 Lines | - Error codes have been updated to be more accurate for the following error cases: | ||||
the transaction. Previously returned RPC_INTERNAL_ERROR. | the transaction. Previously returned RPC_INTERNAL_ERROR. | ||||
- `removeprunedfunds` now returns RPC_INVALID_PARAMETER if the transaction does not | - `removeprunedfunds` now returns RPC_INVALID_PARAMETER if the transaction does not | ||||
exist in the wallet. Previously returned RPC_INTERNAL_ERROR. | exist in the wallet. Previously returned RPC_INTERNAL_ERROR. | ||||
- `fundrawtransaction` now returns RPC_INVALID_ADDRESS_OR_KEY if an invalid change | - `fundrawtransaction` now returns RPC_INVALID_ADDRESS_OR_KEY if an invalid change | ||||
address is provided. Previously returned RPC_INVALID_PARAMETER. | address is provided. Previously returned RPC_INVALID_PARAMETER. | ||||
- `fundrawtransaction` now returns RPC_WALLET_ERROR if bitcoind is unable to create | - `fundrawtransaction` now returns RPC_WALLET_ERROR if bitcoind is unable to create | ||||
the transaction. The error message provides further details. Previously returned | the transaction. The error message provides further details. Previously returned | ||||
RPC_INTERNAL_ERROR. | RPC_INTERNAL_ERROR. | ||||
- The `gettxoutsetinfo` response now contains `disk_size` and `bogosize` instead of | |||||
`bytes_serialized`. The first is a more accurate estimate of actual disk usage, but | |||||
is not deterministic. The second is unrelated to disk usage, but is a | |||||
database-independent metric of UTXO set size: it counts every UTXO entry as 50 + the | |||||
length of its scriptPubKey. | |||||
Reserve block space for high priority transactions (D485) | Reserve block space for high priority transactions (D485) | ||||
--------------------------------------------------------- | --------------------------------------------------------- | ||||
By default reserve 5% of the max generated block size parameter to hiprio transactions. | By default reserve 5% of the max generated block size parameter to hiprio transactions. | ||||
Hence a `bitcoind` instance running with an unmodified configuration will reserve 100K | Hence a `bitcoind` instance running with an unmodified configuration will reserve 100K | ||||
for high priority transactions. The parameter name used for this configuration | for high priority transactions. The parameter name used for this configuration | ||||
`blockprioritypercentage`. While introducing this new parameter we deprecated | `blockprioritypercentage`. While introducing this new parameter we deprecated | ||||
`blockprioritysize`(it was used to specify the amount of high prio reserved area in byte). | `blockprioritysize`(it was used to specify the amount of high prio reserved area in byte). | ||||
A transaction is considered high priority if its priority is higher than this threshold: `COIN * 144 / 250`, | A transaction is considered high priority if its priority is higher than this threshold: `COIN * 144 / 250`, | ||||
where COIN is the value of a one bitcoin UTXO expressed in satoshis. Thus a transaction | where COIN is the value of a one bitcoin UTXO expressed in satoshis. Thus a transaction | ||||
who as an input of 1 bitcoin and are 144 blocks old and whose size is 250 bytes is considered | who as an input of 1 bitcoin and are 144 blocks old and whose size is 250 bytes is considered | ||||
the priority cut-off. | the priority cut-off. |