-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
I think that the course of action is quite simple: 1. Upgrade all the clients to implement the lock limits. (in code, not at the DB exception layer). A bit of research is needed to work out exactly what these limits are so we can maximise the number of transactions. 2. Fix the DB layer, and test that all the clients can support 1MB blocks. 3. Once we are confident that the network supports 1MB blocks, set a date where the lock limits are removed. For me, everyone signed up to bitcoin thinking that there was a 1MB / block limit. The lock limits were unexpected, and could be considered extremely uncontroversial to remove. The discussion of larger blocks (i.e. > 1MB ), that I happen to disagree with, is not relevant to the discussion of the removal of the lock limits. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlFBF0QACgkQBJ8cMDO159aWbwEAs8Ldt8hRpzjS4HdrH3U9Jnaq MWhifXqkJuVC0TVCz3EBAOAfSogdSS7rJvtfV8FqTIox1ek/xJxuHvZdonUnQN1K =I5Cf -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ 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
