Key design principles
What options and approaches are recommended to address these limitations? How can it be ensured that documents remain immutable and that non-repudiation still applies even when documents are stored off-chain? A fundamental best practice is for applications to capture an immutable document hash, which essentially fingerprints the document, storage location (a URL in a content management system, object store, and suchlike), and related metadata, including the timestamp, user credentials, and version number. This data then becomes a document record, which can be stored on-chain, even as the document itself is stored off-chain. The document record is immutable, and the document hash it contains can be used to verify the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access