Farghaly (OP)
Newbie
 Offline
Activity: 38
Merit: 0
|
 |
May 28, 2014, 11:43:01 PM |
|
Quote from Bitcoin Core client version 0.9.0 https://bitcoin.org/en/release/v0.9.0Reject insanely high fees by default in sendrawtransaction What's considered insanely high tx fee ? is there a formula per tx or something ? |
|
|
|
|
|
|
|
|
|
|
|
|
|
"The nature of Bitcoin is such that once version 0.1 was released, the
core design was set in stone for the rest of its lifetime." -- Satoshi
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
DannyHamilton
Legendary
Offline
Activity: 3360
Merit: 4570
|
|
May 29, 2014, 12:01:36 AM |
|
Quote from Bitcoin Core client version 0.9.0 https://bitcoin.org/en/release/v0.9.0Reject insanely high fees by default in sendrawtransaction What's considered insanely high tx fee ? is there a formula per tx or something ? The code checks to see if the fee in the transaction is larger than 10,000 X nMinRelayTxFee. The default setting of nMinRelayTxFee is 10 µBTC, but I believe it can be changed in bitcoin.conf Therefore, with default settings, any transaction with a fee larger than 0.1 BTC will be rejected by sendrawtransaction. (assuming I've got my math correct, the actual setting in the code for nMinRelayTxFee is 1000 satoshis). If you really want to pay a fee larger than 0.1 BTC, I think there's an override parameter you can send along with sendrawtransaction. |
|
|
|
|
|
KaChingCoinDev
|
|
May 30, 2014, 02:37:30 PM |
|
Why is there a limit? I do not see the point of capping it off. If someone wants to pay 1 BTC tx fee, miners will be happy.
|
|
|
|
|
maaku
Legendary
Offline
Activity: 905
Merit: 1011
|
|
May 30, 2014, 03:17:54 PM
Last edit: May 30, 2014, 03:47:53 PM by maaku |
|
It's called a fail-safe design. Because typically when someone provides a >0.1btc transaction fee, it is because they forgot to include a change output, a very, very common mistake. People have lost lots of bitcoin (>200btc in a single transaction!) due to this mistake in earlier versions of bitcoind.
|
I'm an independent developer working on bitcoin-core, making my living off community donations. If you like my work, please consider donating yourself: 13snZ4ZyCzaL7358SmgvHGC9AxskqumNxP |
|
|
|
KaChingCoinDev
|
|
May 30, 2014, 03:33:18 PM |
|
Because typically when someone provides a >0.1btc transaction fee, it is because they forgot to include a change output, a very, very common mistake. It's called a fail-safe design. People have lost lost of bitcoin (>200btc in a single transaction!) due to this mistake.
Ah, okay. Makes more sense. Thanks! |
|
|
|
|
lilfiend
Member
Offline
Activity: 96
Merit: 10
|
|
May 30, 2014, 03:49:06 PM |
|
Because typically when someone provides a >0.1btc transaction fee, it is because they forgot to include a change output, a very, very common mistake. It's called a fail-safe design. People have lost lost of bitcoin (>200btc in a single transaction!) due to this mistake.
While I'd usually say that we should just let them deal with their own stupidity it probably is for the best that a fail-safe like this is put into place. We want bitcoin adoption, not for people to get pissed at bitcoin because they accidentally gave away their coins. |
[Insert E-peen here]
|
|
|
DannyHamilton
Legendary
Offline
Activity: 3360
Merit: 4570
|
|
May 30, 2014, 04:28:16 PM
Last edit: May 30, 2014, 05:47:34 PM by DannyHamilton |
|
Because typically when someone provides a >0.1btc transaction fee, it is because they forgot to include a change output, a very, very common mistake. It's called a fail-safe design. People have lost lost of bitcoin (>200btc in a single transaction!) due to this mistake.
While I'd usually say that we should just let them deal with their own stupidity it probably is for the best that a fail-safe like this is put into place. We want bitcoin adoption, not for people to get pissed at bitcoin because they accidentally gave away their coins. Multiple people all very knowledgeable about bitcoin and raw transactions have made this very mistake for a variety of reasons. As for those who WANT to send a 1 BTC fee, the RPC call allows for an override flag that lets you intentionally send an insanely high transaction fee. The point is, you have to make a conscious decision to intentionally include that flag. |
|
|
|
|
maaku
Legendary
Offline
Activity: 905
Merit: 1011
|
|
May 30, 2014, 05:41:05 PM |
|
it is very important to point out that this is not a protocol rule it is just the user interface asking "are you sure you know what you are doing?"
|
I'm an independent developer working on bitcoin-core, making my living off community donations. If you like my work, please consider donating yourself: 13snZ4ZyCzaL7358SmgvHGC9AxskqumNxP |
|
|
|
|
|
ondratra
|
|
May 31, 2014, 11:13:30 AM |
|
Quote from Bitcoin Core client version 0.9.0 https://bitcoin.org/en/release/v0.9.0Reject insanely high fees by default in sendrawtransaction What's considered insanely high tx fee ? is there a formula per tx or something ? The code checks to see if the fee in the transaction is larger than 10,000 X nMinRelayTxFee. The default setting of nMinRelayTxFee is 10 µBTC, but I believe it can be changed in bitcoin.conf Therefore, with default settings, any transaction with a fee larger than 0.1 BTC will be rejected by sendrawtransaction. (assuming I've got my math correct, the actual setting in the code for nMinRelayTxFee is 1000 satoshis). If you really want to pay a fee larger than 0.1 BTC, I think there's an override parameter you can send along with sendrawtransaction. In originall bitcoind client fee can be set by "settxfee" command. Whole API here https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list . Transactions with fee under nMinRelayTxFee can be rejected by network but usually it just takes longer to process (and even it gets stuck it can be double spended anyway). |
|
|
|
|
|
