Spicenet Docs
  • Welcome to Spicenet
  • Introduction to Spicenet
    • Understanding the Need for a Global Financial Internet
    • The Sovereign Rollup Approach
  • Core Technical Architecture
    • The Nearly Optimal Merkle Tree (NOMT)
    • Asynchronous Execution Pipeline
    • Validator System Architecture
    • Shockwave
  • Advanced Technical Components
    • Sharding Implementation
    • Decentralized Sequencing
    • Based Multiple Concurrent Proposers
    • Multi-Staking Protocol
  • spicenet trading stack
    • Spicenet Trading Stack: Enshrined Liquidity and Market Structure
    • Unified Margin Accounts (UMAs)
    • Global and Local Markets
    • Instrument and Product Specification
    • Flashbooks: Intention-Based Orderbooks
    • Network-Owned Liquidity(NoL): A Deep Dive
    • Decoupled Order Matching and Settlement
  • spicenet execution network
    • Spicenet Execution Network
  • Products
    • PepperDEX: The Connective Tissue of Spicenet
    • hotUSD: the first Bitcoin dollar
    • User Abstraction Suite
    • Capsule: Smart Wallet Module
  • $SPICE Token
    • What is $SPICE?
    • $SPICE Utility
    • $SPICE Distribution
    • Airdrop and Ambassador Program
Powered by GitBook
On this page
  1. Core Technical Architecture

Asynchronous Execution Pipeline

PreviousThe Nearly Optimal Merkle Tree (NOMT)NextValidator System Architecture

Last updated 5 months ago

Traditional blockchain systems process transactions in this order:

  1. Receive transaction

  2. Execute transaction

  3. Update state

  4. Confirm transaction

This sequential process creates unnecessary delays. Spicenet's asynchronous execution pipeline works differently:

Let's walk through what happens when you submit a trade:

  1. Immediate Pre-confirmation (~1ms):

    • Your transaction is validated for basic correctness

    • You receive a pre-confirmation if it's valid

    • The sequencer starts preparing the batch

  2. Parallel Processing:

    • While your transaction is being batched, the sequencer is simultaneously:

      • Executing previous transactions

      • Updating state from earlier batches

      • Processing new incoming transactions

  3. Final Settlement (30-200ms):

    • Your transaction is included in a batch

    • The batch is posted to Celestia

    • Execution completes and state is updated

    • Full confirmation is achieved

This pipeline means traders can:

  • Receive near-instant confirmation of their trades

  • Chain multiple operations together quickly

  • Achieve predictable execution times