|
kseistrup (OP)
|
 |
March 10, 2011, 07:52:21 PM |
|
Hi,
I'd like to change bitcoind's ‘paytxfee’ value on the fly — i.e., without restarting bitcoind — but I can't seem to find a suitable jsonrpc command…
Anyone?
Cheers,
|
Klaus Alexander Seistrup
|
|
|
|
|
|
|
|
|
|
|
|
Each block is stacked on top of the previous one. Adding another block to the top makes all lower blocks more difficult to remove: there is more "weight" above each block. A transaction in a block 6 blocks deep (6 confirmations) will be very difficult to remove.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
jgarzik
Legendary
 Offline
Activity: 1596
Merit: 1091
|
|
March 10, 2011, 08:18:20 PM |
|
I agree it should be change-able at runtime. Long-running nodes will want to adapt to changing network conditions, without needing to restart bitcoind. Here's a patch: http://yyz.us/bitcoin/patch.bitcoin-settxfeeAny volunteers to test ? |
Jeff Garzik, Bloq CEO, former bitcoin core dev team; opinions are my own.
Visit bloq.com / metronome.io
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
|
|
|
|
kseistrup (OP)
|
|
March 10, 2011, 08:26:27 PM |
|
I agree it should be change-able at runtime. Long-running nodes will want to adapt to changing network conditions, without needing to restart bitcoind.
Exactly! I'll bite!  Cheers, |
Klaus Alexander Seistrup
|
|
|
|
kseistrup (OP)
|
|
March 10, 2011, 08:33:31 PM |
|
So far, so good. I ran “bitcoind settxfee 0.01” from the commandline, and now “btc getinfo” shows “"paytxfee" : 0.01000000”.
Thanks for your help!!
Cheers,
|
Klaus Alexander Seistrup
|
|
|
|
kseistrup (OP)
|
|
March 10, 2011, 08:40:52 PM |
|
Hm, there's something I don't understand. I set txfee to BTC 0.01, then sent jgarzik BTC 0.99, thinking that this would add up to BTC 1.00. However: $ btc getinfo | grep txfee
"paytxfee" : 0.01000000,
$ btc sendtoaddress 17NdbrSGoUotzeGCcMMCqnFkEvLymoou9j 0.99 "settxfee patch" jgarzik
2a59d5910721dd5729d19737f300bf9b953fc55d32e6cd16dabb8bd5885280be
$ btc gettransaction 2a59d5910721dd5729d19737f300bf9b953fc55d32e6cd16dabb8bd5885280be
{
"amount" : -0.99000000,
"fee" : -0.02000000,
"confirmations" : 0,
"txid" : "2a59d5910721dd5729d19737f300bf9b953fc55d32e6cd16dabb8bd5885280be",
"time" : 1299789332,
"comment" : "settxfee patch",
"to" : "jgarzik",
"details" : [
{
"account" : "",
"address" : "17NdbrSGoUotzeGCcMMCqnFkEvLymoou9j",
"category" : "send",
"amount" : -0.99000000,
"fee" : -0.02000000
}
]
}
$
How come the fee ended up being BTC 0.02 instead of 0.01? Cheers, |
Klaus Alexander Seistrup
|
|
|
jgarzik
Legendary
Offline
Activity: 1596
Merit: 1091
|
|
March 10, 2011, 08:52:35 PM |
|
EDIT: nevermind |
Jeff Garzik, Bloq CEO, former bitcoin core dev team; opinions are my own.
Visit bloq.com / metronome.io
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
|
|
|
|
|
|
kseistrup (OP)
|
|
March 10, 2011, 09:07:18 PM |
|
Yeah, it must be. I sent BTC 1.00 to someone else, and that transaction had a fee of BTC 0.01. Cheers, |
Klaus Alexander Seistrup
|
|
|
jgarzik
Legendary
Offline
Activity: 1596
Merit: 1091
|
|
March 10, 2011, 09:29:23 PM |
|
Patch updated, to remove lower bound on TX fee.
|
Jeff Garzik, Bloq CEO, former bitcoin core dev team; opinions are my own.
Visit bloq.com / metronome.io
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
|
|
|
|
