Robust timestamps

[bgits]

Having reliable timestamps would be valuable for a wide range of applications. Even accuracy within a range of minutes from time of origination covers a wide range of applications. What research or proof of concepts already exists into how this could be implemented?

[oskarth]

Currently we have receiver timestamp, and there's a WIP to get sender timestamp. See this PR: #417 and discussion here #219

In the future, having block height as a timestamp might be desirable for some applications.

What are more precise requirements and expectations here @bgits? cc @staheri14

[bgits]

There is the open timestamps project which uses blockchain based timestamps. Some use cases are outlined here: https://petertodd.org/2016/opentimestamps-announcement

In use cases like voting for now it's possible to handle requirements using block height and vote specific nonces.

The canonical use case is when chat dialogue is used for discussion in things like dispute resolution, the question of when something was said maybe germane to resolution.

[oskarth]

Generic message follows

I'm going to go ahead and close this discussion as:

1. It is quite old and we are moving away from GH discussions (in favor of either forum.vac.dev or normal issues)

2. Existing discussion has evolved and is captured in more targeted issues already

If you feel like this is in error, please create a thread on Vac forum or a new issue.

---

#430