Contact the desk
One inbox, three kinds of message that are genuinely useful, and an honest account of what this desk cannot help with.
Where to write
Everything reaches the same place: [email protected]. There is no contact form on this site, because a form would collect more data than a static publication has any reason to hold. Plain email, with the page URL in the subject line, is the fastest route to a useful answer.
Messages that get a real reply
- Corrections. Quote the passage, state what is wrong, and say how the correct version can be verified. Corrections that point at primary documentation or at a reproducible calculation are acted on quickly. Corrections that assert a different conclusion without a check take longer, because we have to do the check ourselves.
- Mechanism questions. If a piece describes a pool type, a routing behaviour or a fee component in a way that does not match what you observe, that gap is worth writing about. These messages have improved more pages than any other category.
- Coverage requests. Execution questions we have not covered. The more specific the question, the more likely it turns into a page: "how do I decide clip size on a pair with a shallow SOL side" is workable, "write about slippage" is not.
What this desk cannot do
- Recover funds, reverse a transaction, or intervene in anything that happened on chain. Nobody can, and anyone who says otherwise is running a scam.
- Advise on whether to buy, sell or hold anything. The material here is about execution mechanics, not investment decisions.
- Audit, endorse or vouch for a trading tool, bot or venue. We describe how mechanisms work; we do not certify products.
- Review a token, project or launch, or comment on whether a chart looks organic.
- Provide operational support for third-party software linked from this site. Those are separate operators with their own support channels.
A note on unsolicited offers
Offers of paid guest posts, sponsored articles disguised as editorial, link insertions into existing pages, or paragraphs written by a third party are declined without a reply. The link policy on this site is set in the editorial policy and is not negotiable per request, which makes the negotiation short.
Response expectations
This is a small editorial operation, not a support organisation. Corrections with a verifiable check attached are handled first because they affect readers who are reading the wrong thing right now. Coverage requests are collected and reviewed in batches, so a useful suggestion may sit for a while before it appears as a page. If you do not hear back, the message was read but did not need an answer, or it fell into one of the categories above.
If you are starting from zero
A large share of incoming questions turn out to be one of three articles. If your fills keep missing the quote, start with slippage explained. If transactions keep failing, read quote versus fill. If you are trying to work out how much a swap really cost you, the cost breakdown enumerates every line.