10-19-2026 
|
Getting your Trinity Audio player ready...
|
TL;DR: Tokens don’t literally move across blockchains. Cross-chain systems lock, burn, mint, or release assets while keeping separate ledgers synchronized. The challenge lies in verifying that each network reflects the same underlying claim without creating duplicates.
Key takeaways:
- Cross-chain token transfers do not move tokens between blockchains; they coordinate state changes (lock, burn, mint, release) across separate ledgers.
- Duplicate-asset risk occurs when a single asset is recorded on multiple ledgers without reliable verification.
- Lock-and-mint bridges issue tokens on a destination network as receipts for assets locked on the source network.
- Burn-and-mint bridging reduces custody risk but still requires the destination network to verify that tokens were validly burned, final, and correctly authorized for minting.
- Every cross-chain bridge must rely on a trusted verification mechanism, such as a centralized operator, multi-sig group, oracles, or validators, and each choice introduces security assumptions.
- Tokenized real-world assets raise the stakes for cross-chain interoperability because ownership, custody, and supply must remain consistent across every network where the asset exists.
Interoperability is often defined as the ability to move tokens between networks.
While that’s close to the mark, it’s also a little misleading, because tokens do not leave one blockchain and arrive on another. Instead, a cross-chain system changes the state of one ledger and updates the other.
Depending on the architecture of the blockchains and bridges involved, tokens may be locked on the original network and minted elsewhere, burned on one chain and reissued on another, or released from existing liquidity on the destination network.
The difficult part isn’t making the second part of the transaction happen—it’s proving that the first part happened correctly.
Tokens don’t actually cross blockchains
Imagine Alice owns 100 tokens on Network A, and she wants to use them on Network B.
In a lock-and-mint system, her 100 tokens would be locked on Network A, and 100 corresponding tokens would be reissued on Network B. Chainlink’s Cross-Chain Interoperability Protocol uses this kind of architecture in some implementations.
From Alice’s point of view, the tokens have moved. However, from an accounting perspective, something different has happened behind the scenes.
The original 100 units still exist on Network A, though they’re supposed to be inaccessible, and another 100 units exist on Network B representing the same economic claim.
The entire system depends on one condition: the 100 tokens locked on Network A can’t be used. If they can, there are 200 claims against 100 units of value. That is the core verification problem.
One asset, one truth, two ledgers
Every blockchain maintains its own state. Network A knows what happened on Network A, Network B knows what happened on Network B, and so on.
Neither automatically knows whether an event on another network is valid. Therefore, a cross-chain system requires a trusted mechanism that allows Network B to accept a statement about Network A. Such a statement might say 100 tokens were locked or 100 tokens were burned.
Once Network B accepts such a statement, it can automatically issue 100 tokens or their equivalent value. This means the bridge is doing more than moving assets—it is transmitting a claim about the state of one ledger to another.
The total legitimate economic claim must remain consistent even when representations exist across multiple networks, and the system is responsible for ensuring this.
Lock-and-mint means trusting the lock
Lock-and-mint is easy to visualize.
The representation on Network B is effectively a receipt for assets held on Network A. Its value depends on the original assets remaining locked.
If the bridge contract is compromised, the lock is broken, or the original assets are released improperly, the tokens on Network B may still exist, but their backing no longer does.
The history of bridge hacks shows that this isn’t a hypothetical risk. The catastrophic financial damage in the wake of these hacks is easily verifiable.
Burn-and-mint changes the mechanics, not the problem
Burn-and-mint removes the need to leave the original assets inside a digital lockbox.
In this case, tokens are ‘burned’ or destroyed on Network A, and the equivalent number is issued on Network B. This can eliminate some of the risks associated with custody, but it doesn’t solve the verification problem.
Network B still needs to know whether the burn was valid, if the correct number of tokens were burned, whether the event was final, who authorized the destination mint, etc.
If an attacker can convince Network B that tokens were burned when they were not, they can duplicate the supply.
The need for a trusted middleman
Who or what should Network B trust to make statements about Network A?
Bridge architectures differ significantly in their answer to that question. Some might trust a centralized operator, another might trust a multi-sig group, and another might trust oracles or validators.
All bridge systems must decide whom to trust regarding the state of the corresponding network. All interoperability solutions require answers, all answers introduce assumptions, and all assumptions introduce vulnerabilities.
Tokenization turns interoperability into an accounting problem
These issues have serious real-world consequences when tokenized financial assets enter the equation.
For example, imagine a tokenized treasury security. If it exists on one ledger, there’s an authoritative record of its state. However, if it exists across five ledgers, someone or something must maintain consistency among them.
When questions of ownership, custody, and control of real economic value are on the line, questions about interoperability are no longer abstract or hypothetical. There are costly consequences to mistakes and system failures.
As tokenized real-world assets move into production, the cost of being wrong will increase sharply.
Interoperability is ultimately about shared reality
Bridges and interoperability solutions can solve problems as long as multiple blockchains and digital ledgers exist.
However, it’s important to be clear about what they’re doing. They are not moving tokens from one network to another. Instead, they are coordinating state changes across multiple networks and trying to keep those changes economically consistent.
Cross-chain interoperability isn’t merely about moving assets, but about convincing independent digital ledgers to agree on a shared reality.
FAQs:
Do tokens actually move between blockchains?
No. Most cross-chain systems lock, burn, mint, and release tokens on different networks. The user experiences this as a transfer, but the system is coordinating state changes across multiple ledgers.
What is lock-and-mint bridging?
Lock-and-mint bridging locks tokens on the source network and reissues new ones on the destination network. This system depends on the original tokens remaining locked.
What is burn-and-mint bridging?
Burn-and-mint destroys tokens on the source network and creates the equivalent supply on the destination network. This reduces some custody requirements, but reliable verification is still required.
Why can cross-chain interoperability create duplicate asset risk?
Cross-chain systems can create problems if the same digital asset is represented on multiple ledgers without reliable synchronization. Verification mechanisms are needed to ensure tokens locked, burned, minted, or released across networks still correspond to the same underlying economic claim.
Why does tokenization make blockchain interoperability more important?
Tokenized real-world assets can represent valuable claims. If the same asset is represented across several networks, systems need reliable ways to keep ownership, supply, settlement, and other states consistent across them.
Watch | Tokenization on Public Blockchain: Transforming RWAs and Finance
