Bitcoin Forum
November 23, 2017, 11:37:38 AM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Received transaction not confirming - 0.25btc bounty for help  (Read 963 times)
BTCVanc
Newbie
*
Offline Offline

Activity: 28


View Profile
April 02, 2013, 01:18:15 AM
 #1

First time this has happened,

received a payment of BTC over 4 hours ago and it is not showing up on blockchain.info and has 0/confirmations with no broadcasts:

client is up to date on all blocks with 8 active connections.

any ideas what the issue could be? 0.25btc bounty for any insight that helps.

keep in mind this is a receive not a send. using bitcoin-qt 0.8.0beta

Thanks
1511437058
Hero Member
*
Offline Offline

Posts: 1511437058

View Profile Personal Message (Offline)

Ignore
1511437058
Reply with quote  #2

1511437058
Report to moderator
Join ICO Now A blockchain platform for effective freelancing
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1511437058
Hero Member
*
Offline Offline

Posts: 1511437058

View Profile Personal Message (Offline)

Ignore
1511437058
Reply with quote  #2

1511437058
Report to moderator
1511437058
Hero Member
*
Offline Offline

Posts: 1511437058

View Profile Personal Message (Offline)

Ignore
1511437058
Reply with quote  #2

1511437058
Report to moderator
frga13
Sr. Member
****
Offline Offline

Activity: 384



View Profile
April 02, 2013, 01:30:18 AM
 #2


keep in mind this is a receive not a send. using bitcoin-qt 0.8.0beta

Thanks

isn't 0.8 version broken?

http://bitcoin.org/chainfork.html

jackjack
Legendary
*
Offline Offline

Activity: 1120


May Bitcoin be touched by his Noodly Appendage


View Profile
April 02, 2013, 01:31:50 AM
 #3

May have been sent without enough fee

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
BTCVanc
Newbie
*
Offline Offline

Activity: 28


View Profile
April 02, 2013, 01:32:44 AM
 #4

May have been sent without enough fee


is it just a waiting game if theres lack of fee?

frga13
Sr. Member
****
Offline Offline

Activity: 384



View Profile
April 02, 2013, 01:35:29 AM
 #5

May have been sent without enough fee


is it just a waiting game if theres lack of fee?



If it's just uncomfirmed should be here:
http://blockchain.info/unconfirmed-transactions

But it looks that isn't here...  Undecided

BTCVanc
Newbie
*
Offline Offline

Activity: 28


View Profile
April 02, 2013, 01:43:38 AM
 #6

May have been sent without enough fee


is it just a waiting game if theres lack of fee?



If it's just uncomfirmed should be here:
http://blockchain.info/unconfirmed-transactions

But it looks that isn't here...  Undecided


Well that's not good, is it just lost to the ether? or does it eventually return to the owner.
jackjack
Legendary
*
Offline Offline

Activity: 1120


May Bitcoin be touched by his Noodly Appendage


View Profile
April 02, 2013, 01:45:52 AM
 #7

Is your client directly connected to the sender?
That may explain why you see it whereas it doesn't broadcast.
If it definitely doesn't get included in a block you (and the sender) might want to delete the transaction from your wallet with pywallet

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
frga13
Sr. Member
****
Offline Offline

Activity: 384



View Profile
April 02, 2013, 01:50:05 AM
 #8

May have been sent without enough fee


is it just a waiting game if theres lack of fee?



If it's just uncomfirmed should be here:
http://blockchain.info/unconfirmed-transactions

But it looks that isn't here...  Undecided


Well that's not good, is it just lost to the ether? or does it eventually return to the owner.

True, that's not look good...
I think that could be related with that 0.8 bug, I hope that one of the bitcoin devs can confirm/reject this statement?

