Unconfirmed Bitcoin Problem

Here is my public address: 1BWCNpA3MGYHS3sbbVpGW7jY1Ean1Y3sX4 Does that help?

Why would a wallet report bogus transactions?

No I did not mine it with a laptop. I was part of a mining pool I believe...don't really remember details. I was mining FTC and RPC at the time too, but BTC took so long to mine I never really paid much attention to it.

At first I thought maybe it's the wrong wallet, and my BTC wallet is in a different location, but then when I synced it to Bitcoin Core it showed up with the transactions in the ledger, so I figured it must be the right one. How is it possible that the blockchain would report unconfirmed bogus transactions to me? I did sync the wallet in 2013 and 2014, but I'm not even sure Bitcoin Core existed then. I think it was Bitcoin-Qt or something.

1BWCNpA3MGYHS3sbbVpGW7jY1Ean1Y3sX4

https://blockchain.info/address/1BWCNpA3MGYHS3sbbVpGW7jY1Ean1Y3sX4

there never was any transaction on this address. it is not the right one.
 
If you go to the client console and enter listaddressgroupings do you get additional addresses?

Of course those failed transaction IDs don't show up in a BTC explorer or even a testnet explorer.

You may also want to find the version of bitcoin that was around when you created the original wallet.dat to see if using the new version somehow changes the addresses somehow when using old data. I haven't heard of that happening but it's worth a shot
 
If you go to the client console and enter listaddressgroupings do you get additional addresses?

Of course those failed transaction IDs don't show up in a BTC explorer or even a testnet explorer.

You may also want to find the version of bitcoin that was around when you created the original wallet.dat to see if using the new version somehow changes the addresses somehow when using old data. I haven't heard of that happening but it's worth a shot

No, this is all I get...


11:52:59

listaddressgroupings


11:52:59

[
[
[
"1BWCNpA3MGYHS3sbbVpGW7jY1Ean1Y3sX4",
0.00000000
]
]
]
 
So there is a bug in the blockchain which incorrectly reported these transactions to my wallet? Who do I contact to repair this defect so others aren't affected in the future?

This is my theory of what happened:

You contributed to a mining pool and you were awarded X bitcoins. These bitcoins are sitting in an address that would have paid to your wallet if the tx had gotten confirmed (back in 2013/2014), but it did not. Unless the owners of the mining pool have time-limits on redeeming your bitcoins from the payment address, they're probably still there. So you can get them by one of the two following methods:

