DEV Community

Cover image for A Synthetic Token Is Only as Honest as Its Oracle
Azalea
Azalea

Posted on

A Synthetic Token Is Only as Honest as Its Oracle

On a Sunday this November, Nvidia's board announced a review of its CEO. Stock markets were closed. Traders who wanted to act on the news went to Hyperliquid instead, and within about half an hour roughly $200 million in Nvidia perps changed hands. When Nasdaq opened on Monday, the stock fell around 7%, catching up with where the perps had already gone.

That's the pitch for synthetic assets in one story: price exposure to almost anything, around the clock, from a crypto wallet. It also raises a question that's easy to skip. On a Sunday, with the real market closed, where does the price inside the contract come from?

Three parts, one of them outside the chain

A synthetic token doesn't hold the asset it tracks. ChangeNOW's explainer on synthetic crypto assets breaks the mechanics into a few steps:

1. You lock collateral       → e.g. $150 in ETH
2. The contract mints        → $100 worth of a synthetic gold or stock token
3. An oracle reports prices  → the contract values your position
4. Collateral ratio too low  → the contract liquidates automatically
5. You burn the token        → the contract returns collateral minus fees
Enter fullscreen mode Exit fullscreen mode

Steps 1, 2, 4 and 5 happen on-chain, where you can read the code and check the balances. Step 3 doesn't. The oracle is a bridge to the outside world, and everything else in the contract trusts whatever comes across it.

So when people ask what backs a synthetic token, "collateral" is only half the answer. The other half is "whoever controls the price feed, and how carefully the contract checks it."

The contract can work perfectly and still pay out a billion

The best-known example is old, and still useful.

On June 25, 2019, a price source used by Synthetix started reporting the Korean won at about 1,000 times its real rate. According to Synthetix's own incident write-up, two APIs had separate outages at the same time, and the aggregation logic didn't catch it. A trading bot spotted the gap, converted into sKRW and back into sETH, and made over $1 billion in paper profit in under an hour. The owner agreed to reverse the trades in exchange for a bug bounty.

Nothing in the smart contract malfunctioned. It did exactly what it was told, at a price that was wrong.

In 2026 it's the signer, not the API

The failure modes have moved, but the target hasn't.

In July 2026, the Arbitrum perps exchange Ostium lost about $18 million after an attacker compromised an oracle signer key. With it, they submitted future-dated price reports that made their leveraged trades look profitable, and drained close to a third of the protocol's liquidity.

That pattern matches what security firms keep repeating. In its Q3 report, Hacken recommended widening audits to cover oracles, bridges, custody and signing authorities, because those parts often sit outside the code that actually gets reviewed.

Stale is a failure mode too

A price doesn't have to be fake to be dangerous. It can just be old.

Feeds like Chainlink's publish a new value when the price moves past a deviation threshold or when a heartbeat interval runs out, whichever comes first. That interval differs by feed and by network, from minutes to a full day. Equity feeds only update while the market is in session, which is exactly why a synthetic stock quoted on a Sunday deserves extra suspicion.

A contract that reads the latest answer without checking its age will happily liquidate positions on a price from hours ago. The minimum check looks like this:

function readPrice(AggregatorV3Interface feed, uint256 maxAge)
    internal
    view
    returns (uint256)
{
    (, int256 answer, , uint256 updatedAt, ) = feed.latestRoundData();

    require(answer > 0, "invalid price");
    require(updatedAt != 0, "incomplete round");
    require(block.timestamp - updatedAt <= maxAge, "stale price");

    return uint256(answer);
}
Enter fullscreen mode Exit fullscreen mode

The important part is maxAge. Setting it once for every feed is a common mistake. It should come from each feed's own heartbeat, plus a small buffer, and it needs revisiting when a provider changes that heartbeat. The Chainlink data feed docs list the parameters per feed.

Perps hide a different cost

Perpetual futures give you the same kind of synthetic exposure through a different structure, and they rely on oracles for mark prices and liquidations too. They add one more cost that rarely shows up in the headline: the funding rate. As ChangeNOW's guide to crypto perps explains, it's charged every 8 hours on most large exchanges and every hour on Hyperliquid, and it quietly eats into any position you hold for long.

So with a synthetic token, you're trusting the oracle and the collateral ratio. With a perp, you're trusting the oracle and paying rent for the position.

If you build on synthetic assets

A few checks that would have mattered in every case above:

  • Check freshness per feed. One global staleness threshold is either too strict for slow feeds or too loose for fast ones.
  • Know your market hours. An equity or FX feed that stops updating on weekends isn't broken, but your liquidation logic should know the difference.
  • Sanity-check the value. Compare against a second source or a bounded move since the last update. A 1,000x jump in a currency pair is not a trade signal.
  • Treat signer keys as infrastructure. If a single key can push prices, it belongs in the threat model and the audit scope, alongside the contracts.
  • Have a pause path. When the feed looks wrong, stopping mints, redemptions and liquidations is cheaper than unwinding them later.
  • Tell users where prices come from. "Backed by collateral" means little if nobody can see what decides the price that collateral is measured against.

Synthetic assets are genuinely useful. They let people react to news when traditional markets are closed and reach assets they couldn't otherwise touch. But every one of them inherits the reliability of a feed it doesn't control. The contract is the part everyone audits. The price is the part that decides who gets paid.

Top comments (1)

Some comments may only be visible to logged-in visitors. Sign in to view all comments.