Documentation
Docs31. Bridging to Kortana

31. Bridging to Kortana

Cross-chain asset bridging on Kortana is engineered for maximum security, decentralization, and resistance to systemic bridge exploits.

31.1 Philosophy: No Native Bridge

[!IMPORTANT] Philosophy: No Native Bridge. Kortana does not operate an official multi-sig bridge, relying instead on specialized cross-chain messaging providers (LayerZero, Axelar, Wormhole).

By refusing to operate a monolithic native multi-sig bridge, Kortana eliminates single points of failure and prevents the centralization of multi-billion-dollar liquidity honeypots. Instead, the network relies on specialized, battle-tested cross-chain messaging networks that utilize diverse verification mechanisms (such as decentralized relayer networks, threshold signature schemes, and light client proofs).

31.2 What Each Provider Needs

Cross-chain messaging providers integrating with Kortana deploy their standard smart contract infrastructure directly onto the KEVM:

  • Endpoint Contracts: Receive cross-chain payload messages and verify cryptographic proofs.
  • Gateway Contracts: Lock, mint, or burn bridged assets under the supervision of BridgeMinter.
  • Relayer Nodes: Off-chain validator daemons that monitor Kortana WebSocket feeds and submit execution transactions.

31.3 Wiring a Bridge (Step-by-Step)

Integrating a new bridge provider follows a strict governance authorization process:

  1. Contract Deployment: The bridge provider deploys its verified Endpoint and Gateway contracts to Kortana.
  2. Governance Proposal: An on-chain GovernancePropose transaction is submitted to authorize the gateway address in BridgeMinter.
  3. Quota Configuration: Governance configures the initial hourly minting rate limit and total token capacity.
  4. Liquidity Seeding: Once approved and timelocked, the bridge gateway begins processing deposits and withdrawals.

31.4 Operational Guidance

Bridge operators running relayer infrastructure on Kortana must maintain dedicated relayer accounts funded with native Dinar ($DNR) for paying gas fees.

Relayers should subscribe to the kortanad WebSocket endpoint (wss://ws.mainnet.kortana.xyz/) using eth_subscribe("logs") to detect cross-chain burn and deposit events in real time, ensuring that outgoing transfers are forwarded to destination networks within milliseconds.

31.5 Finality Advantage

Kortana's deterministic 1-block finality provides a massive structural advantage for cross-chain bridges. On legacy networks with probabilistic finality (such as Ethereum PoW or Polygon), bridge relayers must wait for 20 to 128 block confirmations (10–25 minutes) before crediting user deposits to avoid double-spend attacks from chain reorganizations.

On Kortana, once a block receives a BLS12-381 Quorum Certificate, it is mathematically guaranteed to be canonical and permanently immutable. Bridge relayers can safely credit user deposits in approximately 1.5 seconds, providing near-instant cross-chain transfers.


Part VIII — Node Operators & Validators