Gevulot Docs
  • Introduction
  • Firestarter
    • Overview
    • Get Started
      • Create Account
      • Purchase Credits
    • Run Workloads
      • Tasks
      • Workflows
    • Deploy Provers
      • Prover Packaging
      • Prover Deployment
    • RPC API
      • gRPC
      • gevulot-rs
    • Integrations
      • Zk Stack
      • Polygon CDK
      • Scroll SDK
    • Pricing
    • Firestarter AI
    • Firestarter Explorer
  • ZkCloud Design
    • Overview
    • Prover/Verifier Programs
    • Proving Workloads
    • Network Actors
    • Economics
    • Execution Guarantees
  • Usecases
    • Validity Rollups
    • Proof Aggregation
    • ZkVMs
    • Bridges
    • Verifiable RPC
    • ZkML
    • ZkFHE
    • ZK Coprocessors
  • Misc
    • FAQ
    • Website
    • Github
    • Twitter
    • Blog
    • Telegram
Powered by GitBook
On this page
  1. Firestarter

Overview

PreviousIntroductionNextGet Started

Last updated 5 months ago

Firestarter is a high-performance compute network optimized for ZK. It is designed to scale to thousands of prover nodes handling both CPU and GPU workloads, as well as incorporate new hardware as that becomes available. Users can generate proofs using one of the pre-deployed provers, such as Risc0, SP1, Nexus, Aztec, ZKsync, Starkware, Linea & Polygon, or by deploying their own.

Under the hood, Firestarter is an end-to-end implementation of Gevulot’s ZkCloud, just running in a permissioned fashion. The full system is made up of a blazingly fast CometBFT-based chain, which handles Credits, workload allocation and monitoring, and a network of prover nodes that provide compute for generating and verifying zk proofs.