Quote from: gmaxwell on November 14, 2012, 06:43:13 PM

Quote from: grau on November 13, 2012, 05:51:06 AM

since the bitsofproof supernode implements that correctly (otherwise it would not validate the entire chain and testnet3). Let us think about this longer...

Validating the existing chain is _NOT_ proof that it implements it correctly. To be correct all implementations must accept AND reject the same things. Most possible things are not in the chains because, if for no other reason, most possible things are rejected.

Grau, Please confirm that you understand this. It's very important.

I certainly do and I did not state the contrary.

I said more than you quoted. Specifically, I started with:

Quote from: grau on November 13, 2012, 05:51:06 AM

The point is that signature is correct, if it is correct for the hash and public key combination. This is not violated by the code.

Now, that the bitsofproof node validates the production and the test chain lowers the probability that it calculates incorrect hashes for signature checking to a negligible magnitude.