# US 2019/0356493 A1 · Blockchain-anchored smart documents > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2019/0356493 A1 - Document ID: US20190356493A1 - Status: Published application - Kind: A1 - Application number: 16/417,698 - Filed: 2019-05-21 - Published: 2019-11-21 - Earliest claimed: 2018-05-21 - Assignees: Integra, Inc. - Applicants: Integra, Inc. - Inventors: David A. Fisher; David O. Berger; Jay D. Hull - Web page: https://patentgrep.com/patent/US20190356493A1 ## CPC - H04L 9/3247: {involving digital signatures} - H04L 63/123: {received data contents, e.g. message integrity} - G06F 16/93: Document management systems - H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC} - H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD} - H04L 63/101: {Access control lists [ACL]} - H04L 63/102: {Entity profiles} - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A smart document includes enhanced metadata and document content. The enhanced metadata may store an embedded database for recording and tracking a document history and rules. The smart document may be hashed to generate a unique document identifier. The unique document identifier is stored in a distributed ledge and paired with exposed metadata for enforcing access rules for the smart document. ## Claims ### Claim 1 A system for managing smart documents, the system comprising: one or more digital documents each comprising document content and document metadata, the document metadata including one or more access rules each associated with respective user identifiers; a distributed ledger storing one or more entries each comprising a document identifier paired to a distributed metadata, the document identifier associated with a respective digital document of the one or more digital documents and the distributed metadata comprising a portion of the one or more access rules; and an identity store storing user identities; wherein the document identifier is generated based on the respective digital document and a portions of the metadata is distributed to a requesting user based on the one or more access rules and verification of the requesting user by the identity store, the verification comprising validating existence of a respective user identity within the identity store. ### Claim 2 (depends on 1) The system of claim 1, wherein the metadata further comprises one or more signatures. ### Claim 3 (depends on 2) The system of claim 2, wherein the one or more signatures further comprises a paired public key and private key. ### Claim 4 (depends on 1) The system of claim 1, wherein the distributed ledger comprises a blockchain network. ### Claim 5 (depends on 1) The system of claim 1, wherein the identity store comprises a blockchain network. ### Claim 6 (depends on 1) The system of claim 1, wherein the document metadata further comprises an embedded database storing one or more of the one or more access rules, document history, or version information. ### Claim 7 (depends on 6) The system of claim 6, wherein the embedded database comprises a hash tree. ### Claim 8 A method for managing a smart document, the method comprising: receiving a digital document comprising document content and document metadata, the document metadata including one or more access rules each associated with respective user identifiers; generating a document identifier based on the received digital document by hashing the digital document; storing the document identifier in a distributed ledger in association with a distributed metadata, the distributed metadata comprising a portion of the one or more access rules; receiving a request from a user, the request including a user identifier and the document identifier; verifying the user by checking for the user identifier in an identity store; and providing a portion of the metadata to the verified user based on the user identifier and the one or more access rules. ### Claim 9 (depends on 8) The method of claim 8, wherein the metadata further comprises one or more signatures. ### Claim 10 (depends on 9) The method of claim 9, wherein the one or more signatures further comprises a paired public key and private key. ### Claim 11 (depends on 8) The method of claim 8, wherein the distributed ledger comprises a blockchain network. ### Claim 12 (depends on 8) The method of claim 8, wherein the identity store comprises a blockchain network. ### Claim 13 (depends on 8) The method of claim 8, wherein the document metadata further comprises an embedded database storing one or more of the one or more access rules, document history, or version information. ### Claim 14 (depends on 13) The method of claim 13, wherein the embedded database comprises a hash tree. ### Claim 15 A method for validating the contents of a digital document, the method comprising: computing a cryptographic hash of a content portion of a first digital document, but not a metadata portion of the first digital document, to generate a first document identifier; storing the first document identifier, but not the first digital document, on a distributed ledger implemented on a blockchain network operated by multiple entities; editing the first digital document to generate a second digital document; computing a cryptographic hash of a content portion of the second digital document, but not a metadata portion of the second digital document, to generate a second document identifier; storing the second document identifier, but not the second digital document, on the distributed blockchain ledger with a link to the first digital document; computing a cryptographic hash of a content portion of an unknown digital document, but not a metadata portion of the unknown digital document, to generate an unknown document identifier; querying the distributed blockchain ledger to determine whether the unknown document identifier matches the first document identifier or the second document identifier, whether that matching document identifier is linked to any other document identifiers, and the date when the matching identifier and any linked identifiers were stored in the blockchain ledger. ### Claim 16 (depends on 15) The method of claim 15, further comprising the steps of: maintaining an identity blockchain ledger storing public keys associated with known document authors; signing the first document identifier with a first private key corresponding to a first author to generate a signed first document identifier, and uploading the signed first document identifier to the distributed blockchain ledger; signing the second document identifier with a second private key corresponding to a second author to generate a signed second document identifier, and uploading the signed second document identifier to the distributed blockchain ledger; using a public key stored in the identity blockchain ledger to validate the identity of the author of the first digital document or the second digital document. ### Claim 17 (depends on 15) The method of claim 15, further comprising: maintaining an identity blockchain ledger storing public keys associated with verified users; associating content of one of the first document or the second document with a specified public key, the specified public key associated with an accessing user; validating the accessing user identity by checking the identity blockchain ledger for the specified public key when the accessing user attempts to access one of the first document or the second document; and providing access to the associated content to the accessing user based on the specified public key. ### Claim 18 (depends on 17) The method of claim 17, wherein one of the stored first document identifier or the stored second document identifier is paired with a complementary metadata on the blockchain ledger, the complementary metadata including an access list including the specified public key associated with one or more access rights, and wherein validating the accessing user identity further comprises checking for the access list for the specified public key. ### Claim 19 (depends on 17) The method of claim 17, wherein providing access to the associated content includes providing a decryption key associated with the specified public key and the associated content. ### Claim 20 (depends on 15) The method of claim 15, wherein one of the first digital document or the second digital document includes an embedded database, the embedded database stored in a respective metadata portion of the one of the first digital document or the second digital document.