Storage: How to update after Int.Max on height #2
Description
The height is currently used to identity the latest version of a document. If by mistake or abused by an Web3 app, how would the user handle updates to their data? Having multiple fields won't make any difference. Perhaps updates should be allowed if the height is equal, but how do we ensure that an older version is not replacing the new one? Which can happen if an node with old data goes online and starts syncing, it might replace newer data.
One idea would be to introduce an "firstObserved" property on the container (which contains the document) which is not a signed property, but that nodes could use to orchestrate ability to perform a double verification of which document is latest.