What a research page must explain
A page should address a distinct question, not simply repeat a keyword with a new asset name. Its calculator should identify units, inputs and the formula being used, while its text provides a worked example and explains where the calculation stops being sufficient.
Default calculator numbers and synthetic samples are examples. Automatically loaded market observations must identify their source and observation time; a request alone does not make a value current. A result must not be called guaranteed, risk-free, independently audited or real-time without evidence supporting that description.
Source selection and freshness
For network and exchange mechanics, primary protocol documentation and official provider documentation are preferred. A source link supports the associated explanation; it does not mean that the publisher endorses BTCMox.
Live-source displays identify the provider and relevant timestamp when available. A page revision date describes an actual editorial or code revision and is not a substitute for a market observation time. If a feed fails, the interface should report the failure instead of silently presenting an example as a live result.
A session heatmap records retrieved snapshots, not a complete exchange event history. Describe accumulation, distribution and pressure scores as their stated proxies. Do not turn a heuristic into a claim of confirmed wallet ownership, hidden inventory, manipulation or a guaranteed future price move.
Comparisons and commercial relationships
Venue comparisons depend on the supported feeds, instruments and explicit assumptions. They do not cover the entire market or certify a provider's solvency. A higher displayed rate alone does not make a provider preferable.
Sponsored content, affiliate links and material commercial relationships must be labelled near the affected content when present. They must not be used to imply that a commercial placement is an independent outcome of the calculation.
Optional paid API access must be described as a separately activated service with its actual terms and limits. Do not claim live checkout, active customers, guaranteed uptime, approved redistribution rights or a running backend merely from the existence of source code or documentation.
Correction requests
Report a suspected error to [email protected] with the page, input values, result and a concise explanation. A source or reproducible calculation helps us investigate. Do not include credentials or unrelated personal records.
A material calculation correction should update the affected explanation and its revision date. Historical results should not be edited to invent successful performance, and a corrected formula must not be presented as proof of future returns.