Changes between Initial Version and Version 1 of Ticket #18967, comment 4


Ignore:
Timestamp:
May 19, 2016, 7:00:26 AM (4 years ago)
Author:
virgil
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18967, comment 4

    initial v1  
    33Not to say that's impossible, but that's a huge constraint.
    44
    5 Another solution would be that the UUID is a function of the last $k$ consensuses.  And for an Onionoo server to update the family, it must have the a k-length sequence of consecutive consensuses.
     5Even if you require a complete record going back `k` steps, you're going to lose any persistence going back `>k` steps.  Instead of accepting that the Onionoo server will have gaps in its consensus history, wouldn't it be better simply to put them on a blockchain of some sort?