Home
Developer guide
Getting started
  • Getting started
  • About the testnet
    • Connecting Metamask
    • Important links
    • Feature support status
    • Known issues
    • Try it out!
    • Reporting issues
  • ZK Rollup Basics
    • Contract deployment
    • Important: Account abstraction support
    • Block numbers and time
    • 2.0 Overview
    • Handling of ETH and tokens
    • Fee model
    • Transaction types
    • Transaction formats
    • Confirmations and finality
    • Decentralization roadmap
    • L1 / L2 Interoperability
    • Current limitations
    • Web3 API
  • Understanding zkSync 2.0
  • Home
  • /
  • Getting started
  • /
  • ZK Rollup Basics
  • /
  • Confirmations and finality

Confirmations and finality

On zkSync, each transaction is one of the four stages:

  • Pending. The transaction was received by the operator, but it has not been processed yet.
  • Processed. The transaction is proceesed by the server and is confirmed to be included in the next block.
  • Committed. The transaction state diffs were published on Ethereum.
  • Finalized. The SNARK validity proof has been submitted and verified by the smart contract. After this step, the transaction is considered to be final.

The typical time for a transaction to go from Processed to Finalized is a couple of hours.

Please note that for developer convenience, we will usually treat the Processed and Committed states as a single stage called Committed since they have no difference from the UX/DexEx standpoints.

Last updated: 8/17/2022, 2:45:12 PM
Previous
Transaction formats
Next
Decentralization roadmap
Edit on GitHub