Write to [email protected]. That is the only contact route this site publishes, and it goes to the people who write the pages rather than to a queue.
There is no contact form on this site, which is deliberate. A form collects data, needs storage, and creates an obligation to protect it. An email address does none of those things, and it means your message arrives with whatever context you chose to include rather than whatever a set of fields allowed.
Corrections
Corrections are the most useful thing you can send. Solana tooling moves, and a mechanism described accurately last quarter can be wrong now: a default changes, a method is deprecated, a program identifier is superseded, a provider alters a delivery guarantee.
A correction is fastest to act on when it contains three things: the page, the specific sentence or table row, and the source that contradicts it. A link to protocol documentation or to the operator's own reference is ideal. A correction that arrives with a source is usually published the same day it is verified; one without a source has to be researched from scratch and takes considerably longer.
Coverage gaps
If you arrived here with a question and left without an answer, that gap is worth reporting. The most valuable version of this message describes what you were trying to do, what you searched for, and what you eventually had to work out yourself. That last part is what turns a request into an article outline.
The desk cannot cover everything, and some requests fall outside its scope on purpose. Anything about which token to trade, how to interpret a chart as a market signal, or whether a specific project is legitimate is not something this site will write about, regardless of how often it is asked.
What this desk will not do
- Publish measured latency for a provider. Send benchmarks if you like; they will not appear as figures on this site.
- Rank tools or providers. There is no scoreboard here and there will not be one.
- Accept paid placement inside an article. Commercial links on this site are disclosed by placement and are not sold on a per-article basis.
- Give trading advice. No positions, no calls, no view on any token.
- Debug your pipeline. The desk writes general procedures; it does not review individual deployments or code.
- Confirm or deny anything about a wallet. Attribution of on-chain activity to a person is outside the scope of this desk entirely.
Response expectations
Messages are read by a small team, so a reply is not immediate and not guaranteed. Corrections with a verifiable source get priority because they change a page that other people are reading. General questions may be answered directly, may become an article, or may receive no reply at all if they fall outside scope.
Nothing you send is added to a mailing list, because there is no mailing list. Message contents are used to check and improve pages and for nothing else, as described in the privacy page. If you would like a correction credited, say so; the default is to publish the fix without naming anyone.
Before you write
Two of the questions this desk receives most often already have pages. If your screen disagrees with another one, start with where a live volume number comes from, which covers the six independent choices that make two honest systems report different totals. If your panel is behind rather than wrong, why dashboards lag walks the six stages where the delay is usually hiding.