# US 2022/0284525 A1 · Multi-tier blockchain-based system and method for document transformation and accountability

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0284525 A1
- Document ID: US20220284525A1
- Status: Published application
- Kind: A1
- Application number: 17/751,387
- Filed: 2022-05-23
- Published: 2022-09-08
- Earliest claimed: 2018-09-06
- Assignees: Side, Inc.
- Applicants: Side, Inc.
- Inventors: Edward Wu; Guy Gal; Christopher Dzoba; Jeffrey Judkins; Mark J. Stefik; Adriano Castro
- Web page: https://patentgrep.com/patent/US20220284525A1

## CPC

- G06Q 50/167: {Closing}
- G06F 16/137: {Hash-based (content-based indexing of textual data G06F16/31)}
- G06F 16/1834: {implemented based on peer-to-peer networks, e.g. gnutella (p2p communication protocols H04L67/104)}
- G06F 16/1837: {Management specially adapted to peer-to-peer storage networks (topology management mechanisms of peer-to-peer networks H04L67/1042)}
- G06F 16/2358: {Change logging, detection, and notification (replication G06F16/27)}
- G06F 16/248: Presentation of query results
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- G06F 40/174: Form filling; Merging
- G06F 40/186: Templates
- G06Q 10/06314: {Calendaring for a resource}
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/3825: {Use of electronic signatures}
- G06Q 20/3827: {Use of message hashing}
- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- G06Q 50/16: Real estate
- G06V 30/418: Document matching, e.g. of document images
- H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]}
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates}
- H04L 9/3236: {using cryptographic hash functions}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/3247: {involving digital signatures}
- H04L 9/3297: {involving time stamps, e.g. generation of time stamps}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06Q 2220/00: Business processing using cryptography
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06V: IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A multi-tier blockchain-based method for document transformation and accountability is provided. A set of transaction documents for a transfer of real property is received and the transfer is recorded via a multi-tier blockchain. The set of transaction documents is stored on a ledger associated with two or more supernodes in a tier of supernodes. A cryptographic hash of the set of transaction documents is provided to a different tier of nodes and stored on a ledger associated with each of the nodes in the different tier. A number of supernodes in the tier is larger than a number of the nodes in the different tier.

## Claims

### Claim 1

A multi-tier blockchain-based method for document transformation and accountability, comprising:
receiving a set of transaction documents for a transfer of real property; and
recording the transfer via a multi-tier blockchain, comprising:
storing the set of transaction documents on a ledger associated with two or more supernodes in a tier of supernodes;
providing a cryptographic hash of the set of transaction documents to a different tier of nodes; and
storing the cryptographic hash of the transaction documents on a ledger associated with each of the nodes in the different tier, wherein a number of supernodes in the tier is larger than a number of the nodes in the different tier.

### Claim 2 (depends on 1)

A method according to claim 1, further comprising:
selecting one of the supernodes in the tier for adding the set of transaction documents as a block for providing to the other supernodes for storage.

### Claim 3 (depends on 2)

A method according to claim 2, further comprising:
broadcasting the block to the other supernodes for storage via the selected supernode.

### Claim 4 (depends on 1)

A method according to claim 1, wherein the selected supernode transmits a request for notarization of the block to one of the nodes in the different tier with the cryptographic hash.

### Claim 5 (depends on 1)

A method according to claim 1, further comprising:
digitally signing each document in the set of transaction documents.

### Claim 6 (depends on 1)

A method according to claim 1, wherein the set of transaction documents includes at least one of a real estate contract, chain of title, proof of escrow funding, and property deed.

### Claim 7 (depends on 1)

A method according to claim 1, further comprising:
determining the two or more supernodes based on a characteristic of the transfer of real property comprising one or more of location of the real property and value of the real property.

### Claim 8 (depends on 1)

A method according to claim 1, further comprising:
choosing the selecting supernode based on a proof of work problem or using a random number via seed.

### Claim 9 (depends on 1)

A method according to claim 1, further comprising:
storing confidential documents separate from the set of transaction documents.

### Claim 10 (depends on 9)

A method according to claim 9, further comprising at least one of:
generating a watermark on each of the confidential documents for each of the parties of the transfer of real property.

### Claim 11 (depends on 1)

A method according to claim 1, further comprising:
generating the set of transaction documents using templates, wherein each template comprises a plurality of data fields each associated with a data field identifier and the data field identifiers are same for the data fields that are the same in different documents.

### Claim 12 (depends on 11)

A method according to claim 11, further comprising:
populating the templates, comprising:
receiving data values in one or more of the data fields of at least one document template of a plurality of document templates;
receiving an address for the real property;
identifying based on the received property address a set of compliance rules to be applied to populated data fields for determining correctness;
receiving a role of a user associated with the property;
based on the property address and user role, selecting a subset of the document templates to be populated from the plurality of document templates as active documents for a transaction of the property;
generating a model for the active documents comprising the received data values and the data field identifiers for the data fields populated by the received data values, wherein each received data value is associated with the data field identifier for the data field populated with that received data value; and
populating via the model those data fields in the active documents that are unpopulated with the received data values associated with the data field identifiers for those unpopulated data fields.

### Claim 13 (depends on 12)

A method according to claim 12, further comprising:
monitoring correctness of the populated data values in the active documents using the compliance rules via automatic verification of at least a portion of the data values by an authoritative source of subject matter for the portion of the data values.

### Claim 14 (depends on 12)

A method according to claim 12, further comprising:
running completeness logic on the active documents and the data fields of the active documents, comprising at least one of:
comparing the active documents for the transaction with a library of document templates for the transaction and determining one of a new active document template is required for the transaction and no further active documents are required for the transaction;
identifying one or more data fields without associated data values and creating a status indicator for the one or more identified data fields; and
adding one or more data fields to one of the active documents based on a related data field with an associated data value in that active document.

### Claim 15 (depends on 12)

A method according to claim 12, further comprising:
running consistency logic on the data fields of the active documents, comprising:
identifying a change to one of the data values within one of the data fields of one such active document; and
updating the data values with the changed data value to each active document with at least one data field with the same data field identifier as the changed data value.

### Claim 16 (depends on 12)

A method according to claim 12, further comprising:
running correctness logic on one or more of the data fields of the active documents, comprising:
reviewing the data field values and combinations of the data field values within the active documents; and
determining whether the data field values and the combinations of data field values are verified by the authoritative source.

### Claim 17 (depends on 16)

A method according to claim 16, further comprising:
during running of the correctness logic, connecting to one or more servers with information for the authoritative source; and
checking the data fields in the active documents for accuracy with the information of the authoritative source.

### Claim 18 (depends on 12)

A method according to claim 12, further comprising:
running compliance logic on the active documents, comprising:
confirming that the active documents include all documents in a required set of documents for the transaction.

### Claim 19 (depends on 12)

A method according to claim 12, further comprising:
running confirmation logic on the data fields of the active documents, comprising:
reviewing the active documents;
identifying fields designated for signatures and dates; and
determining whether the identified fields designated for signatures and dates are associated with associated data values.

### Claim 20 (depends on 1)

A method according to claim 1, wherein the set of the transaction documents are stored on the two or more supernodes for at least one of a predetermined amount of time or indefinitely.
