dscotese (OP)
|
|
March 12, 2013, 03:39:57 AM |
|
...and did they switch from .8 to .7 during the fork?
|
|
|
|
dscotese (OP)
|
|
March 12, 2013, 03:43:57 AM |
|
Maybe not a good question. The list of blocks shows which are in the "real" chain and which are in the fork.
|
|
|
|
piuk
|
|
March 12, 2013, 04:18:45 PM Last edit: March 12, 2013, 05:30:15 PM by piuk |
|
Blockchain uses a 0.7 based client so it was on "stuck" on 0.7 chain to begin with. But I altered bitcoind to accept the 0.8 blocks about an hour after so it switched to the 0.8 chain for a while, then back to 0.7 when it caught up.
|
|
|
|
btctrada
Newbie
Offline
Activity: 48
Merit: 0
|
|
March 12, 2013, 05:17:27 PM |
|
Hey Ben
Is there an issue with transactions not confirming? They were confirmed prior to the fork, but after the recent transactions are showing unconfirmed? Anyone else?
|
|
|
|
piuk
|
|
March 12, 2013, 05:29:55 PM |
|
Hey Ben
Is there an issue with transactions not confirming? They were confirmed prior to the fork, but after the recent transactions are showing unconfirmed? Anyone else?
If the transaction was confirmed in the now orphaned 0.8 chain it should go back into the memory pool and be included in the 0.7 chain again eventually. If you let me know the tx hash I can take a closer look.
|
|
|
|
BTCdude007
|
|
March 12, 2013, 05:31:41 PM |
|
Same here. Two transactions that were showing many confirmations more than 12 hours ago are now unconfirmed.
One of them shows "Included In Blocks 225444 (2013-03-12 01:07:00 +21 minutes) ". That block must have been on the 0.8 blockchain.
|
|
|
|
piuk
|
|
March 12, 2013, 05:41:15 PM |
|
Need the tx hashes.
|
|
|
|
btctrada
Newbie
Offline
Activity: 48
Merit: 0
|
|
March 12, 2013, 05:42:17 PM |
|
Hey Ben
Is there an issue with transactions not confirming? They were confirmed prior to the fork, but after the recent transactions are showing unconfirmed? Anyone else?
If the transaction was confirmed in the now orphaned 0.8 chain it should go back into the memory pool and be included in the 0.7 chain again eventually. If you let me know the tx hash I can take a closer look. Cheers Ben All these addresses have been affected. 12U63dueaNH1ANWLe2XWF6uUqNnstyNi6c 138bqSSnWz23fNHe6qUHRz8LfieqVmvkYr 149PQjaoTXLBkcX5wczcs947zcUbgTUdxp Second problem my total prior was 490+btc now it is .45+? And strangely the total will increase at random intervals , but when I attempt to withdraw it gives me an error message "insufficient funds" I have a screen shot if that helps? Thanks again... ]
|
|
|
|
BTCdude007
|
|
March 12, 2013, 05:44:48 PM |
|
Check this one:
a691ec7271c69f1d387296778c3928bb6cb07f75cc7054ae3eff048a08cdce10
|
|
|
|
piuk
|
|
March 12, 2013, 06:05:52 PM |
|
Check this one:
a691ec7271c69f1d387296778c3928bb6cb07f75cc7054ae3eff048a08cdce10
I can't see any reason why that transaction wouldn't confirm. I suspect during the whole forking crisis a lot of miners nodes were restarted causing them to drop all transactions in their memory pools so perhaps it just needs rebroadcasting (which I have done now).
|
|
|
|
btctrada
Newbie
Offline
Activity: 48
Merit: 0
|
|
March 13, 2013, 01:43:39 AM |
|
Hey Ben any joy getting my problems fixed? I still have the majority of transactions unconfirmed and the coin total is still .4?
|
|
|
|
piuk
|
|
March 13, 2013, 02:57:44 AM |
|
Hey Ben any joy getting my problems fixed? I still have the majority of transactions unconfirmed and the coin total is still .4?
Other than rebroadcast the transaction again there isn't any blockchain can do to speed up confirmations. I am not sure why they are not confirming. I may have something to do with mining pools deprioritizing staoshidice transactions.
|
|
|
|
btctrada
Newbie
Offline
Activity: 48
Merit: 0
|
|
March 13, 2013, 03:33:01 AM |
|
Hey Ben
Is there an issue with transactions not confirming? They were confirmed prior to the fork, but after the recent transactions are showing unconfirmed? Anyone else?
If the transaction was confirmed in the now orphaned 0.8 chain it should go back into the memory pool and be included in the 0.7 chain again eventually. If you let me know the tx hash I can take a closer look. Cheers Ben All these addresses have been affected. 12U63dueaNH1ANWLe2XWF6uUqNnstyNi6c 138bqSSnWz23fNHe6qUHRz8LfieqVmvkYr 149PQjaoTXLBkcX5wczcs947zcUbgTUdxp Second problem my total prior was 490+btc now it is .45+? And strangely the total will increase at random intervals , but when I attempt to withdraw it gives me an error message "insufficient funds" I have a screen shot if that helps? Thanks again... Cheers How about the second issue? Or will it sort itself?
|
|
|
|
dscotese (OP)
|
|
March 13, 2013, 05:43:45 AM |
|
Second problem my total prior was 490+btc now it is .45+? And strangely the total will increase at random intervals , but when I attempt to withdraw it gives me an error message "insufficient funds" I have a screen shot if that helps?
Thanks again...
Cheers How about the second issue? Or will it sort itself? I think that you need to shutdown your client and then run bitcoind -rescan. The rescan tells it to look for all transactions involving your wallet addresses starting at block 1 - all transactions, that is, that in the MAIN chain. And that changed last night, which is probably why your client doesn't have the correct balances. 450 btc seems like a lot though, so I'm not sure. It's worth a try. On my laptop, the rescan took about 5 minutes. Once it's done, you can restart your client.
|
|
|
|
btctrada
Newbie
Offline
Activity: 48
Merit: 0
|
|
March 13, 2013, 09:00:43 AM |
|
Second problem my total prior was 490+btc now it is .45+? And strangely the total will increase at random intervals , but when I attempt to withdraw it gives me an error message "insufficient funds" I have a screen shot if that helps?
Thanks again...
Cheers How about the second issue? Or will it sort itself? I think that you need to shutdown your client and then run bitcoind -rescan. The rescan tells it to look for all transactions involving your wallet addresses starting at block 1 - all transactions, that is, that in the MAIN chain. And that changed last night, which is probably why your client doesn't have the correct balances. 450 btc seems like a lot though, so I'm not sure. It's worth a try. On my laptop, the rescan took about 5 minutes. Once it's done, you can restart your client. Cheers mate Will give it a go and report (hopefully successful) back.
|
|
|
|
btctrada
Newbie
Offline
Activity: 48
Merit: 0
|
|
March 13, 2013, 05:05:41 PM |
|
Still no Joy Sent a support email...
|
|
|
|
|