Bitcoin Forum
May 08, 2024, 11:05:55 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Small Transaction Not Confirming - Force Wallet to Relay?  (Read 1032 times)
fuzzyhair2 (OP)
Newbie
*
Offline Offline

Activity: 6
Merit: 0



View Profile
August 07, 2014, 06:01:48 PM
 #1

Hey guys,

I've sent two fairly small transactions, but they are not confirming.

https://blockchain.info/tx/5f7905e66144bf6e06ce59a83b71d16e415c6859bddd5f0c646b7d78209cee4f
https://blockchain.info/tx/2fd4330ce93de48f78be4cd9426607e12dbd6696b9708edce1305084c0e71fa3

I did send it with a fee, and they are not spam. In fact, I also sent this one which did confirm, for some reason:

https://blockchain.info/tx/8a6bda1f78fab80ae2521b42805afa79df23d2bc9752a26a74e69a058131c59a

So why is it that those two won't confirm for a day but this one did?

I'm thinking of manually relaying the two transactions to Eligius, which does support small transactions. I think it's a matter of other nodes simply not relaying it, as they think it is spam. So how can I manually relay these? When I try to do a raw send in bitcoin-qt, an error comes up: dust
1715209555
Hero Member
*
Offline Offline

Posts: 1715209555

View Profile Personal Message (Offline)

Ignore
1715209555
Reply with quote  #2

1715209555
Report to moderator
Every time a block is mined, a certain amount of BTC (called the subsidy) is created out of thin air and given to the miner. The subsidy halves every four years and will reach 0 in about 130 years.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715209555
Hero Member
*
Offline Offline

Posts: 1715209555

View Profile Personal Message (Offline)

Ignore
1715209555
Reply with quote  #2

1715209555
Report to moderator
1715209555
Hero Member
*
Offline Offline

Posts: 1715209555

View Profile Personal Message (Offline)

Ignore
1715209555
Reply with quote  #2

1715209555
Report to moderator
1715209555
Hero Member
*
Offline Offline

Posts: 1715209555

View Profile Personal Message (Offline)

Ignore
1715209555
Reply with quote  #2

1715209555
Report to moderator
jjc326
Hero Member
*****
Offline Offline

Activity: 700
Merit: 500


View Profile
August 07, 2014, 06:02:55 PM
 #2

I'd had this problem and people in tech support forum were able to help.  Usually the answer was to "just wait longer."  But there is something you can do to your wallet to "re send" I believe.
fuzzyhair2 (OP)
Newbie
*
Offline Offline

Activity: 6
Merit: 0



View Profile
August 07, 2014, 06:19:21 PM
 #3

I try to rebroadcast but the network propogation is 0% with 0 nodes. I manually do it in bitcoin-qt and it says:

64: dust (code -26)

Is there a way to send it to miners who are willing to mine this? I'm sure there are miners out there but the other nodes are just refusing to relay this transaction to them.

Blockchain says: Within 6 Blocks (Medium Priority)
Weed Stuff
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
August 07, 2014, 08:03:04 PM
 #4

Hey guys,

I've sent two fairly small transactions, but they are not confirming.

https://blockchain.info/tx/5f7905e66144bf6e06ce59a83b71d16e415c6859bddd5f0c646b7d78209cee4f
https://blockchain.info/tx/2fd4330ce93de48f78be4cd9426607e12dbd6696b9708edce1305084c0e71fa3

I did send it with a fee, and they are not spam. In fact, I also sent this one which did confirm, for some reason:

https://blockchain.info/tx/8a6bda1f78fab80ae2521b42805afa79df23d2bc9752a26a74e69a058131c59a

So why is it that those two won't confirm for a day but this one did?

I'm thinking of manually relaying the two transactions to Eligius, which does support small transactions. I think it's a matter of other nodes simply not relaying it, as they think it is spam. So how can I manually relay these? When I try to do a raw send in bitcoin-qt, an error comes up: dust
makessure your network work perfectly . i think thats some error on pool .
contact support .
fuzzyhair2 (OP)
Newbie
*
Offline Offline

Activity: 6
Merit: 0



View Profile
August 07, 2014, 08:13:11 PM
 #5

Okay I solved this problem by doing a double spend.

For all future readers:

What I did was export the private keys off of Blockchain and into my own wallet (bitcoin-qt). Then I made a payment to myself. This one got confirmed, which makes the older one a double spend.

After a while, the old ones that never confirmed should disappear.
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!