Skip to content

On-chain synthetic assets

A practical, fact-checked guide to on-chain synthetic assets: how collateral, oracles, minting, redemption and liquidation create price exposure, and where the legal, technical and market risks remain.

Updated

For educational purposes only; not investment advice. Investing may result in loss.

Direct answer

An on-chain synthetic asset is a token or accounting position designed to track the value of another asset, index or rate without giving the holder the same legal claim as direct ownership. A protocol may create that exposure by locking collateral, reading an external price through an oracle, and allowing minting, trading or redemption under programmed rules.

The label does not tell you how safe or how redeemable the instrument is. Some systems are over-collateralized debt positions; others rely on pooled liquidity, derivatives, centralized custodians or governance-controlled parameters. Check the chain, contract, collateral, oracle, redemption path and controller before comparing two products.

Synthetic exposure can be useful for access, composability or shorting, but it is not a substitute for the underlying asset. A token that tracks gold, an equity index or a foreign currency may provide price exposure while providing no ownership, voting, custody or bankruptcy claim over that reference asset.

How it works

The typical lifecycle is: deposit collateral, verify a price and risk limit, mint or trade the synthetic, then redeem or liquidate the position. A simplified accounting identity is synthetic value ≈ reference price × units; the identity describes exposure, not a guarantee that the market price will track perfectly.

Collateralization ratio = collateral value ÷ debt value. If the ratio falls below a protocol threshold, keepers or other agents may liquidate collateral to cover the debt. The result depends on the oracle’s update rules, liquidation incentives, fees, slippage, liquidity and the authority that can change parameters.

Oracles are a separate trust boundary. A decentralized feed can reduce dependence on one publisher, but it cannot remove bad-data, latency, network-congestion or governance risks. Read the feed’s heartbeat, deviation threshold, decimals and fallback behavior, and verify which contract address consumes it.

Example

Suppose a protocol accepts collateral and mints a token intended to follow gold. If the oracle reports a gold price of P and the position contains Q units, the reference value is P × Q. A trader can gain or lose exposure to gold without holding bullion, while the protocol still has to maintain collateral, liquidity and a working exit route.

A review should trace one real transaction: identify the contract and block, record the oracle answer, calculate collateralization before and after the trade, and include gas, fees and slippage. Then test a stressed case such as a fast price move, a delayed oracle update or a congested liquidation auction. A successful small transaction proves only that one path worked at one moment.

Risks

The main risks are depeg or tracking error, under-collateralization, oracle failure, liquidation losses, thin liquidity, smart-contract bugs, privileged upgrades and custody or counterparty failure. A wrapper or synthetic token can also create a different legal and tax position from the asset it references.

Market price is not the same as redemption value. Check who can mint and burn, whether redemption is permissionless, what fees and minimum sizes apply, and whether a pause, emergency shutdown or governance vote can block exits. Treat advertised yield as a claim to verify, not as proof that the design captures sustainable cash flow.

For a position with a maximum tolerable loss, a simple sizing rule is allowable amount = maximum tolerable loss ÷ stress loss ratio. The stress ratio should include collateral gaps, oracle jumps, liquidation slippage, bridge or exchange outages and the possibility that recovery is delayed or impossible.

Common misconceptions

Myth 1: On-chain visibility means the asset is safe

Public transactions make balances and rules easier to inspect, but they do not fix bad code, bad data, upgrade keys, phishing interfaces or market illiquidity. Verifiability is not a safety guarantee.

Myth 2: A price feed makes the token equivalent to the underlying

An oracle reports a value; it does not transfer ownership, custody or a redemption claim. Tracking can fail during market stress, outages or parameter changes.

Myth 3: Over-collateralization removes liquidation risk

Collateral provides a buffer, not certainty. A rapid move, stale price, auction shortfall or governance change can still leave losses for users or the protocol.

Myth 4: Displayed yield is net, realized income

Quoted yield may include token incentives and omit gas, trading fees, slippage, funding, taxes and exit costs. Rebuild the cash flows in the asset you actually receive and stress-test the exit.

Sources

Navigation

Search the wiki...