On Wed, Mar 13, 2013 at 07:28:06PM +0100, Pieter Wuille wrote: > IMHO, the way to go is first get a 0.8.1 out that mimics the old > behaviour - just as a stopgap solution.
Presumably not emulate too precisely, at least if your initial report that the block caused 0.7 to 'get stuck' was correct. A network that has a mix of 0.8.1 nodes (which will reject the block) and 0.7 nodes (which will hang when receiving the block?) would appear to remove the fork risk. Is it obvious that no other serious problems remain in such a network? (Although I note your proposal to patch 0.7 too, so hopefully the network wouldn't remain in that state for very long) roy ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
