Quote from: Luke-Jr on March 23, 2013, 07:08:41 PM

Quote from: jl2012 on March 23, 2013, 07:03:40 PM

Quote from: Luke-Jr on March 23, 2013, 06:54:35 PM

Quote from: jl2012 on March 23, 2013, 06:31:06 PM

https://en.bitcoin.it/wiki/BIP_0050

A rule should be something agreed to every nodes.

However, according to BIP0050:

Quote

This would be an issue even if the entire network was running version 0.7.2. It is theoretically possible for one 0.7.2 node to create a block that others are unable to validate, or for 0.7.2 nodes to create block re-orgs that peers cannot validate, because the contents of each node's blkindex.dat database is not identical, and the number of locks required depends on the exact arrangement of the blkindex.dat on disk (locks are acquired per-page).

As there is no consensus even among the same version (unless you can prove the otherwise), this is absolutely a bug, not a rule.

There is indeed a bug in pre-0.8 versions, but part of that bug was also a protocol rule.

Which part is you referring to? Please elaborate. A rule should be something reproducible in every single node of the same version. (e.g. the CHECKMULTISIG bug could be considered as a rule)

"No more than 48xx unique transaction references per block"

The exact number was never identified (a new limit of 4500 was added to be safer), and in some edge cases (due to the bug) could vary, but in no circumstance except a 50% attack would cause a blockchain fork.

To be a rule, you need an exact number like 4823, i.e. a block is accepted by every node if it has 4823 unique tx references, and rejected by every node if it has 4824 unique tx references. Ambiguous limit like 48xx or a varying limit due to a bug is unacceptable.