[Chapter-delegates] Blockchain and Food Tracability

[Marcel Waldvogel]

There needs to be some form of reversal, typically designed at the
beginning of the process. For example, it might include (in order of
increasing severity):

* Data entry error: An update to the entry by the original creator or a
third party designated by the creator. This should leave the original
entry legible, but just annotate it, similar to PGP Revocation
Certificates or a contra entry. (This should also notify the recipients
of the original entry; so a publish/subscribe system might be a
technological basis.)
* Fraudulent entry: A fix to the data should be possible by an
overseeing body, again with full transparency.
* Illegal entry: Someone has submitted a trade secret, copyrighted
material, or even child porn to the repository. It should be erasable,
again with full transparency.

-Marcel

On Tue, 2018-10-02 at 12:45 -0400, John Levine wrote:
> In article <0accf29eeb5c4b7e9012688532f9a7cdbabc778d.camel at isoc.ch> you write:
> Aren't "responsible for blockchain governance" and "proof-of-work"
> diametral opposites?
> With PoW, the goal is that nobody can exert control on the contents of
> the blockchain [1]. To me, this implies that there is no governing body
> who can "fix things" if they are broken.
> 
> That's true as far as it goes, but a PoW system makes the often
> unrealistic assumption that nobody can control 51% of the miners.
> Given the size of some mining pools and the opacity of many mining
> operations, that strikes me as a major leap of faith.
> 
> You always have to trust someone.  The only question is who.  You will
> find that in the outside world, people want the ability to back out
> bogus transactions, and the few systems that you can't reverse, like
> international bank wires, have horrible fraud and security problems.
> 
> The application to food is fairly obvious: when (not if) someone puts
> in bogus data, who recognizes it and what do you do about it?
> 
> R's,
> John
> 
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://elists.isoc.org/mailman/private/chapter-delegates/attachments/20181002/3d2b505a/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: This is a digitally signed message part
URL: <https://elists.isoc.org/mailman/private/chapter-delegates/attachments/20181002/3d2b505a/attachment.asc>