Skip to content
OMME
MarketsCommoditiesLaunchRewardsBuybacksApplyDocs
MarketsCommoditiesLaunchRewardsBuybacksApplyDocs
FLYGLDXAGCOPWTINGCORNWHEATSOYCTKCSBLCLHMILKFRIESBURGER
FLYGLDXAGCOPWTINGCORNWHEATSOYCTKCSBLCLHMILKFRIESBURGER
OMMEOnchain Mercantile Memes Exchange
DocsContracts & tokens@OMMExchange ↗
ContentsPrices & updates
01Overview02Commodity coins03Prices & updates04Launching a token05One public pool06Trading with BNB07Fees08Rewards & creator earnings09Platform token10Maintenance & controls11Contracts12FAQ
Contents01Overview02Commodity coins03Prices & updates04Launching a token05One public pool06Trading with BNB07Fees08Rewards & creator earnings09Platform token10Maintenance & controls11Contracts12FAQLaunch a token ↗
Documentation3 / 12

03Prices & updates

Follow a reference price
  1. 01SourceDelayed futures or menu value
  2. 02Validate & normalizeUSD units, time & deviation
  3. 03Publish onchainUpdate the accepted reference
  4. 04Commodity poolAdjust the liquidity positions
A new accepted reference guides commodity liquidity. The Meme pool still sets its own exchange price.
Data sources, heartbeat & outage limits

Where the numbers come from

The current onchain feed uses delayed Databento futures data, normalized to USD per commodity unit. New source observations may be up to 24 hours old when accepted. FRIES and BURGER use OMME-maintained menu values. These references are not live spot quotes or executable prices from those source markets.

When a source stops updating

OMME keeps the last accepted price while waiting for a valid update, including during source outages and market closures. The keeper renews that existing onchain value instead of automatically removing liquidity solely because the source is late. Displayed valuations also retain the last valid data.

The original source timestamp is preserved. An onchain update can therefore be a heartbeat for an older price, rather than a new market observation. New observations still pass timestamp, unit, price and deviation checks before replacing it.

The deployed feed has a one-hour heartbeat limit. If the keeper itself cannot submit updates for that long, operations that read the feed can fail until it recovers. Holding the last price handles source delays; it cannot guarantee execution during a chain, RPC or keeper outage.

←
PreviousCommodity coins
NextLaunching a token
→