Quote from: monsterer on September 04, 2015, 08:35:22 AM

Quote from: Fuserleer on September 04, 2015, 08:25:33 AM

Endorsement information is included in transaction data, which is signed by the transaction creator. They are not malleable in any way.

Malleability isn't the problem - if I am a node which is syncing with the network and I'm presented with two different forks of the chain, how do I select between them?

Aren't we just going full circle again here? Huh

The endorsements guard against forks, because future transactions reference them so as to confirm.

If someone changes some/all the endorsements in a copy of the ledger (its not a chain), in an attempt to present a "fork", those modified transactions wont validate because the hashes of the transactions will not verify against the signature.

The "fork" is junk, because no one can validate it, the ledgers of nodes trying to sync to it wont add a single transaction from it, so there is no choice to make.

A fork is only possible if you can change history, which is what you are suggesting here. However, ledger history can not be changed due to the deterministic nature of who gets to vote, and the difficulty in modifying past endorsements which govern that.