ELDER
TwitterGithub
  • Welcome
  • Elder Snapshot
  • Introduction
    • Back to Basics
    • Rollups : Behind The Scenes
    • Challenges
    • Resolutions
  • Presenting Elder
    • Why ELDER?
    • ELDER : The "VISA" of WEB3
    • Perks for Users
    • Perks for Rollup Operators
  • Architecture
    • Quick Overview: Cosmos-SDK and CometBFT
    • Architecture Design
    • Transaction Flow
    • Run an ELDER Node
    • Elder-Wrap
    • ElderJS
  • Integrations
    • Overview
    • OP-Stack
Powered by GitBook
On this page
  1. Architecture

Transaction Flow

PreviousArchitecture DesignNextRun an ELDER Node

Last updated 4 months ago

Transaction Lifecycle

  1. Unified Entry Point: Users can send transactions across multiple rollups through a single entry point.

  2. Transaction Sequencing: The proposer in the elder protocol sequences transactions from different rollups and creates blocks for the respective rollups. The network achieves 1-block finality and provides inclusion finality for rollups.

  3. Data Availability (DA): Elder network compiles a single full block containing transactions from all rollups and sends it to the Data Availability (DA) layer.

  4. Rollup Distribution: Rollups query their unit blocks and the transactions from Elder.

  5. Proof Handling: Rollups send fault or validity proofs to the settlement layer.

  6. Merkle Root Emission: Upon settlement, the system emits an event containing the Merkle root of the transaction roots from the blocks in the batch.

  7. Watch Tower Operations: An independent, stateless Watch Tower can submit disagreement transactions to the sequencer node in case of a root hash mismatch.

  8. Disagreement and Slashing: If a mismatch is detected, the Watch Tower submits a disagreement transaction, which can result in slashing the registration stake of the rollups.