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.
Topic: Received transaction not confirming - 0.25btc bounty for help (Read 1063 times)
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:You can prevent this by changing your configuration and removing the ability to accept incoming connections.
client is up to date on all blocks with 8 active connections.
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.
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.
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.
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.
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.
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.
Is your client directly connected to the sender?
That may explain why you see it whereas it doesn't broadcast.
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
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.
Is your client directly connected to the sender?
That may explain why you see it whereas it doesn't broadcast.
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
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.
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...
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)
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
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
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...
Well that's not good, is it just lost to the ether? or does it eventually return to the owner.
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...
May have been sent without enough fee
is it just a waiting game if theres lack of fee?
May have been sent without enough fee
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
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
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
Jump to: