Systems, methods, and apparatuses for implementing super community and community sidechains with consent management for distributed ledger technologies in a cloud based computing environment
US-2019238525-A1 · Aug 1, 2019 · US
US2021288814A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2021288814-A1 |
| Application number | US-201917300141-A |
| Country | US |
| Kind code | A1 |
| Filing date | Sep 18, 2019 |
| Priority date | Sep 18, 2018 |
| Publication date | Sep 16, 2021 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A block chain-based system for multi-party, multistage process verification has a server in operable communication with a plurality of electronic client terminals. The server has a database which may have user data and implement a process verification controller. The system further has a block chain ledger. Fora multistage process involving multiple users, for each stage, the system is configured for receiving a function ID selected from a set of available functions via user interfaces of respective client terminals, generating a function hash comprising the function ID and associated function data and creating a function block chain transaction comprising the function hash which is added to the block chain ledger.
Opening claim text (preview).
1 . A system comprising a server comprising a database, the database comprising user data, the server further comprising a process verification controller; a block chain ledger; a plurality of client terminals in operable communication with the server across a wide area network, each client terminal comprising a memory device; a digital display device comprising a user interface wherein, in use, the system is configured for: for each stage of a multistage process involving a plurality of users: receiving a function ID selected from a set of available functions via user interfaces of respective client terminals and generating a function hash comprising the function ID and associated function data; creating a function block chain transaction comprising the function hash; and adding the function block chain transaction to the block chain ledger; and using the process verification controller to inspect the function block chain transactions to verify the multistage process, wherein: the process has a process ID and wherein function block chain transactions comprise a data field comprising the process ID and wherein the process verification controller is configured for identifying function block chain transactions relating to the process by identifying the process ID of data fields thereof; and the system comprises a function verification controller configured to inspect the function block chain transactions and to add verification block chain transactions to the block chain ledger and wherein the process verification controller is configured for verifying the process further with reference to the verification block chain transactions and wherein, for a verification block chain transaction comprising a verification result indicative of unsuccessful completion of a function, the process verification controller is configured for inspecting the block chain ledger for a repeat function block chain transaction associated with a function block chain transaction associated with the verification block chain transaction 2 . A system as claimed in claim 1 , wherein the function hash is a one-way function hash. 3 . A system as claimed in claim 1 , wherein the database comprises asset data and wherein the system is further configured for receiving an asset ID in relation to the function ID and hashing the asset ID with the function ID and the function data to generate the function hash. 4 . A system as claimed in claim 3 , wherein the available functions are filtered according to asset ID. 5 . A system as claimed in claim 1 , wherein the server is configured for building a process ID index which is searched by the process verification controller. 6 . A system as claimed in claim 1 , wherein each verification block chain transaction comprises a verification result and wherein the process verification controller is configured for verifying the process according to verification results of the verification block chain transactions. 7 . A system as claimed in claim 1 , wherein each verification block chain transaction comprises a transaction ID of a function block chain transaction. 8 . A system as claimed in claim 7 , wherein each repeat function block chain transaction comprises a transaction ID of a verification block chain transaction. 9 . A system as claimed in claim 1 , wherein the system further comprises a function verification controller configured to verify function block chain transactions added to the block chain ledger. 10 . A system as claimed in claim 9 , wherein the database comprises at least one transaction contract and wherein the function verification controller is configured for verifying function block chain transactions using the at least one transaction contract. 11 . A system as claimed in claim 10 , wherein the function block chain transaction comprises a data field comprising a transaction ID and wherein the function verification controller is configured for selecting a transaction contract from the at least one transaction contract according to the transaction ID. 12 . A system as claimed in claim 10 , wherein the function contract specifies at least one rule and an output. 13 . A system as claimed in claim 12 , wherein the function verification controller is configured for creating a verification block chain transaction in accordance with the output and adding the verification block chain transaction to the block chain. 14 . A system as claimed in claim 13 , wherein the verification block chain transaction comprises a data field comprising the output. 15 . A system as claimed in claim 9 , wherein the system further comprises a supervised machine learning module and wherein the function verification controller is configured for verifying a function block chain transaction in accordance with an output of the supervised machine learning module. 16 . A system as claimed in claim 13 , wherein the system is configured for storing the function data within a function data database separate from the block chain ledger and wherein the function verification controller is configured for identifying the function data within the function data database using a function block chain transaction and hashing the function data to form a check hash and comparing the check hash against the function hash of the function block chain transaction verify the function block chain transaction. 17 . A system as claimed in claim 1 , wherein the server comprises an automation processor configured to monitor the block chain ledger and automate a process when a function block chain transaction is added to the block chain. 18 . A system as claimed in claim 17 , wherein the function block chain transaction comprises a data field comprising a function ID and wherein the automation processor is configured to automate the process when the function ID matches an automation process ID. 19 . A system as claimed in claim 18 , wherein the process is the sending of an alert to a client terminal. 20 . A system as claimed in claim 9 , wherein the function hash is cryptographically signed with a private key associated with a respective user and wherein the function verification controller is configured for verifying the function hash using a corresponding public key of a cryptographic key pair. 21 . A system as claimed in claim 20 , wherein the database further comprises user hierarchy data and wherein the function hash is cryptographically signed with private keys of at least two users related by the hierarchy data.
using hash chains, e.g. blockchains or hash trees · CPC title
involving digital signatures · CPC title
involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD · CPC title
Office automation; Time management · CPC title
Protecting data integrity, e.g. using checksums, certificates or signatures · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.