Bridges and cross-chain risk

Chains cannot see one another. An asset on one chain cannot simply appear on another, so bridges construct the appearance: lock the original somewhere, issue a representation elsewhere.

The usual mechanism

You deposit an asset into a contract on the source chain, which locks it.
Some party observes that deposit and attests to it.
A contract on the destination chain issues a wrapped token representing the locked asset.
Reversing the process burns the wrapped token and releases the original.

Fact

A wrapped asset is a claim on the bridge, not the asset itself
Wrapped bitcoin on another chain is not bitcoin. It is a token whose value depends entirely on the bridge holding the real thing and honouring redemption. If the locked pot is stolen or the operator fails, the wrapped token becomes a claim on nothing while continuing to exist and trade.

Why bridges are attacked

Concentration. A large pool of assets sits at a single address. The reward for a successful attack is the whole pot.
Complexity. Code must interpret one chain's state correctly on another, with different finality assumptions on each side. More moving parts than almost anything else in the field.
Trusted validators. Many rely on a set of signers, secured by a threshold of keys. Compromise enough of those keys and you can mint from nothing.
Finality mismatch. Accepting a source-chain deposit before it is truly final allows the deposit to be reversed after the destination mint has already happened.

Interpretation

Several of the largest thefts in this field's history have been bridge exploits
That is not because bridge developers are careless. It is because a bridge combines the largest available prize with the hardest available problem, and because the security of the whole arrangement reduces to the weakest of the two chains plus whatever validator set sits between them. It is structurally the most attractive target in the entire system.

The safer designs

Native issuance. The issuer of an asset mints it directly on several chains and honours redemption on each. No locked pot, and it requires an identifiable issuer — which is why it works for stablecoins and not for bitcoin.
Light-client bridges. The destination chain verifies the source chain's consensus itself, rather than trusting a signer set. Far better security properties, far harder to build, and limited to compatible chain pairs.
Canonical layer-2 bridges. The official bridge of a rollup inherits the settlement guarantees of the chain beneath it, which is a much stronger position than a general-purpose third-party bridge.

Practical guidance

Do not leave assets bridged longer than you need them there. Exposure is a function of time.
Prefer a rollup's canonical bridge over a third-party one, even when it is slower.
Understand what backs any wrapped asset you hold, and who could take it.
Sending to the right address on the wrong chain is a common and usually permanent loss. Check the network as carefully as the address.

The general rule for this whole topic: every bridge adds a trust assumption that neither chain had on its own. Fewer hops is better, and no hop is best.

Education, not advice. These lessons explain how things work. They do not tell you what to buy, and Wealth Signal does not publish recommendations. Full disclaimer.