Data Methodology
This page is a plain-language explanation prepared for a small informational website, not an audited or third-party-certified methodology document.
Opening-price recording
A fight does not become "Live" until both the meme token and the stock token have a valid, positive USD price recorded for the same activation moment. Both opening prices are written to the database within a single transaction, under one shared UTC timestamp, along with an opening snapshot. If either price cannot be obtained or validated, activation fails and the fight remains "Scheduled" — no partial or estimated opening price is ever used.
If a fight was not actually tracked from an earlier date, we never reconstruct or guess a historical opening price. Such a fight is either started fresh from the current moment, or requires an administrator-supplied, clearly labeled verified opening price.
Percentage-return calculation
Both assets are compared on percentage return from their own opening price, not on nominal price. This is what allows a fraction-of-a-cent meme token to be compared fairly against a $100+ stock token.
If the absolute value of the lead is below 0.01 percentage points, the fight is displayed as a "Dead Heat" rather than assigning a leader.
Price-source selection
Two provider modes are supported:
- DexScreener pair mode: an administrator enters an exact chain ID and DEX pair address for the asset. The system fetches price data server-side from DexScreener's public API for that specific pair only — it never automatically selects an arbitrary or low-liquidity pair on your behalf.
- Manual verified entry: an administrator enters and validates a price directly. Fight pages identify this source as "Manual verified entry" wherever it applies.
Snapshot frequency
Live fights are updated on a schedule controlled by the site's configured cron job (typically every few minutes, depending on hosting configuration), plus an optional manual "Update Prices Now" action available to administrators. A snapshot is only recorded once both sides of a fight have a valid current price in the same update cycle — a partial update (one side succeeding, one failing) is logged internally but never produces a misleading snapshot.
Delayed feeds
If the time since the last successful update exceeds 15 minutes (configurable by the site administrator), the fight is visibly marked "Data Delayed" throughout the site rather than silently showing stale numbers as if they were current.
Manual entries
Manually entered prices are never disguised as automated feed data. They are labeled "Manual verified entry" in the admin interface and on public fight pages wherever the source is shown.
Tokenized stocks vs. underlying shares
A "tokenized stock" referenced on this site is a separate, third-party crypto asset that aims to track the price of an underlying company's shares — it is not the share itself, is not issued or endorsed by the underlying company, and may trade with pricing differences, delays, or liquidity issues relative to the real stock. Ticker Fight has no relationship with the companies whose names or tickers may be referenced by such tokens.
Why values may differ from another charting platform
Small differences versus other charting tools are expected and normal. Causes include: different exact pair addresses being tracked, different snapshot timing, provider-side caching, differences in how thinly-traded pairs are priced, and rounding for display versus the full-precision values stored internally. Ticker Fight always stores full-precision decimal values and only rounds for on-screen display.