-
Notifications
You must be signed in to change notification settings - Fork 36.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bitcoin ist not catching up after block 1700059 #923
Comments
Which version are you running? |
0.6.0 |
0.6.0 isn't released yet. https://bitcointalk.org/index.php?topic=63165.msg788945#msg788945 |
oh.. i have beta version then... 0.6.0-Beta |
You have 0.6.0rc1. Upgrade to 0.6.0rc2. http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/ or downgrade to 0.5.2. |
oh thx.. i could not downgrade as it throwed me some c++ runtime error.. I upgraded to 0.6.2 and its fine.. |
0.6.0 and 0.6.2 do not exist. You have been using a pre-release of 0.6.0 (the release candidate 1, rc1), which enabled BIP16 as of march 1st. BIP16 was however delayed until april first. This was incorporated in the second pre-release of 0.6.0 (rc2). Someone mined a fake BIP16 transaction, which your 0.6.0rc1 crlient didn't accept, but was valid, as BIP16 was not yet enabled. |
is there any chances (theoretically), that "bad" people can generate (with luck) a wallet ID as mine and steal my coins? |
theoretically, yes. in practice, if all people in the world would generate as many private keys per second as the total number of hash calculations the entire bitcoin network did in its entire history, it would take longer than the age of the universe before any reasonable chance for a double will appear. Also, what does this have to do with this issue? |
nope..just thinking if anyone has the chance to steal my 50k coins.. |
Er. Trying to be tactful here— If you really have 50k BTC and are only now getting around to asking questions about this kind of exposure, I'd strongly recommend you diversify your assets by selling that Bitcoin now. Bitcoin is relatively new and risky technology. If you don't have the time or background to keep up with it and understand it deeply you should probably limit your exposure. In any case, I'm glad your issue was resolved. Cheers. |
@krishKM I'd not recommend selling your bitcoins. I think I understood your question to mean "could someone have stolen my bitcoins as a result of continuing to use 0.6.0rc1", right? The answer is practically, no, as sipa implied but didn't expressly state. Even had there been a fork that your client followed, it wouldn't have been the main fork, and even if you'd spend your coins on that fork, they would still exist on the main fork. If anything, you'd have ended up with 50k coins on both forks, and could have double spent them had anyone else continued following and mining that other fork (which they didn't). I think I'm right in this conclusion. Hopefully someone will correct me if I'm not. |
Right. Receiving while on a fork is the only dangerous operation— because transactions you thought were confirmed may turn out to not be confirmed on the real chain (and there may be conflicting transactions confirmed in their place, making it impossible for them to ever confirm there). Sending, holding, etc. all safe. |
Backport prevector fixes
Use a set for keeping track socket handles and some formatting changes
Hi there,
since two days Bitcoin is not catching up with current block. I have deleted the whole folder and downloaded the block chain again. still same issue.. Am I missing anything??
thx in advance
The text was updated successfully, but these errors were encountered: