Validium Docs
  • Overview
  • Connect to Validium
  • Start Coding 🚀
    • Quickstart
      • Overview
      • Deploy using Validium CLI
      • Deploy using Quickstart Repository
      • Deploy your first contract
      • Create an ERC20 token
  • Tooling
    • Block Explorers
    • Hardhat-Validium
      • Overview
      • Installation
      • Guides
        • Getting started
        • Migrating Hardhat project to Validium
        • Compiling non-inlinable libraries
      • Plugins
        • hardhat-zksync
        • hardhat-zksync-solc
        • hardhat-zksync-vyper
        • hardhat-zksync-deploy
        • hardhat-zksync-upgradable
        • hardhat-zksync-verify
        • hardhat-zksync-verify-vyper
        • hardhat-zksync-ethers
        • hardhat-zksync-node
        • Hardhat Community Plugins
    • Foundary
      • Overview
      • Installation
      • Getting Started
      • Migration Guide
        • Overview
        • Compilation
        • Deployment
        • Testing
  • Test and Debug
    • Getting Started
    • Docker L1 - L2 Nodes
    • In-Memory Node
    • Continuous Integration
    • Hardhat
    • Foundry
  • API Reference
    • Overview
    • Conventions
    • ZKs JSON-RPC API
    • Debug JSON-RPC API
    • Ethereum JSON-RPC API
    • PubSub JSON-RPC API
  • Concepts
    • Transaction Lifecycle
    • Blocks and Batches
    • Validium Network Fee Mechanism
    • Finality
    • System Upgrades
    • ZK Chains
    • Data Availability
      • Overview
      • Recreating L2 state from L1 pubdata
      • Validiums
    • Account Abstraction
    • L1 <-> L2 Communication
  • Components
    • Overview
    • Smart & System Contracts
      • Smart Contracts
      • System Contracts
    • Shared Bridges
    • Sequencer / Server
    • Validium Network EVM
      • Overview
      • Bootloader
      • Precompiles
      • Virtual Machine Specification
        • ZKsync Virtual Machine primer
        • VM Formal Specification
    • Prover
      • Overview
      • ZK Terminology
      • Running the Prover
      • Circuits
        • Overview
        • Circuit Testing
        • CodeDecommitter
        • DemuxLogQueue
        • ECRecover
        • KeccakRoundFunction
        • L1MessagesHasher
        • LogSorter
        • Main VM
        • RAMPermutation
        • Sha256RoundFunction
        • StorageApplication
        • Sorting and Deduplicating
          • Overview
          • SortDecommitments
          • StorageSorter
          • LogSorter
      • Boojum Gadgets
      • Boojum Function - `check_if_satisfied`
    • Compiler
      • Compiler Toolchain Overview
        • Compiler Toolchain Overview
        • Solidity Compiler
        • Vyper Compiler
        • LLVM Framework
      • Specification
        • Overview
        • Code Separation
        • System Contracts
        • Exception Handling
        • EVM Legacy Assembly Translator
        • Instructions
          • Instruction Reference
          • EVM
            • Native EVM Instructions
            • Arithmetic
            • Bitwise
            • Block
            • Call
            • Create
            • Environment
            • Logging
            • Logical
            • Memory
            • Return
            • Sha3
            • Stack
          • Extensions
            • Overview
            • Validium Network Extension Simulation (call)
            • Validium Network Extension Simulation (verbatim)
          • EVM Legacy Assembly
          • Yul
        • EraVM Binary Layout
    • Fee Withdrawer
    • Portal - Wallet + Bridge
    • Block Explorer
    • Transaction filtering
Powered by GitBook
On this page
  • Finality on Ethereum
  • Finality on Validium Network
  • Instant confirmations
  1. Concepts

Finality

Explore the concept of finality in blockchain systems and learn about the steps involved in achieving transaction settlement.

PreviousValidium Network Fee MechanismNextSystem Upgrades

Last updated 7 months ago


Finality in blockchain systems refers to the point at which a transaction is considered irreversible and permanently part of the blockchain. This concept is crucial for ensuring transaction security and reliability.

Finality on Ethereum

On Ethereum, finality is typically achieved after 2 , which translates to approximately 13 minutes under normal network conditions. This duration allows for sufficient block confirmations to prevent reversals and ensure that transactions are settled securely.


Finality on Validium Network

Validium Network, as a Layer 2 (L2) rollup, ties its finality and security mechanisms to those of the underlying Layer 1 (L1) Ethereum chain. The steps involved in reaching finality in Validium Network include:

  1. Batch Formation: Transactions are collected and grouped into a batch. This step generally takes a few minutes.

  2. Batch Commitment: The complete batch is committed to the Ethereum blockchain.

  3. Proof Generation: A cryptographic proof that validates the entire batch is generated. This process typically takes about an hour.

  4. Proof Submission: The generated proof is submitted to an Ethereum smart contract for verification.

  5. Batch Finalization: The batch undergoes a final verification and is settled on Ethereum. This step includes a delay of approximately 21 hours as a security measure during the alpha phase of Validium Network.

Overall, the complete finality time for a transaction on Validium Network is around 24 hours, aligning with the finality of the corresponding Ethereum block.

Advancements in validity proof research are continuously being made, promising potential reductions in proof generation times and, consequently, faster finality periods in the future.


Instant confirmations

While the full finality process on Validium Network can take up to 24 hours, transactions are treated with instant confirmation for user convenience:

  • Immediate Transaction Display: Once submitted, transactions are quickly shown in the user interface and API as unconfirmed.

  • Immediate Asset Usability: Users can immediately utilize the transferred assets for further transactions, which may even be included in the same Validium Network batch.

This feature enables a seamless user experience, although more cautious users may opt to wait for the transaction to reach full finality or pass any intermediate steps before fully trusting the transaction's completion.

epochs