By default, all versions of a data item are retained. Previous versions of a data item can be superseded, but original versions are never destroyed.
Selected versions of the database are hashed upon the blockchain. These versions can be proven to have been created at the specified time and can be proven to have been unaltered.
The state of a database at any point in time can be retrieved.
The complete history of any item can be retrieved, showing its initial contents, and the changes made to the document at each point in time.
Developing Blockchain applications is time-consuming and error-prone because familiar and well-established database development idioms are not available.
ProvenDB layers on top of a standard database engine adding core Blockchain characteristics to the database. The resulting database respects all usual database “CRUD” operations (Create-Read-Update-Delete) but also provides Immutability, Tamper Dection, Point-in-time History, and Data Provenance.play video
ProvenDB can prove multiple documents with a single hash using a Merkle tree. We don’t need a whole tree to prove an individual document that is included in the final hash - we only need the “Merkle path.” Thousands of documents can be included in a single Merkle tree - all anchored to a single Blockchain transaction.Login Sign up for free
ProvenDB can be employed for a wide variety of use cases including but not limited to: