Introducing additional features for resilience to bad publishing, or deliberate obfuscation

[timgdavies]

From e-mail feedback:

The concept looks very appropriate, but [the current approach may] assume that “everything is going to be done as anticipated”. That’s true for the ethical side, but not so for those looking to short, omit and/or obscure. You’ll have “cheating” going on that you’ll want the constructs and facilities to trap. Not sure seeing that aspect being addressed here.

The current statement centric model tries to address one side of cheating, by atomising things out into statements which could be published as a ledger (possibly with options for cryptographic signing). But, there are likely quite a lot of adversarial strategies that could be used by actors to provide bad data, or to cause problems for existing data. What do we need to consider? How could these be mitigated?