Thus spake unknown (unknown@xxxxxxxxx): > On Wed, 30 Jan 2013 15:49:54 -0400 > Mike Perry <mikeperry@xxxxxxxxxxxxxx> wrote: > > > Longer term, I'm interested in having some form (or better: many forms) > > of multipath consensus validation: > > May be that algo is relevant to independed control of consensus data: > https://en.wikipedia.org/wiki/Linked_timestamping > > Any Tor node or some active users can do it potentially. Yeah, an unsigned git repo of hashes + timestamps for each consensus is an easy way to get a well-tested implementation of such a data structure without doing any additional coding. Plus it comes with easy mirroring capabilities, since git is a very common tool these days. I suggested adding signatures to the git repo as a way of authenticating the "newspaper" in that wikipedia page. But yes, technically signatures are not required if you have some other way of authenticating/verifying the head hash of the git repo is the real, current head that everyone sees. The reason you want this hash chain + timestamp history property is for efficient retroactive verification of a large number of consensus hashes. Say for example, to discover if you were ever given a compromised network view upon returning from a visit to a censored location, or similar circumstance. -- Mike Perry
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ tor-talk mailing list tor-talk@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk