Rome Docs
  • Getting Started
  • Overview of Rome
    • Rome Scales Bitcoin
      • How Rome Scales Bitcoin
    • Rome Scales Ethereum
      • How Rome Scales Ethereum
    • Rome Scales Rollups
      • How Rome Scales Rollups
    • Rome Provides Interop with Cosmos
      • How Rome Provides Interop with Cosmos
  • Nexus: Rome's Based Sequencer
    • How Nexus Works
    • Transaction Flow
  • Rome Interop
    • Rome SDK
    • Rome SDK Setup
      • Prepare Environment
      • Set Configuration
      • Run Rhea Example
      • Run Remus Example
      • Run Romulus Example
    • Remus: Cross-Rollup Atomicity
    • Romulus: Cross-Chain Atomicity
  • L2 EVM Setup
    • Prepare Config
    • Download Repos
    • Register your L2
    • Initialize your L2
    • Setup OP Geth Node
    • Run Block Explorer
    • Airdrop & Metamask
    • Check L2 State
    • Simple Transfers
    • Uniswap
    • Run on Remote Server
      • Setup AWS Server
      • Setup Certificate
  • Rome EVM
    • How to use Rome EVM
    • RPC Information
    • Tutorial to deploy a smart contract on Rome EVM
  • Shared Sequencer
    • Atomicity
    • Rome Transactions
    • Rhea
    • Hercules
    • Data Availability
    • Settlement
Powered by GitBook
On this page

Was this helpful?

  1. Shared Sequencer

Hercules

Final Confirmation for the Ordered Transactions

PreviousRheaNextData Availability

Last updated 11 months ago

Was this helpful?

Hercules accepts blocks of ordered transactions from Solana. It executes the block payload on the rollup, thus advancing the rollup state.

Rollup users get fast confirmation directly from Solana without having to wait for Hercules, which can take more time while Solana finalizes the transactions.

This provides deterministic finality for the transaction ordering. This transaction ordering along with the Merkle root of transactions is submitted to Ethereum.

Transaction flow diagram for Hercules