Editorial Policy
This page sets out what the desk treats as a fact, what it treats as an inference, how a note gets corrected, and what commercial relationships exist behind the links on this site.
Sourcing
Claims on this site fall into three categories and each is handled differently. Protocol mechanics come from Solana's public documentation and from behaviour reproducible against a public endpoint; where a note states one, a reader should be able to verify it independently. General system-design patterns come from established engineering practice, and the note argues for them rather than asserting them. Everything else is inference, and inference is labelled in the text.
The desk does not have privileged access to any provider, validator or product. When something cannot be verified from public material, the note says so instead of presenting a plausible guess. Several answers on this site end with an explicit statement of what is unknown, and that is a deliberate output of this policy rather than an oversight.
What the desk will not assert
- How any specific product is implemented internally. Products are described by what they expose to a user.
- Performance figures, landing rates or cost outcomes for any tool, including ones the site links to. The desk does not operate engines and has no results to report.
- Numbers that cannot be traced to a protocol constant, a named public source, or arithmetic whose inputs are supplied in the text.
- Predictions about network conditions, fee levels or market behaviour.
Numbers and arithmetic
Where a note works through a calculation, the calculation is introduced as illustrative and its inputs are stated. The purpose of that arithmetic is to show which quantity constrains which component, not to predict what a run will cost or produce. Readers should substitute their own measurements, and the notes say so at the point the arithmetic appears.
Protocol constants are stated as constants and are checkable. Where a constant could change with a network upgrade, the note frames it as the current documented value rather than as a permanent property.
Corrections
When a note is found to be wrong, the passage is rewritten rather than annotated, and the change is treated as a version of the page rather than as an admission buried in a footnote. Substantive corrections, meaning a change that alters a design conclusion or a protocol claim, are described in the note itself where the correction affects how the surrounding argument should be read.
Typographical fixes, clarifications and reordering are made without ceremony. The dateModified value in each page's structured data reflects the most recent change, and the publication date is the real build date. No date on this site is backdated, and no note is presented as older or more established than it is.
Corrections can be sent through the contact page. The desk would rather receive a specific, checkable objection than a general one, and protocol corrections are the highest-value reports it gets.
Outbound links
Two kinds of outbound link appear on this site. Links to public documentation and reference material exist to let a reader verify a claim without taking the desk's word for it, and they are marked so that search engines do not treat them as endorsements. Links to a commercial console appear where a paragraph is genuinely about a tool of that kind, and they are ordinary editorial links.
The desk states plainly that it may receive a commercial benefit from traffic sent to that console. It does not audit that console's results, does not operate it, has no visibility into its implementation, and does not present it as tested. Nothing on this site should be read as a recommendation that a reader should run an engine at all; the notes describe how such systems are engineered, which is a different claim.
Independence of the technical material
No commercial arrangement changes what a note says about how something works. If a design pattern is weak, the note says so regardless of who uses it. If a mechanism is unverified, no amount of relevance to a linked product turns it into a verified one. Where those two things ever come into conflict, the technical claim wins and the link is removed rather than the sentence softened.
Scope and limits
This is an engineering publication. It does not offer financial, legal or tax advice, and it makes no claim about whether any particular activity is appropriate, permitted or wise in a given jurisdiction. Readers are responsible for their own compliance, their own keys and their own consequences. A signed transaction on this chain is final, and no article can undo one.