Scuba Protocol
  • 🤿Scuba Protocol Basics
    • Getting Started
    • About Scuba Protocol
      • Supported Assets and Networks
      • Risk Acknowledgement
    • Supported Products
      • Dapp Integration Example
    • Roadmap
    • Frequently Asked Questions
    • Community and Support
  • Our Technology
    • How it works
      • The Lifecycle of a Scuba Transaction
      • The Scuba Network Features
    • Compliance Tools
  • Scuba zk Account
    • Step-to-Step Tutorial (Polygon Walkthrough)
    • Step-to-Step Tutorial (Avalanche Fuji Walkthrough)
    • Fee Structure
  • Scuba Treasure Looting Event
    • About the Scuba Treasure Looting Event
    • 🎲 Treasure Tile Selection
    • 💎 Treasure Tile Submission
      • 🔗Network Configuration and Wallet Setup
      • 🎟️zk-Account Setup (Deposit)
      • 💸Tile Submission (Transfer and Withdraw)
    • Frequently Asked Questions (Treasure Looting Event)
Powered by GitBook
On this page
  1. Our Technology

How it works

PreviousCommunity and SupportNextThe Lifecycle of a Scuba Transaction

Last updated 1 year ago

The Scuba Network system consists of five components:

  • User client (web and wasm): a user can use the client to construct proofs when sending transactions on the Scuba Network and to verify proofs when receiving transfers.

  • Scuba Bundler: receives user transactions, aggregates the transactions and submit to the Contract, and helps users pay Host Network fees. It also allows for custom fee types while avoiding revealing user addresses when paying for tx fee on Host Network.

  • Scuba Node: responsible for off-chain proof verification and uploading verification results to the chain in the format of “Scuba Blocks”. A Scuba Node needs to stake a certain amount of Scuba tokens in order to participate in the network. It is worth noting that only one Scuba Node is enough to advance the network.

  • Challenger: checks the Scuba Blocks produced by the Scuba Node and verifies the proofs submitted by the Scuba Nodes. If an error is found, it initiates a fraud proof to the ScubaArbitrator contract on the Host Network, triggering conflict resolution on the Host Network.

  • Scuba Contracts: a set of smart contracts deployed on the Host Network that lock tokens, accept user requests, and resolve conflicts when the Scuba Node’s proof verification results are questioned. Written in Solidity, can be deployed on any EVM compatible network.