Bitcoin ist not catching up after block 1700059 #923

issue krishKM opened this issue on March 10, 2012
  1. krishKM commented at 6:11 PM on March 10, 2012: none

    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

  2. sipa commented at 6:15 PM on March 10, 2012: member

    Which version are you running?

  3. krishKM commented at 6:16 PM on March 10, 2012: none

    0.6.0

  4. luke-jr commented at 6:21 PM on March 10, 2012: member
  5. krishKM commented at 6:23 PM on March 10, 2012: none

    oh.. i have beta version then...

    0.6.0-Beta

  6. gmaxwell commented at 6:40 PM on March 10, 2012: contributor

    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.

  7. krishKM commented at 7:05 PM on March 10, 2012: none

    oh thx.. i could not downgrade as it throwed me some c++ runtime error.. I upgraded to 0.6.2 and its fine.. why i could not continue with the 0.6.0 ?

  8. krishKM closed this on Mar 10, 2012

  9. sipa commented at 7:19 PM on March 10, 2012: member

    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.

  10. krishKM commented at 7:38 PM on March 10, 2012: none

    is there any chances (theoretically), that "bad" people can generate (with luck) a wallet ID as mine and steal my coins?

  11. sipa commented at 7:42 PM on March 10, 2012: member

    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?

  12. krishKM commented at 7:51 PM on March 10, 2012: none

    nope..just thinking if anyone has the chance to steal my 50k coins..

  13. gmaxwell commented at 8:31 PM on March 10, 2012: contributor

    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.

  14. rebroad commented at 4:51 PM on April 6, 2012: contributor

    @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.

  15. gmaxwell commented at 5:00 PM on April 6, 2012: contributor

    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.

  16. suprnurd referenced this in commit 7551d2da26 on Dec 5, 2017
  17. ptschip referenced this in commit b00271f09a on Jan 19, 2018
  18. MarcoFalke locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-17 06:16 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me