大螃嗨

本页面只读。您可以查看源文件，但不能更改它。如果您觉得这是系统错误，请联系管理员。
Dust threshold values
---------------------

The default `minrelaytxfee` was raised from `0.00001` to `0.00005` in Bitcoin Core 0.10.3 as temporary measure against massive memory pool bloat.

The minimum relay fee influences the "dust threshold", and has an impact on the output values of Omni transactions, which are chosen to be as low as possible. As per default, Omni transactions created with Master Core had output values between `0.00000546` BTC and `0.00000882` BTC, whereby the new output values are between `0.0000273` BTC and `0.0000441` BTC.

To continue to create transactions with lower values, start Omni Core with `-minrelaytxfee=0.00001` or add the following to your `bitcoin.conf`:
```
minrelaytxfee=0.00001
```

Lowering the `minrelaytxfee` may result in higher memory consumption, and too low values can result in delayed transaction propagation. A value less than than `0.00001` is generally not recommended.

Transaction fee changes
-----------------------

Starting with Bitcoin Core 0.10, transaction fees, as per default, are no longer hardcoded, but estimated based on previous blocks.

This behavior can result in significantly different fees compared to Master Core 0.0.9, and manual tweaking is recommended, if the default fee estimation doesn't yield satisfying results.

The following fee related configuration options are available:

- `txconfirmtarget=<n>`: create transactions that have enough fees (or priority) so they are likely to begin confirmation within n blocks (default: `6`). This setting is overridden by the `paytxfee` option.
- `paytxfee=<amount>`: fee (in BTC/kB) to add to transactions you send.
- `sendfreetransactions=0|1`: send transactions as zero-fee transactions if possible (default: `0`).

New RPC commands for fee estimation:

- `estimatefee nblocks`: returns approximate fee-per-1,000-bytes needed for a transaction to begin confirmation within nblocks. Returns `-1` if not enough transactions have been observed to compute an estimate.
- `estimatepriority nblocks`: returns approximate priority needed for a zero-fee transaction to begin confirmation within nblocks. Returns `-1` if not enough free transactions have been observed to compute an estimate.

Please note, the fee estimation is not necessarily accurate.