Executive TL;DR• Interoperability is claimed by nearly every institutional blockchain network and means something different in each claim. The term collapses four genuinely distinct capabilities that have different technical requirements and different maturity levels. • The four layers: message passing (can network A tell network B something), asset portability (can a token move between networks retaining its properties), identity portability (does a verified investor credential remain valid across networks), and compliance continuity (do transfer restrictions survive the crossing). • Most networks claiming interoperability deliver message passing and partial asset portability. Identity portability and compliance continuity the two layers that matter most for regulated securities remain substantially unsolved across the industry. • The compliance continuity problem is the specific reason institutional tokenized securities have been slower to become cross-chain than stablecoins and unrestricted tokens. A token that enforces KYC eligibility on its native chain must enforce the same restrictions on any destination chain, or the crossing has created a non-compliant instrument. • For institutional evaluation, the useful question is not whether a network is interoperable but which of the four layers it actually supports, and what happens to compliance enforcement when an instrument crosses networks. |
Ask any institutional blockchain network whether it is interoperable and the answer is yes. Ask what that means specifically and the answers diverge sharply some mean their network can receive messages from other chains, some mean tokens can be bridged, some mean they support a particular cross-chain protocol. These are not the same capability, and for institutions holding regulated securities the differences are consequential rather than semantic.
The Four Layers of Interoperability
Layer 1: Message Passing
The most basic form of interoperability is the ability for one network to convey verified information to another that a transaction occurred, that a state changed, that a condition was met. Cross-chain messaging protocols provide this, and it is the most technically mature layer. Message passing enables coordination between networks without requiring assets to move.
For institutional use, message passing supports meaningful functionality: a settlement instruction on one network triggering an action on another, or a valuation update propagating across chains. It does not, by itself, allow an asset to exist on a different network than where it was issued.
Layer 2: Asset Portability
Asset portability means a token can move from network A to network B and remain economically equivalent. Two mechanisms dominate: lock-and-mint (the asset is locked on the origin chain and a representation is minted on the destination) and burn-and-mint (the asset is destroyed on the origin and reissued natively on the destination).
The distinction matters for institutional risk assessment. Lock-and-mint creates a wrapped representation whose value depends on the bridge contract holding the locked original introducing bridge contract risk that has historically been the largest single category of DeFi loss. Burn-and-mint, where the issuer participates in the process, avoids the wrapped representation entirely but requires issuer involvement rather than permissionless bridging.
Layer 3: Identity Portability
This is where institutional interoperability begins to diverge sharply from general blockchain interoperability. If an investor completes KYC verification and receives an on-chain credential on network A, does that credential remain valid and verifiable on network B?
For most current implementations, the answer is no. Identity registries are typically deployed per network, meaning an institutional investor verified on one network must complete verification again to participate on another. This is the compliance equivalent of the reconciliation problem duplicated effort producing the same result, with no mechanism to recognise that the work has already been done.
Layer 4: Compliance Continuity
The hardest layer, and the one that determines whether institutional tokenized securities can be genuinely cross-chain. A compliance-enforced token restricts transfers to verified eligible holders on its native network. When that token moves to a different network, the restrictions must move with it otherwise the crossing has produced an instrument that looks like the original but does not enforce the rules making it legally compliant.
This is not a theoretical concern. It is the specific reason regulated tokenized securities have been slower to become genuinely cross-chain than stablecoins and unrestricted tokens, which have no transfer restrictions to preserve.
Where Each Layer Stands
| Layer | Maturity | Primary Mechanism | Institutional Gap |
|---|---|---|---|
| Message passing | Mature | Cross-chain messaging protocols with validator or oracle attestation | Trust assumptions vary significantly between protocols |
| Asset portability | Developing | Lock-and-mint bridging; burn-and-mint native issuance | Bridge contract risk in lock-and-mint; issuer involvement needed for burn-and-mint |
| Identity portability | Early | Per-network identity registries; emerging portable credential standards | Investors must typically re-verify per network |
| Compliance continuity | Largely unsolved | Destination-chain compliance module deployment; cross-chain registry queries | No widely adopted standard; case-by-case implementation |
What Institutional Interoperability Actually Requires
- Explicit statement of which layers are supported — a network claiming ‘full interoperability’ without specifying whether identity and compliance travel is making an incomplete claim.
- Documented trust assumptions for message passing — who attests that a cross-chain message is valid, and what happens if that attestation mechanism fails or is compromised.
- Clear asset portability mechanism — whether crossing produces a wrapped representation with bridge dependency or a natively issued instrument on the destination chain.
- A defined answer for identity — whether verified credentials are recognised across networks, and if not, what the re-verification process requires.
- Compliance enforcement on the destination chain — a documented mechanism ensuring transfer restrictions apply after crossing, not merely before it.
- Reversibility and failure handling — what happens if a cross-chain transfer fails partway, and whether assets can be recovered or become stranded.
The Realistic Near-Term Model
For institutional tokenized securities, the pragmatic model emerging is not universal permissionless interoperability but selective, issuer-involved cross-chain issuance. Rather than allowing a token to be bridged anywhere by anyone, the issuer designates which networks the instrument may exist on, deploys compliance infrastructure on each, and controls the mechanism by which the instrument moves between them.
This is less elegant than the permissionless ideal and considerably more workable under current regulatory requirements. It preserves compliance enforcement by ensuring every network hosting the instrument has the necessary infrastructure, at the cost of requiring issuer participation in what would otherwise be a permissionless operation.
Frequently Asked Questions
1. What are the four layers of blockchain interoperability?
Message passing (conveying verified information between networks), asset portability (moving tokens between networks), identity portability (whether verified credentials remain valid across networks), and compliance continuity (whether transfer restrictions survive the crossing).
2. Why is compliance continuity the hardest layer?
A compliance-enforced token restricts transfers to verified holders on its native network. When it moves to another network, those restrictions must move with it otherwise the crossing produces an instrument that resembles the original but does not enforce the rules making it legally compliant. No widely adopted standard yet solves this.
3. What is the difference between lock-and-mint and burn-and-mint bridging?
Lock-and-mint locks the asset on the origin chain and mints a wrapped representation on the destination introducing dependency on the bridge contract holding the original. Burn-and-mint destroys the asset on the origin and reissues natively on the destination, avoiding wrapped representations but requiring issuer involvement.
4. Why have stablecoins become cross-chain faster than tokenized securities?
Stablecoins generally have no transfer restrictions to preserve. Tokenized securities enforce eligibility rules that must survive the network crossing a requirement stablecoins do not face, and the specific reason regulated instruments have been slower to go cross-chain.
5. What is the realistic near-term interoperability model for institutional securities?
Selective, issuer-involved cross-chain issuance rather than universal permissionless bridging. The issuer designates which networks the instrument may exist on, deploys compliance infrastructure on each, and controls movement between them preserving compliance enforcement at the cost of permissionless operation.
Blockmaze and Institutional Interoperability
The interoperability requirements this article identifies — identity and eligibility portability across networks, atomic cross-chain settlement without custodial bridges, standards-aligned token formats, and governance frameworks that can coordinate across protocol boundaries — define the infrastructure challenge that institutional blockchain adoption actually requires solving. Blockmaze’s architecture addresses these requirements at the design level rather than retrofitting interoperability onto an existing single-network model. The BMZ20 and BMZ3643 token standards are aligned with ERC-3643’s identity-binding architecture, enabling eligibility verification that travels with the instrument rather than being stored only on the issuing network. The compliance-enforced transfer logic that identity-verified allowlists implement applies across network contexts: a wallet that has not cleared eligibility cannot receive a tokenised instrument regardless of which chain the transfer originates from. For institutional participants who require not just a compliant network but a network whose instruments can interact with the broader institutional blockchain infrastructure that is taking shape across DTCC, JPMorgan, and regulatory-authorised settlement systems, Blockmaze’s standards alignment is the starting point.
Disclaimer: This article is for informational purposes only and does not constitute financial or legal advice. Readers should conduct their own research and consult with qualified professionals before making any investment or business decisions.