Multi-tier blockchain-based system and method for document transformation and accountability

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, wherein the set of transaction documents are generated 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;

populating the set of transaction documents, 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; 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 from the supernodes that act as recorders of the transfer of real property to a different tier of nodes that act as notaries and have less nodes than the tier of supernodes; and

storing the cryptographic hash of the transaction documents on a ledger associated with each of the nodes in the different tier.

2. 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.

3. A method according to claim 2 , further comprising:

broadcasting the block to the other supernodes for storage via the selected supernode.

4. A method according to claim 2 , 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.

5. A method according to claim 1 , further comprising:

digitally signing each document in the set of transaction documents.

6. 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.

7. 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.

8. A method according to claim 2 , further comprising:

choosing the selected supernode based on a proof of work problem or using a random number via a seed.

9. A method according to claim 1 , further comprising:

storing confidential documents separate from the set of transaction documents.

10. 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.

11. A method according to claim 1 , 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.

12. A method according to claim 1 , 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.

13. A method according to claim 1 , 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.

14. A method according to claim 1 , 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.

15. A method according to claim 14 , 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.

16. A method according to claim 1 , 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.

17. A method according to claim 1 , 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.

18. 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.