Who needs it?
Those who need to prove that a database they manage has not been tempered with. This additional layer of data signatures is an efficient and transparent way of ensuring data immutability; it results in greater trust of all your stakeholders.
Some databases store sensitive or payment-related data. For this reason, they should not be changed through time, but be immutable once they are created. But how to enable all the stakeholders to see for themselves that the records have remained intact? The database manager can periodically take a snapshot of the database or that of a part of the (recent) transactions and store a cryptographic signature on a public or consortium blockchain where all the stakeholders have access to and view these signatures.
What it does?
Our software takes regular snapshots of the database or its recent transactions, creating a cryptographic signature of this data. By exporting and storing this data on a public or consortium blockchain, a database manager transparently shares this information with all the stakeholders through blockchain viewers (block explorers). In this way, any unauthorized change of the past database records would be clearly visible and provable; a change of data would not produce the same cryptographic signature of the snapshot as originally stored on a blockchain.