Canonical vs Third-Party Bridges
Definition
A canonical bridge is the route between chains that the token's issuer, or the destination network itself, designates as official: the issuer recognizes the token it produces as its own, typically because the issuer mints it natively on the destination chain or authorizes the bridge to do so. A third-party bridge is an independent service that locks the original token and issues its own wrapped token on another chain; that wrapped token is the bridge operator's claim, not the issuer's security. The two can look identical in a wallet and carry the same name. They differ in who stands behind them: the issuer for a canonical token, the bridge for a third-party wrapper. For tokenized securities this decides redemption rights, distributions, eligibility enforcement and what happens if anything goes wrong on the bridge.
Why it matters
The same ticker on two chains can be two different instruments. When an issuer extends its token to a new chain itself, holders there own the issuer's security. When a third party bridges it, holders own the bridge's promise. In normal markets the two trade at the same price; in a bridge failure, an issuer dispute or a compliance action they can diverge completely, and only one will be redeemed. For tokenized funds and notes, where redemption at NAV is the anchor of value, holding the issuer's own token on a chain it supports is the conservative choice, and the issuer's list of official contract addresses is the document that settles the question.
Common misconceptions
- •Same name and ticker do not mean same issuer. Anyone can deploy a token with a fund's name.
- •Canonical does not mean risk free. The messaging or minting layer remains a dependency.
- •A third-party wrapper is not illegal or worthless. It is a different claim, on a different party.
- •Issuer distributions do not reach wrappers automatically. The bridge must pass them through, if it does at all.
- •Recognition can change. Issuers add and remove supported chains; check the current list.
Technical details
Side by side
Who stands behind it: canonical, the issuer; third-party, the bridge operator and its validators.
Register: canonical tokens are entries on the issuer's register; third-party wrappers are not, the bridge contract is the registered holder of the locked originals.
Redemption: canonical, with the issuer for eligible holders; third-party, unwrap with the bridge first.
Compliance: canonical tokens carry the issuer's allowlist and freezes; wrappers may not.
Failure: canonical, issuer's problem to correct; third-party, wrapper holders may bear the loss.
Examples from AltStreet's reviews and markets
Ondo: Ondo Bridge, cross-chain mint and burn through LayerZero; USDY transferable across Ethereum, BNB Chain, Solana and HyperEVM.
Franklin FOBXX: the transfer agent records shares on several networks and publishes official BENJI contract addresses network by network.
Superstate: share counts published for each supported network and book entry, which identifies the recognized supply.
USDC: Circle's cross-chain protocol burns on the source chain and mints native USDC on the destination, rather than wrapping.
Checklist
Find the issuer's official contract list for the chain you will use.
Prefer issuer-minted tokens on supported chains for anything you may need to redeem.
If using a wrapper, identify the bridge, its verification method and its record.
Confirm whether distributions and corporate actions reach your version.
Know the route back to the issuer's own token and what it costs.
How investors apply the term
Investors usually apply this term by tying the definition back to the controlling documents and then asking which cash flows, rights, restrictions, or valuation assumptions it changes. A useful review looks at the term alongside fees, leverage, liquidity, reporting frequency, and manager discretion rather than treating it as a standalone concept.
The practical diligence test is simple: identify who benefits if the assumption is wrong, who has control when conditions change, and what evidence the investor receives after closing. Terms that cannot be reconciled to documents, cash movements, and monitoring data should be treated as marketing shorthand until proven otherwise.
Frequently asked questions
- Does a bridged token have the same redemption rights as the original?
- Only if the issuer recognizes it. A token minted on the destination chain by the issuer, or by a bridge the issuer authorizes, is normally the same security with the same rights. A third-party wrapper gives its holder a claim on the bridge to release the original token; the issuer will usually redeem only the original, and only for eligible holders.
- How do I tell which version I hold?
- Compare the token's contract address on that chain with the issuer's published list of official addresses. If the address is not listed, or the token was minted by a bridge contract the issuer does not name, it is a third-party wrapper. AltStreet's Franklin review found that Franklin published BENJI contract addresses for eight of the networks in its timeline but none for BNB Chain, which shows why the list, not the token name, is the test.
- What are examples of canonical bridging?
- Issuer-run burn-and-mint: Ondo's bridge moves its tokens between chains by burning on one and minting on the other through LayerZero messaging. Stablecoin issuer protocols work the same way for USDC, with Circle burning on the source chain and minting native USDC on the destination. Layer 2 networks also have canonical bridges to their base chain, often with withdrawal challenge periods.
- Why would anyone use a third-party bridge?
- To reach a chain the issuer does not support, or to move faster or more cheaply than the canonical route. The cost is a new counterparty and a token the issuer may not recognize.