Bitcoin Forum
May 05, 2024, 12:52:41 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Ways Bitcoin Transactions Fail to Confirm  (Read 1107 times)
ZiggyMarley (OP)
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
March 17, 2014, 06:47:07 PM
 #1

What can cause a bitcoin transaction to fail to confirm?  I know having a transaction fee of 0 can result in miners not being willing to confirm your transaction.  What are some other possible causes?
1714870361
Hero Member
*
Offline Offline

Posts: 1714870361

View Profile Personal Message (Offline)

Ignore
1714870361
Reply with quote  #2

1714870361
Report to moderator
In order to get the maximum amount of activity points possible, you just need to post once per day on average. Skipping days is OK as long as you maintain the average.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714870361
Hero Member
*
Offline Offline

Posts: 1714870361

View Profile Personal Message (Offline)

Ignore
1714870361
Reply with quote  #2

1714870361
Report to moderator
1714870361
Hero Member
*
Offline Offline

Posts: 1714870361

View Profile Personal Message (Offline)

Ignore
1714870361
Reply with quote  #2

1714870361
Report to moderator
1714870361
Hero Member
*
Offline Offline

Posts: 1714870361

View Profile Personal Message (Offline)

Ignore
1714870361
Reply with quote  #2

1714870361
Report to moderator
fendlestick
Hero Member
*****
Offline Offline

Activity: 546
Merit: 500



View Profile
March 17, 2014, 07:28:36 PM
 #2

Closing your wallet to quick after after sending.

20% OFF All Bondage - www.cryptosextoys.com
Affiliates Get 10% - Join
fbueller
Sr. Member
****
Offline Offline

Activity: 412
Merit: 266


View Profile
March 21, 2014, 12:38:21 AM
 #3

I found an interesting one a while ago, I'll try post later with the txid. Basically, I found a still unconfirmed transaction,which was initially broadcast in like 2013, and that blockchain reported was included in many blocks. Very strange.

It turned out that it was broadcast by a very old client, and very few miners still ran that version of bitcoin. but some did,and it occasionally got mined and announced. But, the network rejects these blocks since they contain a now non-standard transaction.


Bitwasp Developer.
yabtcl
Full Member
***
Offline Offline

Activity: 189
Merit: 103



View Profile
March 21, 2014, 02:48:32 AM
 #4

A transaction with an output less than 0.00005430 is also a non standart transaction and this is also an obstacle to your transaction be confirmed

Foxpup
Legendary
*
Offline Offline

Activity: 4354
Merit: 3042


Vile Vixen and Miss Bitcointalk 2021-2023


View Profile
March 21, 2014, 07:46:27 AM
 #5

I found an interesting one a while ago, I'll try post later with the txid. Basically, I found a still unconfirmed transaction,which was initially broadcast in like 2013, and that blockchain reported was included in many blocks. Very strange.

It turned out that it was broadcast by a very old client, and very few miners still ran that version of bitcoin. but some did,and it occasionally got mined and announced. But, the network rejects these blocks since they contain a now non-standard transaction.
TXID or it didn't happen. Blocks containing non-standard transactions are perfectly valid and will not be rejected; they just aren't mined by most miners, so creating non-standard transactions is a bad idea if you don't like waiting a long time for confirmations.

Will pretend to do unspeakable things (while actually eating a taco) for bitcoins: 1K6d1EviQKX3SVKjPYmJGyWBb1avbmCFM4
I am not on the scammers' paradise known as Telegram! Do not believe anyone claiming to be me off-forum without a signed message from the above address! Accept no excuses and make no exceptions!
zaseb
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
March 21, 2014, 03:13:31 PM
 #6

What can cause a bitcoin transaction to fail to confirm?  I know having a transaction fee of 0 can result in miners not being willing to confirm your transaction.  What are some other possible causes?

These are the most common reasons:

Your fee is too low to be included by a miner or too low to be relayed by nodes.

Your client is not properly connected to the network when broadcasting the transaction.

An input your are spending is unconfirmed and will never confirm.

The transaction is too small (less than 5430 satoshi's)
yabtcl
Full Member
***
Offline Offline

Activity: 189
Merit: 103



View Profile
March 21, 2014, 06:09:34 PM
 #7

The transaction is too small (less than 5430 satoshi's)

Actually, the sum of the transaction outputs can be higher than 5430 satoshis, but if one of the outputs has less than 5430 satoshis the transaction will be considered non stardard

byt411
Hero Member
*****
Offline Offline

Activity: 798
Merit: 1000


View Profile
March 21, 2014, 06:43:33 PM
 #8

Also, if you double spend coins, the one quickest to confirm will get confirmed, and the other probably won't.
fbueller
Sr. Member
****
Offline Offline

Activity: 412
Merit: 266


View Profile
March 21, 2014, 11:25:59 PM
 #9

I found an interesting one a while ago, I'll try post later with the txid. Basically, I found a still unconfirmed transaction,which was initially broadcast in like 2013, and that blockchain reported was included in many blocks. Very strange.

It turned out that it was broadcast by a very old client, and very few miners still ran that version of bitcoin. but some did,and it occasionally got mined and announced. But, the network rejects these blocks since they contain a now non-standard transaction.
TXID or it didn't happen. Blocks containing non-standard transactions are perfectly valid and will not be rejected; they just aren't mined by most miners, so creating non-standard transactions is a bad idea if you don't like waiting a long time for confirmations.

From my chat logs I saw it 28th February here: https://blockchain.info/tx/4005d6bea3a93fb72f006d23e2685b85069d270cb57d15f0c057ef2d5e3f78d2 but I guess they've purged their logs for orphaned transactions. It was for a p2sh address, I decoded the redeemscript, which was for a 1-of-1 address. Blockchain said it was unconfirmed, but it had been included in many blocks. Each of them was no longer in the leading chain.

So it looked like the transaction had an invalid signature (in terms of 0.7+ clients, the majority), although it was fine for 0.6+. The small number of people on 0.6 were the only people who could mine it, but the mining power was on 0.7 anyway.

So blockchain was right in saying 'unconfirmed', as although it made it into occasional blocks, they were all orphaned.

Bitwasp Developer.
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!