Bitcoin Forum
April 25, 2024, 11:11:01 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Normal big-enough transaction with 0 fee is not confirmed for hours  (Read 672 times)
oleganza (OP)
Full Member
***
Offline Offline

Activity: 200
Merit: 104


Software design and user experience.


View Profile WWW
April 03, 2013, 05:45:28 PM
 #1

Interesting. I have a transaction that sends around 0.1 BTC from a single 0.4 BTC output that was confirmed >100 blocks before. It is not included in any block for 7 hours already. I've been sending similar transactions with zero fees before from the same blockchain.info iPhone app and it was always confirmed quickly enough. What could be the reason for the problem? Is it just the mining fee that is suddenly required, or we are hitting block size limit, or one of the addresses could be banned? (Destination addresses are a new one, not SatoshiDice, and the same my address for the change.)

Bitcoin analytics: blog.oleganza.com / 1TipsuQ7CSqfQsjA9KU5jarSB1AnrVLLo
1714043461
Hero Member
*
Offline Offline

Posts: 1714043461

View Profile Personal Message (Offline)

Ignore
1714043461
Reply with quote  #2

1714043461
Report to moderator
1714043461
Hero Member
*
Offline Offline

Posts: 1714043461

View Profile Personal Message (Offline)

Ignore
1714043461
Reply with quote  #2

1714043461
Report to moderator
1714043461
Hero Member
*
Offline Offline

Posts: 1714043461

View Profile Personal Message (Offline)

Ignore
1714043461
Reply with quote  #2

1714043461
Report to moderator
"If you don't want people to know you're a scumbag then don't be a scumbag." -- margaritahuyan
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714043461
Hero Member
*
Offline Offline

Posts: 1714043461

View Profile Personal Message (Offline)

Ignore
1714043461
Reply with quote  #2

1714043461
Report to moderator
1714043461
Hero Member
*
Offline Offline

Posts: 1714043461

View Profile Personal Message (Offline)

Ignore
1714043461
Reply with quote  #2

1714043461
Report to moderator
1714043461
Hero Member
*
Offline Offline

Posts: 1714043461

View Profile Personal Message (Offline)

Ignore
1714043461
Reply with quote  #2

1714043461
Report to moderator
SomeWhere
Member
**
Offline Offline

Activity: 71
Merit: 10


View Profile
April 03, 2013, 05:48:14 PM
 #2

It took 10 hours for a 1.5 BTC transaction of mine to be confirmed once without fees. It's variance. It can take a really long time depending on luck pretty much.
deepceleron
Legendary
*
Offline Offline

Activity: 1512
Merit: 1025



View Profile WWW
April 03, 2013, 05:56:00 PM
 #3

A transaction sending 0.4 BTC with 100 confirmations is not high enough priority to send with no fee.

priority = sum(input_value_in_base_units * input_age)/size_in_bytes

((0.4 * 100,000,000) * 100) / 258 = 15,503,875

Transactions need to have a priority above 57,600,000 to avoid the enforced limit. I would recommend ANY payment include a fee even if it would qualify to be free, as "free transaction" space in blocks is limited, and profit-motivated miners have no incentive to include free transactions over those with fees.
oleganza (OP)
Full Member
***
Offline Offline

Activity: 200
Merit: 104


Software design and user experience.


View Profile WWW
April 03, 2013, 06:15:47 PM
 #4

A transaction sending 0.4 BTC with 100 confirmations is not high enough priority to send with no fee.

priority = sum(input_value_in_base_units * input_age)/size_in_bytes

((0.4 * 100,000,000) * 100) / 258 = 15,503,875

Transactions need to have a priority above 57,600,000 to avoid the enforced limit. I would recommend ANY payment include a fee even if it would qualify to be free, as "free transaction" space in blocks is limited, and profit-motivated miners have no incentive to include free transactions over those with fees.

Thanks for the details. I'll check the source code.

Bitcoin analytics: blog.oleganza.com / 1TipsuQ7CSqfQsjA9KU5jarSB1AnrVLLo
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!