How Does Truebit Work?

Truebit Workflow

Truebit Verify is aimed at developing, deploying and executing Truebit Functions, apart from Truebit API Tasks with complete transparency. Truebit's platform provides proof of the correct execution of your code and allows you to integrate safely with different APIs, move data between blockchains, and implement complex application code.

There are two execution types:

• Function Tasks – execute predefined functions.

• API Tasks – interact with external APIs.

Both task types are invoked through a standard REST interface, allowing seamless integration into your applications or workflows, moving data across different chains.

Function Tasks

This diagram represents the Function Task execution from a Task Requester point of view.

As a Task Developer, you create Truebit Function Tasks —self-contained functions that run on Truebit Verify Node. These tasks act like microservices and are exposed via a REST API.

For Function Tasks, Truebit Verify Hub makes these tasks internet-accessible and orchestrates node operations. Under the hood, Truebit leverages blockchain-based ledgers to secure execution, ensure full transparency, and manage system-level financial mechanics.

Within Function Tasks, each of them is executed by multiple nodes, with Truebit Transcripts certifying outputs and providing an immutable audit trail of task and node behavior. In case of discrepancies in node responses, the Adjudication Process is triggered to resolve them by re-executing the task under the Truebit Control Node. This process determines which node provided an incorrect result, ensuring discrepancies are resolved and all nodes execute tasks honestly.

API Tasks

This diagram represents the API task execution from a Task Requester point of view.

As a Task Developer, you create Truebit API Tasks. These tasks function like microservices and are accessible via a REST API.

The TEE (Trusted Executed Environment) executes API Tasks by directly calling an API endpoint. This keeps API credentials and data private. Truebit Verify Nodes use a shared session key to verify communication between the Hub and API endpoints.

Transparency is also crucial when moving data across different blockchains. As blockchains don't naturally communicate, interoperability becomes complex in Web3. We simplify this by transparently coding interactions between blockchains, ensuring the validity of read and write operations. This certification makes the operation secure, resolving challenges in moving data between different blockchains.