Digital contracts 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 contract identifier in a blockchain. Because there may be many digital contracts offered as virtual services, the contract identifier uniquely identifies a particular 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 digital contract. The blockchain need only include or specify the contract 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 executed by a server that cryptographically proves a geographical outsourcing of a digital contract, comprising:
receiving, by the server, a blockchain lacking a machine-executable programming code representing the digital contract;
determining, by the server, that an off-chain execution of the digital contract is required by identifying a contract identifier specified by the private blockchain in lieu of the machine-executable programming code representing the digital contract;
determining, by the server, a geographical restriction to the off-chain execution of the digital contract by identifying a geographical parameter specified by the blockchain;
identifying, by the server, a network address that is associated with the geographical parameter;
outsourcing, by the server, the off-chain execution of the digital contract by sending a service request to the network address requesting a cloud-based contractual service based on the contract identifier that uniquely identifies the digital contract; and
in response to the outsourcing of the off-chain execution of the digital contract, generating, by the server, a cryptographic proof of the outsourcing by hashing a cryptographic address associated with the cloud-based contractual service.
2. The method of claim 1 , further comprising receiving a service result associated with the cloud-based contractual service.
3. The method of claim 2 , further comprising generating another cryptographic proof of the service result by hashing another cryptographic address associated with a provider of the cloud-based contractual service.
4. The method of claim 2 , further comprising conducting a cryptocoinage transaction in response to the service result.
5. The method of claim 1 , further comprising receiving a service update associated with the cloud-based contractual service.
6. The method of claim 5 , further comprising generating another cryptographic proof of the service update by hashing another cryptographic address associated with a provider of the cloud-based contractual service.
7. The method of claim 1 , further comprising publicly publishing the cryptographic proof via a public blockchain.
8. The method of claim 1 , further comprising conducting a cryptocoinage based on the generating of the data record in the blockchain data layer.
9. The method of claim 1 , further comprising transacting a cryptocoinage transaction in response to the sending of the service request.
10. A system that cryptographically proves a geographical outsourcing of a digital contract, comprising:
a hardware processor; and
a memory device storing instructions that, when executed by the hardware processor, cause the hardware processor to perform operations, the operations comprising:
receiving a blockchain lacking a machine-executable programming code representing the digital contract;
read accessing the blockchain by using an application programming interface (API) associated with a read access permission;
determining that an off-chain execution of the digital contract is required by reading, via the API, a contract identifier specified by the private blockchain in lieu of the machine-executable programming code representing the digital contract;
reading, via the API, a contractual parameter specified by the blockchain that is associated with the digital identifier;
reading, via the API, a geographical parameter specified by the blockchain defining a geographical execution restriction associated with the digital contract;
identifying a network address by querying an electronic database having a database entry that associates the geographical parameter defining the geographical execution restriction to the network address;
outsourcing the off-chain execution of the digital contract by sending a service request to the network address requesting a cloud-based contractual service based on the contractual parameter specified by the blockchain; and
in response to the outsourcing of the off-chain execution of the digital contract, generating a cryptographic proof of the outsourcing by hashing a cryptographic address associated with the cloud-based contractual service.
11. The system of claim 10 , wherein the operations further comprise receiving a service result of the cloud-based contractual service.
12. The system of claim 11 , wherein the operations further comprise generating another cryptographic proof of the service result by hashing another cryptographic address associated with a provider of the cloud-based contractual service.
13. The system of claim 11 , wherein the operations further comprise conducting a cryptocoinage transaction in response to the service result.
14. The system of claim 10 , wherein the operations further comprise receiving a service update associated with the cloud-based contractual service.
15. The system of claim 14 , wherein the operations further comprise generating another cryptographic proof of the service update by hashing another cryptographic address associated with a provider of the cloud-based contractual service.
16. The system of claim 10 , wherein the operations further comprise publicly publishing the cryptographic proof via a public blockchain.
17. A non-transitory memory device storing instructions that when executed by a hardware processor perform operations for cryptographically proving a geographical outsourcing of a digital contract, the operations comprising:
receiving a blockchain lacking a machine-executable programming code representing the digital contract;
read accessing the blockchain by using an application programming interface (API) associated with a read access permission;
determining that an off-chain execution of the digital contract is required by reading, via the API, a contract identifier specified by the private blockchain in lieu of the machine-executable programming code representing the digital contract;
reading, via the API, a contractual parameter specified by the blockchain that is associated with the contract identifier;
determining a geographical requirement to the off-chain execution of the digital contract by reading, via the API, a geographical parameter specified by the blockchain;
identifying a network address by querying an electronic database having a database entry associating the geographical parameter to the network address;
geographically outsourcing the off-chain execution of the digital contract by sending a service request to the network address requesting a cloud-based contractual service based on the contractual parameter; and
in response to the geographically outsourcing of the off-chain execution of the digital contract, generating a cryptographic proof of the geographically outsourcing by hashing a cryptographic address associated with the cloud-based contractual service.
18. The non-transitory memory device of claim 17 , wherein the operations further comprise:
receiving a service result associated with the cloud-based contractual service; and
generating another cryptographic proof of the service result by hashing another cryptographic address associated with a provider of the cloud-based contractual service.