Topic: Please help test: Bitcoin 0.5.6rc2 and 0.4.7rc2 (FIXES STUCK BLOCK BUG) (Read 2662 times)

People running production services don't need the risk of new bugs, and will run old versions even if they're buggy. Stable branches let these people keep patched against bugs without the huge risk of new ones that comes with bleeding edge. I've been holding back on pointing out that the real cause of this was the huge complexity of BIP16, and that it would have probably not been a problem if we had adopted the simpler BIP17 instead. Nobody writes perfect code, so the risk of bugs in new versions is impossible to avoid.
I am, at least.

This is why I think the so-called "stable" backports are a bad idea. I want people to spend time finding and fixing bugs in 0.6.2, and I want people to realize that the core developers are not supporting older releases.

^^^ Verified

Tried the bitcoind binary out in OSX Lion (10.7.4), seems to work fine.

Regarding the stuck block bug...

Block 177618 was rejected by BIP16-enabled backports (0.4.x and 0.5.x) due to containing a P2SH redemption with over 200 bytes in. Since the BIP16 code uses IsPushOnly to check the scriptSig for compliance, and IsPushOnly in these versions also enforced the 200-byte "is standard" rule, they were effectively treating it as a network rule. This was not a problem in 0.6 because the original OP_EVAL commit (e679ec9) moved the check outside of IsPushOnly.

This problem could have been avoided if either IsPushOnly was renamed when its semantics/behaviour changed significantly, or I inspected the OP_EVAL commit in detail instead of skipping it over as a new feature and not bugfixes. Additionally, it might have helped, if the commit message mentioned the change, but I'd probably have still missed it as it wasn't relevant until months later.

To get unstuck, follow these instructions:
1. Ensure you have the minimum required 1280 MB memory available
2. Create a new file in your bitcoin directory (the same one with wallet.dat) called DB_CONFIG with the following two lines:3. Start bitcoind or Bitcoin-Qt
4. WAIT AT LEAST SIX HOURS; Your client will NOT show any signs of making progress during this time
5. When complete, your client should be up-to-date on block count
6. At this time, you may wish to delete the DB_CONFIG file and restart your client, to use less memory

bitcoind and Bitcoin-Qt version 0.5.6 release candidate 2 (sigs) are now available for download at:

• Mac OS X: bitcoind only
• Windows: installer | zip
• Source: tar.gz

bitcoind version 0.4.7 release candidate 2 (sigs) is now available for download at:

• Windows: installer | zip
• Source: tar.gz

bitcoind and Bitcoin-Qt version 0.6.0.8rc2 is also tagged in git.

These are bugfix-only releases.

Please report bugs by replying to this forum thread. Note that the 0.4.x wxBitcoin GUI client is no longer maintained nor supported. If someone would like to step up to maintain this, they should contact Luke-Jr.

BUG FIXES

• Fix BIP16 validation to not enforce non-standard size limit of 200 bytes. Fixes being stuck at block 177617 (0.4 and 0.5)
• Do not select first address automatically in the address book when sending (Bitcoin-Qt)
• Hopefully final fix for the stuck blockchain issue
• Fix various database crashes and improve error checking
• Properly escape double-quote character in strings when exporting CSV
• Fix #952 by checking if we have a new address or an updated label
• Don't call exit() in Shutdown() for Bitcoin-Qt (fixes a tray-icon issue)
• Filter out whitespace and zero-width non-breaking spaces in Bitcoin address validator
• Properly store source addresses in database
• Remove redundant tooltip on optional transaction fee. Fixes #1218 (Bitcoin-Qt)
• Change initial balance on Overview page from "123.456 BTC" to "0 BTC" to not confuse users, whom might see it before we initialize with the real wallet balance (Bitcoin-Qt)
• Fix various places where Bitcoin-Qt was being shutdown improperly
• Hide UI immediately after leaving the main loop (Bitcoin-Qt)
• Various documentation corrections and debugging fixes

---

Thanks to everybody who contributed code or helped test this release:

Pieter Wuille
Philip Kaufmann
Luke Dashjr
Wladimir J. van der Laan
Matt Corallo
Jeff Garzik
R E Broadley
Fordy
Gavin Andresen
Michael Hendricks
Chris Moore
Christian von Roques
Peter Todd