Decisional architectures in blockchain environments
Digital or “smart” contracts execute in a blockchain environment. Any entity (whether public or private) may specify a digital contract via a table identifier in a blockchain. Because there may be many digital contracts offered as virtual services, the table identifier uniquely identifies a particular decision table and/or the digital contract offered by a virtual machine, vendor or supplier. The blockchain is thus not burdened with the programming code that is required to execute the decision table and/or the digital contract. The blockchain need only include or specify the table identifier (and perhaps one or more contractual parameters), thus greatly simplifying the blockchain and reducing its size (in bytes) and processing requirements.
1. A method performed by a server outsourcing a cloud-based contractual service, the method comprising:
receiving, by the server, a contract identifier specified by a blockchain associated with a digital contract;
receiving, by the server, a contractual parameter specified by the blockchain associated with the digital contract;
identifying, by the server, a subcontractor's Internet protocol address by querying an electronic database that associates the contract identifier specified by the blockchain to the subcontractor's Internet protocol address;
identifying, by the server, a table identifier by querying the electronic database that also associates the contract identifier specified by the blockchain to the table identifier;
sending, by the server, a service request specifying the table identifier to the subcontractor's Internet protocol address and requesting the cloud-based contractual service based on the contractual parameter specified by the blockchain and a decision table referenced by the table identifier; and
generating, by the server, a data record in a blockchain data layer describing the service request sent to the subcontractor's Internet protocol address requesting the cloud-based contractual service based on the contractual parameter specified by the blockchain and the decision table referenced by the table identifier.
2. The method of claim 1 , further comprising receiving a service result from the cloud-based contractual service.
3. The method of claim 2 , further comprising generating another data record in the blockchain data layer describing the service result.
4. The method of claim 2 , further comprising transacting a cryptocoinage in response to the receiving of the service result.
5. The method of claim 1 , further comprising transacting a cryptocoinage.
6. The method of claim 1 , further comprising transacting a cryptocoinage in response to the sending of the service request.
7. The method of claim 1 , further comprising transacting a cryptocoinage in response to the generating of the data record in the blockchain data layer.
8. The method of claim 1 , further comprising receiving a service update associated with the cloud-based contractual service.
9. The method of claim 8 , further comprising generating another data record in the blockchain data layer describing the service update.
10. A system outsourcing a cloud-based contractual service, the system comprising:
a hardware processor; and
a memory device storing instructions that when executed by the hardware processor perform operations, the operations comprising:
receiving a contract identifier specified by a blockchain associated with a digital contract;
receiving a contractual parameter specified by the blockchain associated with the digital contract;
querying an electronic database having entries that associate contract identifiers to Internet protocol addresses and to table identifiers associated with decision tables;
identifying a subcontractor's Internet protocol address of the Internet protocol addresses that is associated by an entry of the entries in the electronic database to the contract identifier specified by the blockchain;
identifying a table identifier of the table identifiers that is associated by another entry of the entries in the electronic database to the contract identifier specified by the blockchain;
sending a service request specifying the table identifier to the subcontractor's Internet protocol address requesting the cloud-based contractual service based on the contractual parameter specified by the blockchain and a decision table referenced by the table identifier; and
generating a data record in a blockchain data layer describing the service request sent to the subcontractor's Internet protocol address requesting the cloud-based contractual service based on the contractual parameter specified by the blockchain and the decision table referenced by the table identifier.
11. The system of claim 10 , wherein the operations further comprise receiving a service result from the cloud-based contractual service.
12. The system of claim 11 , wherein the operations further comprise generating another data record in the blockchain data layer describing the service result.
13. The system of claim 11 , wherein the operations further comprise transacting a cryptocoinage in response to the receiving of the service result.
14. The system of claim 10 , wherein the operations further comprise transacting a cryptocoinage.
15. The system of claim 10 , wherein the operations further comprise transacting a cryptocoinage in response to the sending of the service request.
16. The system of claim 10 , wherein the operations further comprise transacting a cryptocoinage in response to the generating of the data record in the blockchain data layer.
17. The system of claim 10 , wherein the operations further comprise receiving a service update associated with the cloud-based contractual service.
18. The system of claim 10 , wherein the operations further comprise generating another data record in the blockchain data layer describing the service update.