Blockchains cannot read each other. Every mechanism that appears to move an asset from one chain to another is a workaround, and the workaround is where the risk lives.
Nothing crosses between chains
A blockchain validates only its own transactions. It has no native way to observe balances or events on a separate network with a separate consensus process.
A bridge therefore does not transport an asset. It locks or destroys the original on one chain and causes a representation to appear on the other.
The representation is a distinct token whose value rests entirely on the promise that the original remains locked and redeemable at any time.
The lock creates a concentrated pool
Assets locked in a bridge contract accumulate as more users cross, so the contract holds the combined deposits of everyone who has ever used it.
That pool is a single target with a clearly published balance, which is the reason bridges have historically attracted a disproportionate share of large exploits.
An attacker who can mint representations without a corresponding lock, or release locked assets without burning representations, breaks the relationship the whole design depends on.
Verification models differ substantially
Some bridges rely on a set of external validators who observe one chain and attest to the other, which places trust in that group and its key management.
Others use cryptographic proofs verified on chain, reducing reliance on a trusted group at the cost of complexity and higher transaction expense.
The distinction determines what an attacker must compromise: a signing quorum in the first case, or the proof verification logic itself in the second.
Wrapped assets depend on the issuer
A wrapped token is only as sound as the arrangement backing it, whether that is a smart contract holding reserves or a custodian holding assets off chain.
If the backing fails or the redemption path closes, the wrapped token can trade away from the asset it represents even though nothing changed on the origin chain.
Holders often treat wrapped versions as equivalent to the original, which understates the additional layer of dependency they have taken on.
Smart contract risk compounds the rest
Bridge contracts are complex, hold large balances and interact with multiple chains, which is an unfavorable combination for software that cannot easily be patched.
Audits examine known categories of flaw and do not certify that a contract is safe, a distinction that audit reports state directly in their own language.
These are structural observations about how the technology works rather than assessments of any particular bridge, and none of it constitutes guidance about holding or moving assets.