xhavic.io
GitHub (Coming Soon) Whitepaper
Docs / Dual Wallet System

Finality Model

Understanding soft finality, Ethereum finality, escrow finality, and the 7-day challenge period.

Xhavic has multiple finality states. Understanding these is essential for building applications that correctly handle transaction confirmation.

Finality States

StateTimeDescription
Sequenced (soft finality)~200msSequencer has ordered the transaction
Batch posted~60 secondsCalldata posted to Ethereum
L1 confirmed~13 minutesEthereum block confirmed
Challenge period closed7 daysFull finality — no fraud proof submitted

By Wallet Type

Instant Wallet

For Instant Wallet transactions, soft finality (200ms) is sufficient for most DeFi applications. The transaction is practically irreversible because the sequencer has committed to the ordering — re-ordering would trigger fraud proofs.

Secured Wallet

For Secured Wallet transactions, no action should be taken until the 24-hour escrow closes. During the escrow window, authorized signers can reverse the transaction.

StateTimeSafe to act on?
EscrowedImmediateNo — can be reversed
Escrow closed24 hoursYes — finalized
Batch posted24h + ~60sYes
Challenge closed24h + 7 daysMaximum security

Application Guidelines

Application TypeMinimum FinalityRecommended Wallet
DEX tradesSoft (200ms)Instant
Token transfers (small)Soft (200ms)Instant
NFT mintingSoft (200ms)Instant
AI agent operationsSoft (200ms)Instant
Treasury transfersEscrow closed (24h)Secured
RWA settlementL1 confirmed + escrowSecured
L2 → L1 withdrawalsChallenge closed (7d)Either