Few days ago I have a situation with 0 confirmation. The problem was that tx have no miner fee included, so it's returned to me after 50 hours or so..
But my tx was all the time in Uncorfirmed transaction zone (http://blockchain.info/unconfirmed-transactions)

Stephen Gornick
Legendary
*
Offline Offline

Activity: 2324



View Profile
April 02, 2013, 01:52:56 AM
 #9

Is your client directly connected to the sender?
That may explain why you see it whereas it doesn't broadcast.

I'm wondering if that is starting happen for person-to-person transactions on -OTC.  For example, through IRC without cloaking someone would see your IP address, connect to you and send you a bogus valid transaction (but them make it bogus by broadcasting at the same a double spend to the rest of the network).   You see the transaction, send your money (e.g., Dwolla or whatever) and then that transaction never confirms.

If it definitely doesn't get included in a block you (and the sender) might want to delete the transaction from your wallet with pywallet

If it is an incoming transaction, then simply shutting down and restarting the app will cause it to disappear from the memory pool.

BTCVanc
Newbie
*
Offline Offline

Activity: 28


View Profile
April 02, 2013, 02:00:23 AM
 #10

Is your client directly connected to the sender?
That may explain why you see it whereas it doesn't broadcast.

I'm wondering if that is starting happen for person-to-person transactions on -OTC.  For example, through IRC without cloaking someone would see your IP address, connect to you and send you a bogus valid transaction (but them make it bogus by broadcasting at the same a double spend to the rest of the network).   You see the transaction, send your money (e.g., Dwolla or whatever) and then that transaction never confirms.

If it definitely doesn't get included in a block you (and the sender) might want to delete the transaction from your wallet with pywallet

If it is an incoming transaction, then simply shutting down and restarting the app will cause it to disappear from the memory pool.



Yeah client has been shut down and restarted a few times, pretty scary that it doesn't show in unconfirmed.
deepceleron
Legendary
*
Offline Offline

Activity: 1512



View Profile WWW
April 02, 2013, 02:04:54 AM
 #11

OP removed original transaction info:

tx: 4dd6dd583c9cb82c1f03ccfbd7b7982fbc593af82d3ee1c6243348d97678421c
35BTC
1Hv9Q3Vw6UP6DJNjKBk1DyxLrtr9YQ5jLV

I found this transaction in my logs:
CTxMemPool::accept() : accepted 4dd6dd583c (poolsz 698)

This transaction is not in my memory pool any longer. If you saw the payment immediately pop up in your Bitcoin client while it was running, and it still remains, you may be able to get some details from the tx data in the wallet with the console command:

gettransaction 4dd6dd583c9cb82c1f03ccfbd7b7982fbc593af82d3ee1c6243348d97678421c

You may be able to dump it also, which can be decoded to show the source of the funding:

getrawtransaction 4dd6dd583c9cb82c1f03ccfbd7b7982fbc593af82d3ee1c6243348d97678421c

If it is even wiped from your client upon restart, likely the sender has double-spent the funding inputs, causing it to be wiped from everyone's memory pools as invalid.

BTCVanc
Newbie
*
Offline Offline

Activity: 28


View Profile
April 02, 2013, 02:20:21 AM
 #12

OP removed original transaction info:

tx: 4dd6dd583c9cb82c1f03ccfbd7b7982fbc593af82d3ee1c6243348d97678421c
35BTC
1Hv9Q3Vw6UP6DJNjKBk1DyxLrtr9YQ5jLV

I found this transaction in my logs:
CTxMemPool::accept() : accepted 4dd6dd583c (poolsz 698)

This transaction is not in my memory pool any longer. If you saw the payment immediately pop up in your Bitcoin client while it was running, and it still remains, you may be able to get some details from the tx data in the wallet with the console command:

gettransaction 4dd6dd583c9cb82c1f03ccfbd7b7982fbc593af82d3ee1c6243348d97678421c

You may be able to dump it also, which can be decoded to show the source of the funding:

getrawtransaction 4dd6dd583c9cb82c1f03ccfbd7b7982fbc593af82d3ee1c6243348d97678421c

If it is even wiped from your client upon restart, likely the sender has double-spent the funding inputs, causing it to be wiped from everyone's memory pools as invalid.

hey Deepceleron thanks for the info,

I've done a couple full restarts and it still shows in my Bitcoin-Qt client as Unconfirmed and existing. But does not show anywhere else.
deepceleron
Legendary
*
Offline Offline

Activity: 1512



View Profile WWW
April 02, 2013, 02:32:49 AM
 #13

I've done a couple full restarts and it still shows in my Bitcoin-Qt client as Unconfirmed and existing. But does not show anywhere else.
Please attempt this command:
in Bitcoin: Help -> Debug window -> Console
paste this line:
getrawtransaction 4dd6dd583c9cb82c1f03ccfbd7b7982fbc593af82d3ee1c6243348d97678421c 1

You can paste all the resulting info here (or PM me if you think there is something in there all of us wouldn't already know by being part of the Bitcoin network).

What you are looking for is the lines with
"vin" : [
{
"txid" : "90d5103866b2...75a68bad30380a4a6e8037",
"vout" : 0,


Of course you'll have different strings of letters and numbers.

The vin txid entries are the transactions that are the source of the funds. This is what we are examining - if the previous transaction outputs have already been spent by another transaction besides 4dd6dd583 then you definitely have someone attempting to double spend you and play a game we call "April fools".

If you have a result "No information available about transaction (code -5)" then you no longer have any information about the transaction saved either, it's super-gone.

Stephen Gornick
Legendary
*
Offline Offline

Activity: 2324



View Profile
April 02, 2013, 02:38:45 AM
 #14

I've done a couple full restarts and it still shows in my Bitcoin-Qt client as Unconfirmed and existing. But does not show anywhere else.

Ok, then someone is probably re-connecting to you and re-sending it [edit: Or you are connecting to a peer that is relaying it to you.]

You can prevent this by changing your configuration and removing the ability to accept incoming connections.

deepceleron
Legendary
*
Offline Offline

Activity: 1512



View Profile WWW
April 02, 2013, 02:41:44 AM
 #15

Ok, then someone is probably re-connecting to you and re-sending it. 

You can prevent this by changing your configuration and removing the ability to accept incoming connections.
This is probably the case already, that he's behind unforwarded NAT:

client is up to date on all blocks with 8 active connections.

deepceleron
Legendary
*
Offline Offline

Activity: 1512



View Profile WWW
April 09, 2013, 10:21:16 PM
 #16

So, resolution? Someone scammed the OP?

My new policy: Tech support is free. Tech support with a "bounty" to attract attention needs to be held in escrow before I respond.

Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!