Editorial policy
The rules this desk holds itself to, written plainly enough that you can check whether a given note follows them.
Sourcing
Claims fall into four categories, and every claim on this site should be identifiable as one of them.
| Type | Example | Standard applied |
|---|---|---|
| Protocol fact | A Solana signature costs a fixed base fee in lamports | Must be checkable in the protocol's own documentation and is linked where practical |
| Documented parameter | A launchpad migration threshold or fee percentage | Stated as documented and changeable, with an explicit instruction to re-verify before budgeting |
| Illustrative math | A worked cost example using round numbers | Labelled illustrative in the figure itself and never described as a measurement |
| Inference | A pattern in a transaction list suggesting automation | The word inference, or an equivalent hedge, appears in the same sentence |
What is banned outright
Never published here
- Invented statistics of any kind, including market sizes, success rates and adoption figures.
- Review counts, star ratings, aggregate rating markup, or testimonials.
- Author personas with fabricated credentials, photographs or biographies.
- Backdated publication dates. Every page carries the real build date and a live modified date.
- Screenshots or figures presented as real measurements when they were constructed for illustration.
- Performance claims about any tool, product or strategy, including ones we link to.
- Price predictions, targets, or anything that functions as a recommendation to buy or sell.
Observation against inference
A large part of writing about this subject involves reading behaviour from public data. That reading is often reasonable and almost never conclusive. Funding patterns, interval regularity and uniform swap sizing can all be produced deliberately or accidentally, and sophisticated automation is specifically designed to avoid producing them.
Accordingly, notes here separate the two. Balances, transaction counts, signer sets and account states are observations. Motive, coordination and intent are inferences. Where a note draws a conclusion about intent, it says so, and it says what would have to be true for the conclusion to be wrong.
Numbers and arithmetic
Illustrative arithmetic is used heavily on this site because it is the fastest way to show why a mechanism matters. Every such example is marked as illustrative inside the figure, uses deliberately round inputs, and describes a hypothetical token. None of it should be quoted as a measurement, and none of it is calibrated to any real market.
Where a figure comes from a protocol, the note says which protocol and what to check. Where a figure has changed historically, the note says that it has changed rather than presenting the latest value it happens to know as permanent.
Commercial links
This site links to a commercial product. The relationship is straightforward and stated here rather than buried: the links are placed deliberately, they are capped in number, and the site may benefit from them.
Three rules apply. First, a commercial link never replaces an explanation; the paragraph around it has to carry information whether or not you click. Second, the surrounding text describes what is on the other side rather than making a claim about results. Third, no note is written for the purpose of hosting a link, and the evaluative note on tooling includes the category's real limitations in the same detail as its capabilities.
External and network links
Links to protocol documentation, explorers and repositories are provided to let you verify claims yourself, and carry a nofollow attribute. Links to other publications in the same subject area are used only when the target genuinely answers the next question raised by the paragraph.
Corrections
Report
Send the page, the sentence and the reason it is wrong. Specificity is what makes a correction fast.
Verify
The claim is re-checked against the protocol, the chain, or the source it was drawn from.
Correct and describe
If the claim is wrong it is corrected. Substantive corrections are described in the note rather than silently overwritten, so a returning reader can see what changed.
Withdraw if necessary
If a note cannot be repaired, it is withdrawn rather than left standing with a caveat attached.
Dates
Every page carries a published date equal to the date it was actually built and a modified date generated at request time. Neither is manipulated to make material look fresher than it is.
Use of automation in production
Drafting and editing tools are used in producing this site. Responsibility for every published claim sits with the desk regardless of how a draft was produced, and the sourcing standards above apply identically to any sentence, however it was written.
Risk
Nothing here is financial, investment, legal or tax advice. Bonding-curve tokens are high-risk instruments and total loss is a normal outcome in this market. Automated trading adds operational risk to market risk. You are responsible for assessing your own jurisdiction, your own exposure, and the legality of anything you choose to do.
Questions about any of the above go to the contact page. Background on scope and method is on the about page.