couldn't you just set it with the custom option? what's the point of having that enabled by default?
Because I use RPC commands like sendmany on bitcoind server, that's why I need it set by default.
Topic: Bitcoin server - set minimum transaction fee - page 2. (Read 2814 times)
Because I use RPC commands like sendmany on bitcoind server, that's why I need it set by default.
couldn't you just set it with the custom option? what's the point of having that enabled by default?
UPDATE: I'm talking about the following setting:
Is there any way to enable it by default for the use of sendtoaddress, sendfrom or sendmany on bitcoind?
Is there any way to enable it by default for the use of sendtoaddress, sendfrom or sendmany on bitcoind?
Hello fellows!
I'm actually running bitcoind server to receive and send transaction through my own software.
Transaction size of my spends are always near to 100kb/500kb, so how do I set a minimum/pseudo-fixed transaction fee in my bitcoin.conf/software? If you haven't figured out yet what I mean, I would always pay 0.0001 BTC for each spend cause they never exceed 1.000kb.
Hoping in a fast reply
(SELF MADE) MOMENTANEOUS WORKAROUND:
Are you testing any of these on the Mainnet?
No because I do not have enough bitcoins. However, I've seen many sending with "pseudo-fixed" fees on testnet too.
It's my understanding that testnet does not require any fees. This may be lending to your problem.
Also surely you have enough Bitcoin to test some 0.0001 sending fees. Just send them somewhere and bring them back (such as to Coinbase, etc).
Testnet requires fees too!
Then how do miners mine those bitcoins?
Whatever, I've finally found the parameter: minrelaytxfee =
TX example: http://tbtc.blockr.io/tx/info/90e8519b747117df73cd244d40b26c7ab3e962fbd7b3106bfa9995da85c072e2
(SELF MADE) DEFINITIVE SOLUTION:
You can't, the reference implementation wallet always pays some-amount-per-1000-bytes-of-the-transaction.
The rules for the 0.10 release are:
+ By default, you always pay a fee (this is different from previous releases that would send transactions without a fee if they had high enough priority) (run with -sendfreetransactions=1 to get the old behavior of sending high-priority transactions without a fee)
+ By default, the fee-per-kilobyte is estimated based on recent transaction confirmation history.
To get close to what you want (pay a fixed fee per transaction), run with -paytxfee=0.whatever : that tells the wallet code to pay 0.whatever BTC per 1000 bytes. Most transactions are about 500 bytes big.
See here: http://core2.bitcoincore.org/smartfee/fee_graph.html ... for how high to make -paytxfee=0.whatever based on how long you're willing to wait for the first confirmation (that page graphs estimates from the latest&greatest fee estimation code from Alex Morcos that will hopefully be in the 0.11 Bitcoin Core release).
I'm now having full control of fees through:
Previous method was working fine but when change addresses (inputs) were too much I started spending more than 0.0001 BTC, complete chaos
However now's everything ok with new functions
I'm actually running bitcoind server to receive and send transaction through my own software.
Transaction size of my spends are always near to 100kb/500kb, so how do I set a minimum/pseudo-fixed transaction fee in my bitcoin.conf/software? If you haven't figured out yet what I mean, I would always pay 0.0001 BTC for each spend cause they never exceed 1.000kb.
Hoping in a fast reply
(SELF MADE) MOMENTANEOUS WORKAROUND:
Unfortunately, none of these works. How's that possible? What I'm doing wrong?
Are you testing any of these on the Mainnet?
No because I do not have enough bitcoins. However, I've seen many sending with "pseudo-fixed" fees on testnet too.
It's my understanding that testnet does not require any fees. This may be lending to your problem.
Also surely you have enough Bitcoin to test some 0.0001 sending fees. Just send them somewhere and bring them back (such as to Coinbase, etc).
Testnet requires fees too!
Then how do miners mine those bitcoins?
Whatever, I've finally found the parameter: minrelaytxfee =
TX example: http://tbtc.blockr.io/tx/info/90e8519b747117df73cd244d40b26c7ab3e962fbd7b3106bfa9995da85c072e2
(SELF MADE) DEFINITIVE SOLUTION:
Hello fellows!
I'm actually running bitcoind server to receive and send transaction through my own software.
Transaction size of my spends are always near to 100kb/500kb, so how do I set a minimum/pseudo-fixed transaction fee in my bitcoin.conf/software? If you haven't figured out yet what I mean, I would always pay 0.0001 BTC for each spend cause they never exceed 1.000kb.
Hoping in a fast reply
I'm actually running bitcoind server to receive and send transaction through my own software.
Transaction size of my spends are always near to 100kb/500kb, so how do I set a minimum/pseudo-fixed transaction fee in my bitcoin.conf/software? If you haven't figured out yet what I mean, I would always pay 0.0001 BTC for each spend cause they never exceed 1.000kb.
Hoping in a fast reply
You can't, the reference implementation wallet always pays some-amount-per-1000-bytes-of-the-transaction.
The rules for the 0.10 release are:
+ By default, you always pay a fee (this is different from previous releases that would send transactions without a fee if they had high enough priority) (run with -sendfreetransactions=1 to get the old behavior of sending high-priority transactions without a fee)
+ By default, the fee-per-kilobyte is estimated based on recent transaction confirmation history.
To get close to what you want (pay a fixed fee per transaction), run with -paytxfee=0.whatever : that tells the wallet code to pay 0.whatever BTC per 1000 bytes. Most transactions are about 500 bytes big.
See here: http://core2.bitcoincore.org/smartfee/fee_graph.html ... for how high to make -paytxfee=0.whatever based on how long you're willing to wait for the first confirmation (that page graphs estimates from the latest&greatest fee estimation code from Alex Morcos that will hopefully be in the 0.11 Bitcoin Core release).
I'm now having full control of fees through:
- getbalance
- listunspent
- createrawtransactions
- signrawtransaction
- sendrawtransaction
Previous method was working fine but when change addresses (inputs) were too much I started spending more than 0.0001 BTC, complete chaos
However now's everything ok with new functions
Jump to: