IP Library Granted Patent US 11,348,098
Granted Patent B2
US 11,348,098 · App. 16/116,976 · Granted May 31, 2022

Decisional architectures in blockchain environments

Inventor: Paul Snow (Austin, TX)
Assignee: Inveniam Capital Partners, Inc.
G06Q20/367A41D1/002A41D11/00A41D13/005A41D15/00A41D31/00A41D31/06D02G3/36D02G3/441D03D1/0088D03D15/47D03D15/56D03D15/567G05B15/02G06Q20/065G06Q20/0658G06Q20/12G06Q20/3674G06Q20/3829G06Q20/401H04L9/0637A41D3/00A41D2500/20D10B2101/20D10B2401/046D10B2401/16D10B2401/18D10B2501/04D10B2501/06G06F1/163G06F16/29G06F21/53G06F21/645H04L9/0618H04L9/0643H04L9/3236H04L9/3239H04L67/12H04L2209/38H04L2209/56
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,348,098
App. No.
16/116,976
Granted
May 31, 2022
Kind
B2
Abstract

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.

Claims (26)

1. A method performed by a server that requests a cloud-based contractual service that executes a software programming component associated with a digital contract, the method comprising:

receiving, by the server, a blockchain recording transaction records conducted by computers via a network;

reading, by the server, a contract identifier encoded by the blockchain in lieu of a programming code representing the digital contract,

wherein the contract identifier occupies less memory space than the programming code representing the digital contract, the latter installed off-chain;

querying, by the server, an electronic database for the contract identifier specified by the blockchain, the electronic database having entries that electronically associate contract identifiers to Internet protocol addresses and to table identifiers including the contract identifier specified by the blockchain;

identifying, by the server, an Internet protocol address of the Internet protocol addresses that is electronically associated by the electronic database with the contract identifier specified by the blockchain that is associated with the digital contract;

identifying, by the server, a table identifier of the table identifiers that is electronically associated by the electronic database with the contract identifier specified by the blockchain that is associated with the digital contract;

sending, by the server, a service request via the network to the cloud-based contractual service represented by the Internet protocol address identified by the electronic database, the service request specifying the table identifier identified by the electronic database and requesting the cloud-based contractual service that executes the software programming component associated with the digital contract based on a decision table referenced by the table identifier; and

generating, by the server, a data record in a blockchain data layer documenting the service request sent to the Internet protocol address and specifying the table identifier referencing the decision table.

2. The method of claim 1 , further comprising receiving a service result sent from the cloud-based contractual service specifying an output generated by the software programming component associated with the digital contract based on the decision table associated with the table identifier.

3. The method of claim 2 , further comprising generating another data record in the blockchain data layer that describes the service result of the cloud-based contractual service.

4. The method of claim 2 , further comprising transacting a cryptocoinage conducted by the computers via the network in response to the service result of the cloud-based contractual service.

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 data record in the blockchain data layer that describes the service update associated with the cloud-based contractual service.

7. The method of claim 1 , further comprising generating a cryptographic proof by hashing the data record in the blockchain data layer.

8. The method of claim 7 , further comprising publicly publishing the cryptographic proof via a public blockchain.

9. The method of claim 1 , further comprising transacting a cryptocoinage conducted by the computers via the network in response to the generating of the data record in the blockchain data layer.

10. The method of claim 1 , further comprising transacting a cryptocoinage conducted by the computers via the network in response to the sending of the service request.

11. A method performed by a server requesting a cloud-based contractual service that executes a software programming component associated with a digital contract, the method comprising:

receiving, by the server, cryptocoinage transaction records conducted by computers via a network;

reading, by the server, a contract identifier specified by the cryptocoinage transaction records in lieu of a programming code representing the digital contract,

wherein the contract identifier occupies less memory space than the programming code representing the digital contract, the latter installed off-chain;

identifying, by the server, an Internet protocol address that is associated with the contract identifier;

identifying, by the server, a table identifier that is associated with the contract identifier;

sending, by the server, a service request via the network to the cloud-based contractual service represented by the Internet protocol address, the service request specifying the table identifier and requesting the cloud-based contractual service that executes the software programming component associated with the digital contract based on a decision table referenced by the table identifier; and

generating, by the server, a data record in a blockchain data layer documenting the service request sent to the Internet protocol address and specifying the table identifier referencing the decision table.

Assignments (4)
AMENDMENT AND JOINDER TO SECURITY AGREEMENT Recorded Mar 29, 2025
From: INVENIAM CAPITAL PARTNERS INC
To: 1221 INVENIAM LLC; 1221 INVENIAM II LLC
Reel/Frame 070741/0157 →
SECURITY INTEREST Recorded Jun 27, 2024
From: INVENIAM CAPITAL PARTNERS, INC.
To: 1221 INVENIAM LLC
Reel/Frame 067932/0074 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 28, 2021
From: FACTOM, INC.
To: INVENIAM CAPITAL PARTNERS, INC.
Reel/Frame 056692/0506 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 28, 2018
From: SNOW, PAUL
To: FACTOM, INC.
Reel/Frame 047604/0686 →
Continuity (2)
Provisional Application 62714909 · Aug 6, 2018
Related Publication 20200042987A1 · Feb 6, 2020
Cited By (11)
US 12,192,371 US 12,225,107 US 12,231,535 US 12,231,566 US 12,341,906 US 12,511,314 US 12,519,848 US 12,580,782 US 12,591,895 US 12,597,066 US 12,647,291