# US 2025/0358136 A1 · Verifiable code execution via role-based validation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0358136 A1
- Document ID: US20250358136A1
- Status: Published application
- Kind: A1
- Application number: 18/872,136
- Filed: 2023-06-06
- Published: 2025-11-20
- Earliest claimed: 2022-06-07
- Assignees: Truebit Co.
- Applicants: Truebit Co.
- Inventors: Jason Richmond Teutsch
- Web page: https://patentgrep.com/patent/US20250358136A1

## CPC

- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 9/3271: {using challenge-response}
- G06F 9/4887: {involving deadlines, e.g. rate based, periodic}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A controller-treasurer node may access a transcript within off-chain storage with respect to a particular distributed ledger. The transcript may include an execution profile for an execution of executable code by a solver node. Based on the transcript, the controller-treasurer may determine whether the solver node correctly executed the code. When the controller-treasurer node determines that the execution profile indicates a correct execution, the controller-treasurer node may commit an indication of the validity of the execution profile to the particular distributed ledger.

## Claims

### Claim 1

A method including:
accessing, via a controller-treasurer node and within off-chain storage, a transcript provided at least in part by a participant node, the transcript including an execution profile for at least executable code designated for a task, the off-chain storage including a first storage location unrecorded within a chain associated with a distributed ledger, where the transcript references a commitment by the participant to a particular solution for the executable code and a reveal of the solution for the executable code occurring after provision of the commitment, the commitment binding the participant node to the particular solution prior to the reveal of the solution for the executable code;
determining, based on the references to the commitment and the reveal within the transcript, that the participant node correctly executed the executable code for the task;
committing, via the controller-treasurer node and responsive to the determination, an indication for the distributed ledger that the participant node correctly executed the executable code for the task to validate the execution by the participant node for the distributed ledger; and
causing the indicator to be recorded on-chain for the distributed ledger, the on-chain recording including a recordation location within a cryptographic structure associated with the distributed ledger.

### Claim 2 (depends on 1)

The method of claim 1, where validating the execution by the participant node for the ledger includes validating at least a portion of the transcript for the distributed ledger.

### Claim 3 (depends on 1)

The method of claim 1, where the transcript includes a record of a verifier challenge.

### Claim 4 (depends on 3)

The method of claim 3, where validating the execution by the participant node for the ledger includes causing transfer of token-set and/or counter-set responsive to the correctly executed executable code determined by the controller-treasurer node.

### Claim 5 (depends on 1)

The method of claim 1, where the controller-treasurer node includes a node executing a controller role and/or a treasurer role.

### Claim 6 (depends on 1)

The method of claim 1, where the first storage location includes an on-chain referenced location for another distributed ledger.

### Claim 7 (depends on 6)

The method of claim 6, where validating the execution by the participant node includes analyzing a judgment provided for the another distributed ledger by a judge node associated with the another distributed ledger.

### Claim 8 (depends on 1)

The method of claim 1, where validating the execution by the participant node includes analyzing a judgment in off-chain storage, the judgment provided a judge node.

### Claim 9 (depends on 1)

The method of claim 1, where the execution profile includes an ordered set of transactions detailing a solution for the executable code.

### Claim 10 (depends on 9)

The method of claim 9, where the transcript further includes a record of a reveal action of the solution by the participant node.

### Claim 11 (depends on 10)

The method of claim 10, where the record of the reveal action indicated that the reveal action occurred prior to an end of a timeout window for execution.

### Claim 12 (depends on 1)

The method of claim 1, where the indication for the distributed ledger that the participant node correctly executed the executable code includes a referenceable validation of an output value from the correctly executed executable code.

### Claim 13

A system including:
communication circuitry configured to access, via a controller-treasurer node and within off-chain storage, a transcript provided at least in part by a participant node, the transcript including an execution profile for at least executable code designated for a task, the off-chain storage including a first storage location unrecorded within a chain associated with a distributed ledger, where the transcript references a commitment by the participant to a particular solution for the executable code and a reveal of the solution for the executable code occurring after provision of the commitment, the commitment binding the participant node to the particular solution prior to the reveal of the solution for the executable code; and
role-execution circuitry configured to:
determine, based on the references to the commitment and the reveal within the transcript, that the participant node correctly executed the executable code for the task;
commit, via the controller-treasurer node and responsive to the determination, an indication for the distributed ledger that the participant node correctly executed the executable code for the task to validate the execution by the participant node for the distributed ledger; and
cause the indicator to be recorded on-chain for the distributed ledger, the on-chain recording including a recordation location within a cryptographic structure associated with the distributed ledger.

### Claim 14 (depends on 13)

The system of claim 13, where the role-execution circuitry is configured to validate the execution by the participant node for the ledger by validating at least a portion of the transcript.

### Claim 15 (depends on 13)

The system of claim 13, where the transcript includes a record of a verifier challenge.

### Claim 16 (depends on 15)

The system of claim 15, where the role-execution circuitry is configured to validate the execution by the participant node for the ledger by causing transfer of token-set and/or counter-set responsive to the correctly executed executable code determined the controller-treasurer node.

### Claim 17 (depends on 13)

The system of claim 13, where the controller-treasurer node includes a node executing a controller role and/or a treasurer role.

### Claim 18

A product including:
machine-readable media other than a transitory signal; and
instructions stored on the machine-readable media, the instructions configured to, when executed, cause a processor to:
access, via a controller-treasurer node and within off-chain storage, a transcript provided at least in part by a participant node, the transcript including an execution profile for at least executable code designated for a task, the off-chain storage including a first storage location unrecorded within a chain associated with a distributed ledger, where the transcript references a commitment by the participant to a particular solution for the executable code and a reveal of the solution for the executable code occurring after provision of the commitment, the commitment binding the participant node to the particular solution prior to the reveal of the solution for the executable code;
determine, based on the references to the commitment and the reveal within the transcript, that the participant node correctly executed the executable code for the task;
commit, via the controller-treasurer node and responsive to the determination, an indication for the distributed ledger that the participant node correctly executed the executable code for the task to validate the execution by the participant node for the distributed ledger; and
cause the indicator to be recorded on-chain for the distributed ledger, the on-chain recording including a recordation location within a cryptographic structure associated with the distributed ledger.

### Claim 19 (depends on 18)

The product of claim 18, where the first storage location includes an on-chain referenced location for another distributed ledger.

### Claim 20 (depends on 18)

The product of claim 18, where the execution profile includes an ordered set of transactions detailing a solution for the executable code.
