Storage Proofs
HomeDashboard
  • Getting Started
    • Introduction
    • Use Cases
    • Quick Start Guide
    • Key Concepts
  • Storage Proofs
    • Overview
    • Workflow
      • Workflow Examples
    • Accessing Block Hash
  • Solutions
    • Storage Proof API
      • Authentication
      • Payload Examples
    • Turbo
      • Workflow
      • RPC Endpoint
      • Turbo Compute
  • Architecture
    • Overview
    • Smart Contracts
    • Cross-Chain Storage Proofs
      • Native Messaging Systems
      • OP Stack Chains
  • Guides
    • Using Storage Proof API
    • Integrating Storage Proofs
    • Building a Storage Proof Powered Bridge
    • Writing Turbo Smart Contracts
    • Sending Turbo Transactions
  • References
    • Contract Addresses
    • Supported Networks
    • Glossary
  • Media Links
    • Twitter
    • Telegram
Powered by GitBook
On this page
  1. Solutions
  2. Turbo

Workflow

How Turbo Works

PreviousTurboNextRPC Endpoint

Last updated 10 months ago

  1. Transaction Initiation: A user initiates a transaction targeting a Turbo-enabled smart contract.

  2. RPC Processing: The Turbo Enabled RPC processes the transaction:

    • If no Storage Proofs are required, the transaction is directly broadcasted to the chain.

    • If Storage Proofs are needed but missing, the transaction fails, and the system identifies the required proofs.

  3. API Query Building: The system constructs an API request to fetch necessary proofs from the off-chain Storage Proof API.

  4. Turbo Bundle Creation: Upon receiving the Storage Proof, a Turbo Bundle is constructed:

    • The first transaction verifies the Storage Proof and assigns verified data to contract storage.

    • Subsequent transactions utilize these variables.

    • A final transaction clears the variables to maintain blockchain integrity.

  5. Blockchain Inclusion: The Turbo Bundle is sent to a sequencer or validator for inclusion in the blockchain.

Turbo Transaction Workflow