The signing of documents is a classic use case for blockchain, It aims to exit the trust cycle by inheritance from PNG, or also a hierarchical trust chain model.
Seems to be logic, that somehow, blockchain could help to remove that dependency with certificators, and that’s just what we’re going to explain, how the blockchain signature works and how to take advantage from it.
If we Google this topic (sign documents with blockchain), there is an excess of information with hundreds of proposals in several countries.
And of course, we can’t forget the functionality we’re looking for: Remember that the ultimate goal is to validate that a document has been issued by an individual or a company.
This validation may contain associated metadata (expiration, type, confidentiality, etc …), you can always attach information to the sign itself, we do that using a merkel-tree combination, just in the way we did for other blockchain projects.
ok… let’s see how the sign with blockchain works…
To sign documents with blockchain it is important to know what elements are involved in the process:
issuer: is the natural person, who has a digital certificate with which he signs the document
recipient: is the document that will be signed
Basically, an issuer signs a document with his private key and later writes in the blockchain.
But of course … how can we guarantee that the document is the same and has not been changed? … or that particular document is the one that has been signed … the answer is using merkel-tree to validate the data associated with the document.
What can we expect from a sign ecosystem ?
- A site to manage signed documents. (login, listing, signature, shipping … etc …)
- Persist documents at the user’s discretion in an encrypted manner on distributed systems (IPFS)
- Create a specific standard for the firm (this frees us from dependence on the platform) https://certificates.media.mit.edu
- Possibility of validating the attached document a certificate of a document