Bitcoin Forum
May 05, 2024, 09:10:30 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Default tx fee should be changed from 100 to 10 bits!  (Read 3703 times)
Kazimir (OP)
Legendary
*
Offline Offline

Activity: 1176
Merit: 1001



View Profile
July 08, 2014, 02:34:42 PM
 #1

Since Bitcoin Core 0.9, the default transaction fee ('relayfee' in bitcoin.conf) was changed from 0.0001 (or 0.1 milliBTC or 100 bits) to 0.00001 BTC (or 0.01 milliBTC or 10 bits) per kilobyte.

Any chance this can be applied in Bitcoin Wallet for Android too?

One of the advantages of Bitcoin used to be 'almost free' transactions. But with todays currency rates, 0.0001 BTC is 4~5 euro cents, which is (even though it's obviously a small amount of money) still a lot more than consumers pay on regular bank wire transfers. Also, for micropayments (typically less than one euro) or small donations, a 4~5 cent fee is a pretty high percentage.

So, fixing the Android Wallet to use the official Bitcoin Core tx fee would help a lot in convincing people to give Bitcoin a try and put it to use in actual economic traffic!

In theory, there's no difference between theory and practice. In practice, there is.
Insert coin(s): 1KazimirL9MNcnFnoosGrEkmMsbYLxPPob
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
Andreas Schildbach
Moderator
Hero Member
*
Offline Offline

Activity: 483
Merit: 501


View Profile
July 08, 2014, 02:48:01 PM
 #2

We are monitoring transaction fees closely. At the moment it looks like even though lots of nodes relay transactions with a 0.01 mBTC fee per kB, miners don't care. They still require 0.1 mBTC per kB. As a result, transactions will get stuck.

If you want to experiment with fees, feel free to build your own binary from the source.
Kazimir (OP)
Legendary
*
Offline Offline

Activity: 1176
Merit: 1001



View Profile
July 14, 2014, 09:08:17 AM
 #3

At the moment it looks like even though lots of nodes relay transactions with a 0.01 mBTC fee per kB, miners don't care. They still require 0.1 mBTC per kB.
How do you verify this, or where does this conclusion come from? I typically send all my transactions with a 10 bit fee (at least when paying from a wallet that allows custom fees, such as MultiBit or blockchain.info/wallet) and I never ever experienced any problems.

Quote
If you want to experiment with fees, feel free to build your own binary from the source.
I'm pretty unexperienced with Android development, but I'll look into it, thanks.

In theory, there's no difference between theory and practice. In practice, there is.
Insert coin(s): 1KazimirL9MNcnFnoosGrEkmMsbYLxPPob
medUSA
Legendary
*
Offline Offline

Activity: 952
Merit: 1003


--Signature Designs-- http://bit.ly/1Pjbx77


View Profile WWW
July 14, 2014, 10:54:03 AM
 #4

At the moment it looks like even though lots of nodes relay transactions with a 0.01 mBTC fee per kB, miners don't care. They still require 0.1 mBTC per kB.
How do you verify this, or where does this conclusion come from? I typically send all my transactions with a 10 bit fee (at least when paying from a wallet that allows custom fees, such as MultiBit or blockchain.info/wallet) and I never ever experienced any problems.

I have tried sending a 900 byte transaction with 0.00001 fee (which would normally require 0.0001 fee) and it took over 40 hours to confirm. Is this what you mean by "never ever experienced any problems"? How long did yours take?
Kazimir (OP)
Legendary
*
Offline Offline

Activity: 1176
Merit: 1001



View Profile
July 15, 2014, 11:12:41 AM
 #5

I have tried sending a 900 byte transaction with 0.00001 fee (which would normally require 0.0001 fee) and it took over 40 hours to confirm. Is this what you mean by "never ever experienced any problems"? How long did yours take?
Seriously? I'm not sure how large 900 bytes is compared to a regular tx, I always send simple txs from one address to another, using 0.00001 BTC fee. It typically takes 0 or 1 block to confirm (sometimes 2 or 3, rarely 4, never longer).

In theory, there's no difference between theory and practice. In practice, there is.
Insert coin(s): 1KazimirL9MNcnFnoosGrEkmMsbYLxPPob
medUSA
Legendary
*
Offline Offline

Activity: 952
Merit: 1003


--Signature Designs-- http://bit.ly/1Pjbx77


View Profile WWW
July 15, 2014, 11:31:29 AM
 #6

Seriously? I'm not sure how large 900 bytes is compared to a regular tx, I always send simple txs from one address to another, using 0.00001 BTC fee. It typically takes 0 or 1 block to confirm (sometimes 2 or 3, rarely 4, never longer).

Well, a 1 input and 2 outputs (recipient and change address) transaction is about 250 bytes. A transaction with 4 inputs and 1 output is about 900 bytes. I use low maturity coins (have not been idle with 200+ confirmations) and tried sending a 4 to 1 transaction to test the acceptance of 0.00001 fee. I used low maturity coins because I do not want the maturity of coins (priority score) to influence the confirmation time.  It took 40 hours to confirm.

I believe your transaction sent with 0.00001 fee was confirmed quickly because of the maturity (high priority) rather than widespread acceptance of a 0.00001 fee. You probably could have sent it without a fee and it would confirm just as quickly.

Mike Hearn
Legendary
*
Offline Offline

Activity: 1526
Merit: 1129


View Profile
July 15, 2014, 06:33:16 PM
 #7

A better fix would be to teach bitcoinj about priority and start to use fee/prio estimation so it knows when it doesn't have to attach any fee at all. Then some transactions would go back to being free again.
galbros
Legendary
*
Offline Offline

Activity: 1022
Merit: 1000


View Profile
August 25, 2014, 09:37:53 PM
 #8

Would it be hard to give the user an option between 10K and 1K satoshi?  Sometimes I am fairly indifferent for how long it takes a transaction to confirm and others I need to go ASAP.

Thanks for all the work on the Android BTC wallet!
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!