Katana | Bridging — Agglayer, Vault Bridge & Cross-Chain Routes
Learn how bridging to Katana works across canonical Agglayer infrastructure, productive Vault Bridge assets and additional interoperability protocols.
Bridging is more than asset transfer
Katana supports multiple cross-chain routes. The canonical bridge path connects through Agglayer infrastructure, while productive Vault Bridge flows can add yield strategy behavior to supported assets.
Canonical Agglayer bridge
The canonical route uses Katana’s Agglayer-connected bridge contracts and network identifiers. Developers integrating the canonical bridge should distinguish chain ID from Agglayer network identifiers and should verify contract addresses before sending messages or assets.
Vault Bridge flows
For supported assets, bridging can be tied to productive strategies. That means the asset users receive on Katana may represent capital that remains deployed elsewhere, creating different withdrawal and risk assumptions than a simple lock-and-mint bridge.
Other interoperability protocols
Katana can also integrate third-party cross-chain systems. Each protocol has its own router contracts, message finality, supported assets, security model and failure modes.
Bridge UX
A good bridge interface should clearly show source chain, destination chain, token, amount, expected output, fees, estimated time and whether the route creates a wrapped or productive asset. Users should never have to infer which bridge path is being used.
Bridge safety checklist
Verify source/destination networks, token contract, destination recipient, bridge contract, minimum output and any redemption constraints. For programmatic bridging, handle message status and partial failures explicitly.
Frequently Asked Questions
What is Katana’s canonical bridge?
Katana uses Agglayer-connected canonical bridge infrastructure.
How is Vault Bridge different?
Vault Bridge can keep supported underlying capital productive while users receive corresponding assets on Katana.
Can other bridge protocols connect to Katana?
Yes. Additional interoperability protocols can provide separate routes with their own security models.
What should users verify before bridging?
Source chain, destination chain, token, recipient, route, fees and withdrawal mechanics.