Of what will the network be "aware"? Can it determine the passing of time?

[polpolrene]

RFC for timestamping in SAFE

This does not rely on any other input other than the device’s own system clock? (The embedded one that runs on the CMOS battery) Also, there is no verification of this time?

Any time consensus within SAFEnet?

No blockchain, that’s great. Safecoin transactions within a second, just like digital cash with a crypto sign from the last owner. But what about time in the network? Let’s say someone creates some sort of youtube on the network. Everybody can upload movies to this “SAFEtube” but how do we know which movie was uploaded at what time? I think it would be great to know that! And what about a search-engine in the network? It would be great to search all the SAFEsites which where online in 2015 when …

Timestamps or not timestamps

If at all possible, I strongly advocate implementing some kind of “consensus” timestamps to every uploaded file. Someone pointed out that a hash on the bitcoin blockchain could be used for proof of anteriority, but having an optional timestamp might not be good enough. Having timestamps at the network level would be good not only for disputes, but also for the study of history.

Timekeeping idea

This is fully based on @000’s ingenious revelation about timekeeping. A network-wide clock at the expense of 8 extra bytes in the message headers. And another 8 bytes for in-group messages, and the same for our list of close group members. The idea of timekeeping came up multiple times, but it was deemed impossible without having to rely on external references. For most practical purposes*, however, it would be enough to establish the order of events. I believe we may achieve this entirely wi…