Preservation of electronic documents
Problem Statement
These contents are translated by Google Translate
Compared to paper documents, electronic documents are more susceptible to falsification and have vulnerabilities that make it difficult to detect falsification after the fact because no trace of falsification remains. Electronic signatures and long-term signatures (time stamps) are used to mitigate these vulnerabilities.
With electronic signatures, the hash value is encrypted with a private key and incorporated into the electronic document. If the private key is leaked, this electronic document will not be safe. In this case, the security of previously signed electronic documents is compromised. Timestamps also use public-key cryptography, so any compromise, vulnerability, or disclosure would render them ineffective.
For this reason, electronic signatures are generally valid for 1 to 3 years, and long-term signatures (time stamps) are 10 years, and if they exceed 10 years, they must be re-signed. If the private key is compromised, the signature will be revoked.
Also, long-term signatures (timestamps) must be signed for each country that you want to certify, because the time stamps recognized by each country differ.
It is practically difficult to apply electronic signatures or long-term signatures (time stamps) to all electronic documents that occur daily. It is common to perform processing for collateral.
Solution Overview
These contents are translated by Google Translate
Record the expiration of the electronic signature, the revocation of the electronic signature due to the leakage of the private key, the hash value of the electronic document, the hash value of the electronic document that has been electronically signed, and the timestamp token (a token generated by long-term signature) This makes it possible to detect tampering even if the electronic signature has been compromised (expired) or the electronic signature has been revoked due to the leakage of the private key.
Why Scalar
These contents are translated by Google Translate
ScalarDL records data on a per-asset basis. When you append data to an asset, the newly recorded data is stored concatenated with the hash value of the previous data, forming a chain of hashes. For this reason, the older the data, the longer the hash chain, the more difficult it is to falsify, and the more it can be compromised. Similarly, even if the private key is leaked, if the past data is changed while new data is accumulated, the entire hash chain must be recalculated and reconstructed, so the leaked private key can be used to restore the past data. has become difficult to rewrite. In addition, if ScalarDL is built with an Auditor configuration, it is very difficult to tamper with the recorded data because it is necessary to tamper with not only the server that recorded the data but also the data on the Auditor side.
Therefore, if you record the hash value of the electronic document, the hash value of the electronic document that has been electronically signed, and the time stamp token (the token generated by the long-term signature), you can use the data as evidence to prove the electronic document. has not been tampered with, and its validity can be proven. Also, since ScalarDL assets can prove order, when a timestamp token is recorded in an asset, the data recorded before it existed before the timestamp token. can also be proved.