Role-Based Code Execution Validation Across Distributed Ledgers

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems face challenges in efficiently validating code execution across different distributed ledgers without relying on on-chain resources, particularly in scenarios where ledgers lack interoperability and trust overlap, leading to inefficiencies in asset mobility and smart contract execution costs.

Innovation Solution

A system that enables off-chain code execution to be validated on-chain using a solver-verifier contention protocol, with a controller-treasurer or judge node providing authoritative validation, ensuring accurate and efficient execution verification through a transcript-based approach.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If on-chain code execution validation is performed, then execution accuracy and trust are improved, but computational overhead and costs increase

Engineering Contradiction:

Improveexecution validation accuracyVSAvoidcomputational overhead

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The validation process is segmented into two distinct phases: off-chain execution phase where the actual code execution occurs with full computational resources, and on-chain validation phase where only the transcript and proof of correct execution are verified. This segmentation allows the heavy computational workload to be performed off-chain while maintaining on-chain reliability through cryptographic verification of the execution transcript.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

An execution transcript serves as an intermediary artifact between off-chain code execution and on-chain validation. The transcript contains cryptographic proofs and verification data that enable on-chain nodes to validate off-chain execution results without re-executing the full code, thus reducing on-chain computational overhead while maintaining validation accuracy.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If off-chain code execution is used, then computational efficiency is improved, but validation reliability and trust decrease

Engineering Contradiction:

Improvecode execution efficiencyVSAvoidexecution validation trust

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system implements a feedback mechanism where the off-chain execution result (transcript) is fed back to the on-chain ledger for verification. The transcript includes cryptographic proofs that provide feedback to on-chain nodes about the correctness of off-chain execution, enabling trust in off-chain results through on-chain verification of the feedback data.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

Instead of copying the entire code execution process to the on-chain ledger, the system creates a condensed copy of the execution transcript containing only the essential verification data. This selective copying maintains reliability by including cryptographic proofs while improving efficiency by excluding redundant execution details from on-chain storage.

Inventive Principle:

Principle #26Copying

3Adaptability or versatility

If multiple distributed ledgers are used, then functionality and options are improved, but interoperability and trust overlap decrease

Engineering Contradiction:

Improveledger functionalityVSAvoidlack of interoperability

Core Design Contradiction:

Adaptability or versatilityVSObject-generated harmful factors

Solution Approach 1:

The execution transcript format is designed with universal characteristics that enable it to be validated across multiple different distributed ledgers. The transcript includes standardized cryptographic proofs and verification data that can be interpreted by different ledger systems, allowing the same off-chain execution to be validated on multiple ledgers without requiring ledger-specific customization.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The execution transcript acts as a universal intermediary that bridges different distributed ledgers. It contains interoperable verification data that can be consumed by multiple ledger systems, enabling trust transfer and validation across ledger boundaries without requiring direct integration or trust overlap between the ledgers themselves.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS20250358136A1Verifiable code execution via role-based validation

Publication Date: 2025.11.20 TRUEBIT CO

AI summary

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.