Digital contracts in blockchain environments

Inventors

Snow, Paul

Assignees

Inveniam Capital Partners Inc

Interested in licensing this patent?

MTEC can help explore whether this patent might be available for licensing for your application.

Publication Number

US-11620642-B2

Patent

Publication Date

2023-04-04

Expiration Date


Abstract

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.

Core Innovation

The invention provides a blockchain-based digital contract architecture in which a blockchain specifies a contract identifier rather than providing the contract code. A contract/data-layer server receives a first blockchain and determines, by reading the contract identifier specified by the first blockchain, that outsource execution of the digital contract is required.

To perform the outsource execution, the server accesses a blockchain distribution network to the first blockchain using an application programming interface (API) with a read access request, and conducts cryptocoinage transactions in exchange for accessing the first blockchain. Based on the contract identifier, the server maps the contract identifier via a database entry to a virtual machine, determines a network address associated with the virtual machine, and sends a service request requesting the outsource execution of the digital contract.

After receiving a response confirming successful outsource execution, the server generates a cryptographic proof of successful execution by hashing a cryptographic address associated with the virtual machine using a hashing algorithm. The server publishes the cryptographic proof and conducts a second cryptocoinage transaction in exchange for publishing the cryptographic proof, including embodiments where publishing uses a second blockchain.

Claims Coverage

The independent claims are directed to a server method, a system, and a non-transitory memory device. Across these independent claims, the inventive coverage centers on using a contract identifier from a first blockchain to trigger outsource execution on a mapped virtual machine and then publishing a cryptographic proof of successful execution, with cryptocoinage transactions tied to accessing the first blockchain and to publishing the proof.

Outsource-execution based on contract identifier from first blockchain

Receiving a first blockchain; reading a contract identifier specified by the first blockchain; determining based on the contract identifier that an outsource execution of the digital contract is required.

Virtual machine assignment via mapping contract identifier through database

Determining a virtual machine assigned to the digital contract by mapping the contract identifier via a database entry to the virtual machine; determining a network address associated with the virtual machine.

Service request to virtual machine for outsource execution and success confirmation

Sending a service request to the network address associated with the virtual machine, the service request requesting the outsource execution of the digital contract; receiving from the virtual machine a response confirming that the outsource execution of the digital contract was successful.

Cryptographic proof generation by hashing virtual-machine cryptographic address

Generating a cryptographic proof of successful execution of the digital contract by the virtual machine by hashing a cryptographic address associated with the virtual machine using a hashing algorithm; publishing the cryptographic proof of successful execution of the digital contract.

Cryptocoinage transactions for accessing and for publishing

Requesting access from a blockchain distribution network to the first blockchain using an application programming interface (API), wherein the access request comprises a read access request; conducting a first cryptocoinage transaction in exchange for accessing of the first blockchain; conducting a second cryptocoinage transaction in exchange for the publishing of the cryptographic proof.

Publishing cryptographic proof on second blockchain

Publishing the cryptographic proof of successful execution of the digital contract on a second blockchain.

Collectively, the independent claims claim a flow where blockchain-derived contract information is used to determine a mapped virtual machine for outsource execution, after which successful execution is evidenced by a cryptographic proof generated via hashing and then published, while cryptocoinage transactions support blockchain access and proof publishing, including embodiments requiring publishing on a second blockchain.

Stated Advantages

Documented Applications

No documented applications found

JOIN OUR MAILING LIST

Stay Connected with MTEC

Keep up with active and upcoming solicitations, MTEC news and other valuable information.