[Feedback appreciated]: Find a better way to store the signature

[Flajt]

Currently the system stores the signature as metadata with originstamp, however this is not that great, if originstamp would stop operations, it would be impossible to verify the signatures, as we may not be able to access them. A better way to store them is required.

Ideas:

• Embed them in the file, and strip it before calculating the hash (shouldn't be that hard to implement, just need to send the signature down after signing. It would however require adding a versioning metadata filed to check if we need to pull data from originstamp or the file)
• ???

Any thoughts on this matter are appreciated

[Flajt]

Seem like that the signature is available in the provided PDF, which is nice. But I'm still unsure if that is sufficent, since it would only allow the owners to verify it completly.

[Flajt]

Will add used Web3 providers where it has been persisted to as metadata + a version code EDIT: Reason: This will allow modifying the data and how it's saved, paving the way to add features like this.

[Flajt]

See #140