You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 8, 2020. It is now read-only.
From our recent discussions it turned out that signature time might be crucial for some use cases.
(eg. proving that one have created a file / photo / results before a given time)
What's your opinion on storing this value in the contract?
I know that it's possible to read the signature time now by fetching the events, but having this stored in the contract will make the information available instantaneously for the users, without involving any extraneous, possibly long-lasting requests.
The text was updated successfully, but these errors were encountered:
From our recent discussions it turned out that signature time might be crucial for some use cases.
(eg. proving that one have created a file / photo / results before a given time)
What's your opinion on storing this value in the contract?
I know that it's possible to read the signature time now by fetching the events, but having this stored in the contract will make the information available instantaneously for the users, without involving any extraneous, possibly long-lasting requests.
The text was updated successfully, but these errors were encountered: