🤝Enhanced Security

The HUB Bridging Mechanism

The HUB bridging mechanism leverages Ethereum as a central focal point to enhance security and improve routing for users. Rather than relying on direct connections between every chain, users route through Ethereum to bridge assets to other supported blockchains.

When transferring assets from point A to point B, users perform two transactions, with each chain maintaining its own liquidity pool for the asset. Unlike systems with unified liquidity pools, Delta (formerly Syncer) uses separate liquidity pools for each chain path, promoting autonomy and resilience against chain outages. This decentralized approach ensures liquidity is distributed across all chain paths.

However, Delta addresses potential issues from decentralized liquidity by implementing a HUB connected to each path with a single liquidity pool. If two chains are not directly linked to the HUB, users can still route through the HUB (Ethereum) to reach their target destination chain, ensuring flexible and secure bridging.

Referencing Stargate and Instant Guaranteed Finality

Instant Guaranteed Finality ensures that once a transaction is successfully completed on the source chain, funds will be available on the destination chain. This guarantee hinges on having adequate liquidity on the destination chain to prevent withdrawals that could invalidate pending transactions. In a decentralized system, users cannot be solely responsible for maintaining liquidity, as it would limit their ability to freely withdraw funds.

However, achieving Instant Guaranteed Finality through technical means is impractical. Executing a transaction across multiple chains simultaneously is not feasible, and providing native asset liquidity (as opposed to synthetic tokens) requires substantial funding. This limitation makes unrestricted bridging channels difficult to implement.

Delta’s Approach: Secured Guaranteed Finality

Delta's cross-chain bridge takes a different approach with Secured Guaranteed Finality. Instead of guaranteeing that funds are available on the destination chain once the source chain transaction is complete, Delta commits funds on the source chain only after the transaction is successfully processed on the destination chain. This method ensures greater control for users throughout the process.

Delta holds the user's funds on the source chain without affecting the bridge state during the transaction process. The user has the option to either confirm the transaction on the destination chain or revoke it if needed. This gives users the flexibility to cancel and revert their transaction back to the source chain if the situation requires.

When the transaction is confirmed, users can withdraw funds on the destination chain, and liquidity is updated on the source chain. If the destination chain lacks sufficient liquidity due to previous withdrawals, users can choose to leave the transaction pending or revert it to recover their funds. Since no state change occurs until confirmation, Delta ensures that held funds are safely returned to the source chain in the event of a cancellation.

Open and Decentralized

Delta’s cautious and user-centric approach protects funds at the code level while supporting non-curated and user-generated bridging paths. This means Delta can facilitate the bridging of any native asset between two chains without requiring substantial liquidity reserves. By adopting this open model, projects of all sizes can leverage Delta, ensuring that on-chain governance decisions and protocol developments are not limited by liquidity constraints.

Delta’s secured finality model and decentralized approach open up opportunities for users and projects to engage in secure, flexible, and scalable cross-chain transactions while maintaining full control over their assets.