Editorial policy
The rules this desk works to, written down so that readers can hold us to them. They exist because the category we cover is unusually full of fabricated evidence, and the only useful response is to be specific about what we will and will not do.
Policy summary
Sourcing
Technical claims are checked against protocol documentation, program interfaces and observable chain behaviour. Where a behaviour can be observed by a reader, we prefer to describe how to observe it rather than to assert a figure that would have to be trusted. We do not treat other articles in this niche as sources, because the same errors circulate through them unchecked.
External links to primary sources such as protocol documentation and block explorers are used where they support a specific claim. They carry a nofollow attribute and open in a new tab. We link out to documentation rather than paraphrasing it when the exact wording matters.
Numbers
Three categories are permitted and there is no fourth.
- Protocol constants, such as the slot target, the blockhash validity window, lamport denomination or transaction size limit. These are stated as constants and are checkable against documentation.
- Illustrative arithmetic, explicitly labelled as such, with every input visible so that a reader can substitute their own. Illustrative figures are chosen to show the structure of a calculation, never to imply a typical result.
- Attributed figures from a named public source, with the source linked.
Explicitly banned: invented statistics, performance figures, win rates, backtests, volume totals we cannot verify, and any number presented as an industry fact without a source. If a number would be persuasive and we cannot support it, it does not appear.
Why we publish no vendor scores
Rating a trading platform requires observing its execution, which is precisely the part that is private. From outside, we can assess documentation, fee models, custody arrangements, transparency and exit paths. We cannot assess routing quality, landing performance or reliability under stress without operating the platform at scale with real capital over a long period.
Publishing a score built only on the observable part would give it authority it has not earned, and readers would reasonably assume it covered the unobservable part too. So we publish the framework instead, weighted and with explicit anchors, and leave the scoring to the person whose money is at stake. Where we use a named platform as an example, we say what the example demonstrates and we do not attach a rating to it.
Commercial links
A small, fixed number of links on this site point to a commercial automation platform and may be commercially beneficial to us. The ceiling is six across the whole site: the home page hero, the home page console section, the footer, and three article references where a concrete implementation makes an abstract class tangible.
Rules we apply to them. Each one sits in a paragraph that explains what the reader will find on the other side, never a sales claim, never a price, never a performance figure. No article carries more than one. Security pages carry none at all, because a page about custody should not be selling anything. And the evaluation framework applies to linked platforms exactly as it applies to any other, including the refusal to publish a score.
Links to other sites
We link to other publications when their page answers the precise next question a paragraph raises, and not otherwise. We do not run reciprocal link arrangements, do not participate in link exchanges, and do not sell links. If a link here stops being useful, it gets removed rather than kept for its own sake.
Authorship and disclosure
Pages are published under the desk byline. We do not invent named authors, credentials, photographs or biographies. Where drafting tools are used in preparing material, the responsibility for every published claim remains with the desk, and no page is published without the technical claims being checked against primary documentation.
Dates
Publication dates are real build dates. Modification dates change when a page changes. We do not backdate pages to appear established, and we do not refresh a date without a substantive edit behind it.
Corrections
Send a correction with the page, the specific claim and a reference. Verified factual errors are fixed promptly, and where the correction changes the meaning of a section we say what changed rather than editing silently. Typographical fixes are made without a note. Disagreements about interpretation are not corrections, but they are welcome, and they occasionally result in a paragraph being rewritten to state a trade-off more honestly.
We do not remove accurate material because a company objects to it, and we do not add material because a company requests it.
Scope limits
This desk does not publish trading strategy, signals, price opinions or token analysis. It does not offer financial advice of any kind. Automation moves real funds on a public ledger, every class of tool described here can lose money through market movement, execution failure or operator error, and no page on this site should be read as a suggestion to trade.