Canonical bridge

Canonical bridge is the bridge that a project’s team or DAO designates as the primary route for asset transfer. When multiple bridges exist, the market and integrators converge on one wrapped representation as the standard — the canonical version.

Why the concept matters

In practice, a single asset can have five to ten different wrappers on the same target chain — each bridge (Wormhole, LayerZero, deBridge, Multichain before its collapse) issues its own. Without a canonical pick, DeFi fragments: liquidity is spread, users get confused, and attackers gain options.

A canonical bridge delivers:

• One wrapper everyone knows and accepts.
• Deep liquidity in one venue instead of ten thin ones.
• Minimal confusion for end users.
• Legitimacy — usually backed directly by the project’s team or foundation.

Who decides

• The project team or its DAO via vote.
• De facto market consensus: whichever wrapper attracts most liquidity.
• Sometimes exchanges: an asset is listed via a specific bridge and that becomes canonical by default.

Canonical bridges in the TON ecosystem

• TON Bridge (BNB / Ethereum) — TON Foundation’s official bridge. wTON via this bridge is canonical for most integrations.
• USDT. Native USDT jetton is issued by Tether directly — not a “bridge” in the usual sense, but the canonical USDT on TON.
• For other assets the canonical status is unstable: different DEXs back different wrappers, liquidity stays fragmented.

Risks of a canonical bridge

Being designated “official” does not erase risk:

• If the canonical bridge breaks, every piece of wrapped-asset liquidity is in the blast zone.
• A team can switch canonicals — legacy holders are stuck with a deprecating wrapper.
• A canon without audit and reserves is policy, not safety.

When dealing with wrapped assets always check which bridge issued them. The canonical version is usually safer — but not automatically; the trust model of the specific bridge still matters.