- Resubmit the original tx as-is; assuming it has the correct signature on it, the coins will get moved to your wallet when the tx goes through; if the tx fees are too low (quite possible for 2013/2014 era tx's), it may get stuck in the mempool

- Find out the paying address(es) (the inputs to your tx's) and look them up on the blockchain to see if they're still funded. If they are, contact the mining pool and ask them to resubmit the tx from their end, you can show them the tx's you have to show that they paid you back in 2013/2014 you just never received the payment (i.e. you can use the signed tx as a receipt, effectively). Hopefully, they respond and help you out.
 
never seen that before..

of course there are many fringe cases in software. tx malleability which destroyed MtGox was one of them.
 
Hush, you are going to destroy an entire industry.



The resident crypto pumpers don't like talking about posts like OP's, which can be found all over the net. Tons of reports of coins disappearing/stolen, funny business on exchanges where data like stops was manually changed by the exchange itself, the Tether "question" about whether bitfinex is creating the appearance of dollars entering the market when it's not...and more.

Sorry OP. I'll be shocked if your half a coin is "found". The exchange founder's yacht ain't gonna pay for itself, ya know.
 
Oh, I'm not asking you to paste it here. And, no, the tx does not expose the private key, by design (otherwise, you would be giving away your private key to the peer nodes when you broadcast the transaction). Good on you for not assuming, however. Here's a link describing the tx format. I recommend extracting the inputs from the tx using Core commands. This way, you're not trying to manually monkey around with the bytes. You can safely post the addresses of the inputs because an address is just a public record index in the blockchain that is associated with an unspent output. Once you've confirmed whether the inputs are still funded, then it's a matter of trying to resubmit the transaction.

To check any address or transaction ID for yourself, just go to blockexplorer, copy-paste it in and then press enter.

Addresses, block numbers and transaction ID's are always 100% safe to show to others. You should exercise care with public keys - while they will not compromise your funds if they are exposed, exposing them is equivalent to address-reuse which is discouraged on the basis of long-term security considerations. Of course, showing your private keys is equivalent to giving away cash, so take utmost care with them ... just avoid handling them as much as possible beyond the minimum required to make sure you control your funds and have proper backups, etc. And, yes, you have to specifically export your private key in order to expose it (please don't do this, even locally). This is why this usage is discouraged. Instead, people are encouraged to "sweep" private keys, which just submits a transaction moving your old coins to a new address with a fresh private key.

When you have some spare time, consider reading over this amazing blog post to demystify the mechanics of Bitcoin transactions. Even if you're not a techie, just skim over it to get an idea of what's involved. Think of it kind of like looking under the hood of a running car ... even if you don't understand all the whirling gears & levers, you still get a feel for what's going on inside the vehicle.

If you decide to re-broadcast the transaction, you can use this page unless you have Core, then there's probably a way to do it from there.

Hope you get your coins back!

If you decide to re-broadcast the transaction, you can use this page unless you have Core, then there's probably a way to do it from there.

Hope you get your coins back!

When I try to rebroadcast the raw transaction I get this...

Missing parents for c16587ae806c2392635a20843a78f8f6a1275c6990a797f8266e3b9d8a29bd1e while inserting: [c677f8172824b4bb761f0ce51e23235f4a6613c62e74e847936f95440fae6b6c]

If I decode it I get this...

{
"lock_time":0,
"size":225,
"inputs":[
{
"prev_out":{
"index":0,
"hash":"c677f8172824b4bb761f0ce51e23235f4a6613c62e74e847936f95440fae6b6c"
},
"script":"47304402204f1602b609027990a8e17355bdb9d967882aed3ac85e06c9311d33a3228ba9d90220097941a24457d36508f8d17e94400184c849f44c48296aab09e4deb9d23e4e2f012103db4cc04dac3ee0cb4ab0afc108eb1f398ab659be127240a672b1abe139f84b60"
}
],
"version":1,
"vin_sz":1,
"hash":"c16587ae806c2392635a20843a78f8f6a1275c6990a797f8266e3b9d8a29bd1e",
"vout_sz":2,
"out":[
{
"script_string":"OP_DUP OP_HASH160 7336d1277adaf305dddde5cedc686bb1e4988bda OP_EQUALVERIFY OP_CHECKSIG",
"address":"1BWCNpA3MGYHS3sbbVpGW7jY1Ean1Y3sX4",
"value":10630472,
"script":"76a9147336d1277adaf305dddde5cedc686bb1e4988bda88ac"
},
{
"script_string":"OP_DUP OP_HASH160 95a28eec6c32896699df4ca36c880d7e42e504c5 OP_EQUALVERIFY OP_CHECKSIG",
"address":"1EeCRLCksdBRJ7SUkAAFKk1TssVv62hoTQ",
"value":89379528,
"script":"76a91495a28eec6c32896699df4ca36c880d7e42e504c588ac"
}
]
}


Does this offer any more clues?

This is the raw transaction in Hex...

01000000016c6bae0f44956f9347e8742ec613664a5f23231ee50c1f76bbb4242817f877c6000000006a47304402204f1602b609027990a8e17355bdb9d967882aed3ac85e06c9311d33a3228ba9d90220097941a24457d36508f8d17e94400184c849f44c48296aab09e4deb9d23e4e2f012103db4cc04dac3ee0cb4ab0afc108eb1f398ab659be127240a672b1abe139f84b60ffffffff024835a200000000001976a9147336d1277adaf305dddde5cedc686bb1e4988bda88acc8d25305000000001976a91495a28eec6c32896699df4ca36c880d7e42e504c588ac00000000
 
I also did a -reindex and that didn't work either.

No idea...

Never encountered your situation or even seen anyone else with the problem.

The only way that could have happened though, is if the transaction was dumped from the mempool before it was mined, or it was malformed somehow and rejected, but I'd assume it'd show as rejected in that case.

You'd have to ask someone more knowledgeable, like a bitcoin developer.

My guess it was dumped from the mempool, and wasn't retransmitted, but that's just a guess.

Can you log onto the mining pool you used and see what it says. Maybe you'll get lucky or something, or show them, and they can send you a new transaction.
 
Just posted on reddit to see if I can get any help there. Price has gone vertical since I started this thread. I would really like to get my money out before the bubble bursts.
 
Just posted on reddit to see if I can get any help there. Price has gone vertical since I started this thread. I would really like to get my money out before the bubble bursts.


Uhh, you're not really not going to sell all of it, are you?
 
Uhh, you're not really not going to sell all of it, are you?

Haven't really thought that far ahead yet. I have other cryptocurrencies. First I would just like to prove that I can get some of it out of my wallet. Then I'll figure out what to do from there. Whether that's dollar-cost-averaging, or liquidation, I don't know.
 
BTW, I was able to unlock this wallet using an old password in an attempt to send coins, but it still reports the balance as zero. If this was an empty shell wallet that was never used I doubt I could get my password to work on it. There is a reason why the blockchain is reporting these transactions into my wallet.
 
Back
Top