I am more interested in Dusk Network's planned source of market data than in the phrase "real time."
Dusk and NPEX plan to use Chainlink DataLink for official exchange data and Data Streams for low-latency price updates. That can give DuskEVM applications a feed tied to the venue that produced the information, instead of a price assembled from unrelated crypto markets.
Provenance solves one problem. It does not make the price executable.
An official last trade can be old. A fast update can come from a thin market. A correct reference price can still sit far from the amount available to buy or sell. If a lending or settlement application treats the feed as instant liquidity, it may calculate risk from a number that nobody can actually trade at size.
The data path also needs a failure policy. What does a Dusk application do when the feed is stale, the venue is closed, or a security is suspended? Continuing with the last value may be dangerous. Freezing every action may trap users.
This is why I would watch metadata beside the price: timestamp, market status, source venue, confidence or quality rules, and the depth behind the observation. Smart contracts should reject stale data explicitly rather than letting each developer invent a timeout.
Corporate actions also need adjustments, or yesterday's valid price can become today's misleading input.
The integration is not yet the same thing as live Dusk market activity. I want to see an issued instrument, official updates reaching DuskEVM, and an application responding correctly to both normal and interrupted feeds.
Dusk can bring authoritative exchange information onchain. The stronger milestone is making applications understand what that information can support.
A price feed tells a contract what was observed. It should never be mistaken for a promise that the market will fill the next order.
@Dusk_Foundation $DUSK #dusk
$ACE $CYS
Dusk and NPEX plan to use Chainlink DataLink for official exchange data and Data Streams for low-latency price updates. That can give DuskEVM applications a feed tied to the venue that produced the information, instead of a price assembled from unrelated crypto markets.
Provenance solves one problem. It does not make the price executable.
An official last trade can be old. A fast update can come from a thin market. A correct reference price can still sit far from the amount available to buy or sell. If a lending or settlement application treats the feed as instant liquidity, it may calculate risk from a number that nobody can actually trade at size.
The data path also needs a failure policy. What does a Dusk application do when the feed is stale, the venue is closed, or a security is suspended? Continuing with the last value may be dangerous. Freezing every action may trap users.
This is why I would watch metadata beside the price: timestamp, market status, source venue, confidence or quality rules, and the depth behind the observation. Smart contracts should reject stale data explicitly rather than letting each developer invent a timeout.
Corporate actions also need adjustments, or yesterday's valid price can become today's misleading input.
The integration is not yet the same thing as live Dusk market activity. I want to see an issued instrument, official updates reaching DuskEVM, and an application responding correctly to both normal and interrupted feeds.
Dusk can bring authoritative exchange information onchain. The stronger milestone is making applications understand what that information can support.
A price feed tells a contract what was observed. It should never be mistaken for a promise that the market will fill the next order.
@Dusk_Foundation $DUSK #dusk
$ACE $CYS