Unbacked Mint

An unbacked mint is the creation of wrapped, synthetic or receipt tokens without the corresponding units of the underlying asset entering reserve. It is the terminal failure mode of any issuance system, because the resulting tokens are indistinguishable from legitimate ones to every contract downstream — they can be traded, redeemed, or used as collateral.

The invariant it violates

Every issuance system asserts the same property, whether or not it is written down:

1issued_supply ≤ independently_verified_backing

"Independently" is the operative word. The backing figure must come from a source the issuing path cannot influence. Once the thing being measured can affect the measurement — by populating its cache, supplying its input, or choosing the numeric range it operates in — the invariant stops holding.

How the check fails

Unbacked mints rarely result from a missing check. In the three September 2026 incidents, the relevant control existed and executed in all three cases, failing in a different way each time:

• Bypassed — verification caching returned a false cache hit, so the check never ran (Liquid)
• Fooled — message validation accepted a forged payload it should have rejected (Symbiosis)
• Starved — an unsafe downcast destroyed the liability value before the check read it (Notional V1)

Containment

Because the mint path can fail in ways an audit may not anticipate, unbacked issuance should be bounded independently of whether the validation logic is correct:

• Per-transaction and per-epoch issuance caps, so one validation bug is not unbounded loss
• Reserve reconciliation comparing outstanding supply against custody across every chain
• Circuit breakers keyed to reserve drawdown rate rather than absolute thresholds

The Symbiosis incident illustrates the gap: mint volume was effectively unbounded, and realised loss was limited only by available exit liquidity — a market condition, not a control.