Interested in licensing this patent?
MTEC can help explore whether this patent might be available for licensing for your application.
Abstract
Digital or “smart” contracts execute in a blockchain environment. Any entity (whether public or private) may specify a digital contract via a blockchain. Because there may be many digital contracts offered as virtual services, the contract 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 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 an off-blockchain smart contract execution architecture in which a blockchain specifies a contract identifier associated with a digital contract and, in some cases, associated contractual parameters and verification values. A data layer server inspects the blockchain and cryptographically verifies the sender before proceeding with execution.
The data layer server queries an electronic contracts database to map the contract identifier and/or contractual parameters to a destination network resource. The mapped destination may be a contract server, a virtual machine, a service, or a decision table engine, and the server sends a service request requesting execution of the digital contract and then receives a service response or result.
After receiving the service response or result, the server generates blockchain data-layer records such as timestamps, updates, and proofs, including cryptographic proofs or affinities published on a public blockchain. The architecture separates execution from documentation of execution, with optional outsourcing of different contract components and decision tables across different network resources and virtual machines.
Claims Coverage
The provided material includes three independent claims covering the same core server-side or system/memory-device flow for identifying a digital contract via a contract identifier on a blockchain, resolving a network address from an electronic database, sending a service request for execution, and receiving a service result; dependents further add blockchain data-layer records and cryptocoinage transactions tied to specific steps.
Blockchain contract identifier to network address resolution
Identifying a contract identifier specified by a blockchain, the contract identifier associated with the digital contract, and identifying a network address associated with the network resource by querying an electronic database that associates the contract identifier to the network resource.
Service request triggers execution via the network address
Sending a service request to the network address requesting an execution of the digital contract.
Service result retrieval
Receiving a service result of the execution of the digital contract.
Blockchain data-layer record generation for service request or service result
Generating a blockchain data layer data record describing the service request sent to a network address requesting execution of a digital contract and/or generating a blockchain data layer data record describing the service result.
Cryptocoinage tied to a specific blockchain-related step
Conducting cryptocoinage in response to generating a data record in the blockchain data layer, and/or in response to sending a service request to the network address, and/or in response to receiving a service result.
Across the independent claims, the core inventive coverage is the mapping of a blockchain-specified contract identifier to a network address via an electronic database, sending a service request for digital contract execution to that network address, and receiving a service result; dependent features add blockchain data-layer record generation and cryptocoinage tied to generating the records, sending the request, and/or receiving the service result.
Stated Advantages
Not explicitly described in patent.
Documented Applications
Not explicitly described in patent.
Interested in licensing this patent?