Follow the data path
The Markets page requests the Next.js market endpoint, whose feed adapter reads the retained CryptoTrades Cloudflare Pages data service. That service supplies CoinMarketCap snapshots for Bitcoin, Ethereum, Solana and Chainlink. The frontend is not a direct exchange order book.
The separate service is a production dependency. A frontend deployment alone does not replace it, and a successful page response does not establish that every source is fresh. This draft describes the code and existing configuration; it is not a new uptime or latency measurement.
Evidence: CryptoTrades market and news methodology
Read quote time and retrieval time separately
A quote timestamp identifies the provider observation associated with a price. A retrieval timestamp identifies when the feed obtained a response. Loading a page now does not turn an older observation into a current price.
If either timestamp is absent or outside the adapter’s permitted range, the relevant item is not accepted as a fresh valid observation. Do not subtract retrieval time from your clock and call that exchange latency: the provider and venue collection methods are outside this frontend.
Understand the cache and outage windows
The retained service caches markets for five minutes and news independently by source for fifteen minutes. Its labeled outage snapshots expire after one hour for markets and six hours for news. The Next.js bridge may reuse a successful response for thirty seconds.
The bridge also applies freshness and structure checks. A previously successful response can be reused as stale only within its allowed age and with eligible items. These windows describe implementation choices, not guaranteed refresh intervals or service-level commitments.
| Layer | Markets | News |
|---|---|---|
| Retained source cache | 5 minutes | 15 minutes per source |
| Outage snapshot age limit | 1 hour | 6 hours |
| Bridge reuse | 30 seconds | 30 seconds |
Evidence: CryptoTrades market and news methodology
Missing observations stay missing
A price must be positive and finite. Unsupported assets, duplicate rows, invalid timestamps and malformed records are rejected. A missing percentage change or capitalization is retained as unavailable rather than converted into zero.
If no usable feed remains, the interface reports the unavailable state. A genuine 0% change is different from missing change data. Similarly, a successful HTTP request is different from a complete, validated source response.
Evidence: CryptoTrades market and news methodology
News headlines retain their provenance
The news adapter accepts attributed items from Bitcoin Optech, the Ethereum Foundation Blog and the SEC. It checks source identity, URL origin/path, author, publication and retrieval dates, and the expected license reference before display.
Attribution does not make a headline an independent CryptoTrades investigation. Open the original item, check its publication date and distinguish announcements from evidence of adoption or investment quality. Changes in source licensing or URL structure may require a feed update.
Evidence: CryptoTrades market and news methodology
Use a snapshot within its scope
USD is the reference currency. An aggregate observation can differ from the bid or ask available to a particular account on a particular venue. Nothing in the table models your order size, fees, slippage or asset-transfer costs.
When citing a snapshot, record its source, quote time and retrieval time. For a research study, retain the actual observation window and method rather than treating the current table as historical data. Report suspected issues with the affected asset/source and a public reference.
Sources & method
- CryptoTrades market and news methodology
Checked against the current feed and cache implementation. No uptime or latency study was performed. Checked 2026-10-28.
Continue learning
Found an error? Contact the editorial team with the page and supporting source. Never send private account information.