LogoLogo
  • Entangle
    • Overview
    • Security Audits
  • Universal Interoperability Protocol
    • Overview
    • Architecture
      • Scalability and Network Stability
        • L2 Utility Blockchains
        • Transmitter Groups
      • Security and Consensus Mechanism
      • Finality
      • Execution Latency
      • Compatibility and Interoperability
    • Developer Guides
      • Getting Started
      • Solidity
        • Simple Abstract Messenger Example
        • Deploying Your Custom EVM Protocol
        • Bridging Tokens with UIP
        • Become an EVM Transmitter
      • Solana
        • Simple Abstract Messenger Example
        • Deploying Your Custom Solana Protocol
        • Become a Solana Transmitter
      • Calculate Cross-Chain Transaction Cost
      • Customizable Message Transmission Options
      • How to Debug Sent Messages
      • SDK Setup
      • Revenue Sharing for Transmitters
      • How to Become a Super Transmitter
    • Endpoints
  • Universal Data Feeds
    • Overview
    • Architecture
      • Data Delivery Methods
        • Pull Model
        • Push Model
      • Oracle Contract & User Interaction
    • Developer Guides
      • Custom Data Feeds
      • Fetch Data via Pull Model (PAYG)
        • EVM Smart Contracts
        • Solana Smart Contracts
      • Fetch Data via Pull Model (Subscriptions)
        • EVM Smart Contracts
        • Solana Smart Contracts
      • Fetch Data via Push Model
        • EVM Smart Contracts
        • Solana Smart Contracts
    • User Guides
      • Accessing Feeds
      • Subscribe to a Data Feed
      • Check Subscription
      • Manage Subscription
      • Renew Subscription
    • Data Endpoints
  • Universal Token Standard
    • Overview
    • Architecture
      • Fee Components
    • Developer Guides
      • Manual Deploy
        • Token Deployment Types
        • Create a Custom Token
        • Factory Blueprint Deployment
        • Examples
          • Initial Setup
          • UTS Connector
            • Mint & Burn Connector Scheme
            • Lock & Unlock Connector Scheme
            • Connector Over Native Currency
          • UTS Token
            • Simple Token
            • Token with Messages
      • Bridge SDK
      • Token Verification
      • Fees Calculation & Gas Estimation Logic
      • Estimations
    • User Guides
      • Launch Universal Token
      • Create a Liquidity Pool
      • Expand Existing Token
      • Transfer Liquidity to Connector
      • Bridging
    • Contract Addresses
  • Entangle Interoperable Blockchain
    • Overview
    • Architecture
    • Developer Guides
      • Set up a Validator Node
      • Delegating to Validators
      • Undelegating from Validators
      • Supported Accounts
  • More
    • Media Kit
    • FAQ
    • Report an Issue
    • Become a Partner
Powered by GitBook
On this page
  • Types of Finality
  • Examples

Was this helpful?

Export as PDF
  1. Universal Interoperability Protocol
  2. Architecture

Finality

PreviousSecurity and Consensus MechanismNextExecution Latency

Last updated 1 month ago

Was this helpful?

Just because a transaction shows up on the blockchain doesn’t mean it’s set in stone — it can still be reversed or reorganized, depending on how the blockchain works. I.e., blockchains differ in their consensus mechanisms and finality times so while transactions may appear on-chain shortly after submission, they are not immediately secure from potential modifications or reversals. This impacts UIP's transaction speed.

Types of Finality

Different blockchains have their own ways of deciding when a transaction is truly final, and these methods can vary a lot in terms of speed and security. Generally, there are two types of finality:

  • Determinisitic Finality - Ensures that once a transaction is finalized, it cannot be undone. This type is common in Proof of Stake (PoS) and Proof of Authority (PoA) blockchains, which rely on validators reaching consensus to confirm a transaction's permanence. Deterministic finality offers users predictability and security, as transactions are finalized once specific protocol criteria are met, often within seconds to minutes.

  • Probabilistic Finality - Typical in Proof of Work (PoW) blockchains, provides increasing certainty over time. Transactions become more secure as additional blocks are added on top of the block containing the transaction. While this model works effectively, it is slower than deterministic systems, often requiring minutes or even hours for practical finality.

Examples

The finality of the source and destination blockchains plays a critical role in transaction execution latency. On fast-finality blockchains like or , finality can occur in under a second, allowing near-instantaneous cross-chain interactions. Conversely, blockchains with slower finality, such as or , introduce additional delays, which can range from minutes to hours depending on network conditions and the number of confirmations required.

- Finality is reached when validators agree on "checkpoint" blocks, requiring a two-thirds majority for validation. Reverting a finalized block would require burning one-third of the total staked ether, making such attacks prohibitively expensive.

- Cosmos achieves near-instant finality through Byzantine Fault Tolerant consensus, finalizing blocks as soon as two-thirds of validators confirm them.

- Employs probabilistic sampling, where validators repeatedly vote until a consensus is reached, achieving sub-second deterministic finality.

Avalanche
Cosmos
Ethereum
Bitcoin
Ethereum (PoS)
Cosmos (Comet BFT)
Avalanche