Contact the desk
One address reaches the workshop. A specific correction, with the page and the sentence named, will always get a better answer than a general complaint, because a specific correction can be checked and acted on the same day.
Write to [email protected]. There is no form on this page, no newsletter and no sign-up, so an email is the whole mechanism. Include the page address and, where it is relevant, the mint address you are asking about, since most disagreements about a token turn out to be disagreements about which mint is under discussion.
What is most useful to send
A correction
An error of fact, a field name that has changed, an account size that is wrong, or an inference that does not follow from the fields it cites. Name the page and the sentence. If it is checkable, it gets checked.
A mechanism question
Anything about how an instruction behaves, which account a value lives in, or why a step is described as irreversible. Questions of this kind frequently turn into edits, because they usually expose a sentence that assumed too much.
A gap
A field, extension or standard that the workshop uses without explaining, or explains in two places in two different ways. Consistency across pages is a requirement here, so an inconsistency is a defect rather than a matter of style.
A topic request
A construction decision you keep meeting and cannot resolve from the documentation. Requests shape what gets written next. Nothing is promised and no schedule is published.
What the desk cannot do
It cannot look at a named token and tell you whether it is safe or worth holding. That is the request that arrives most often and it is the one thing this site is built not to do. Account fields record state, never intent, and a verdict about people assembled from fields would be an opinion dressed as a finding.
- No verdicts on named tokens, wallets, teams or launchpads, in public or in private.
- No audits, paid reports, retainers or bespoke analysis, and no referrals to anyone offering them.
- No guidance on making any check on this site return a misleading answer, in any framing.
- No price opinions, targets, entries, exits or portfolio comments.
- No help recovering a key, reversing a revocation or undoing anything the site describes as permanent, because none of those is possible.
What the desk can do is explain how a field works, so you can read it yourself against whatever you are looking at and reach your own conclusion. The procedure for doing that without any help is set out in full in the field guide.
Quoting and reuse
Quoting a paragraph with a link back is fine and needs no permission. Republishing a whole note is not, because these pages are edited when the underlying programs change and a frozen copy keeps the errors. If you cite the workshop in your own work, cite the specific page and the date you read it: the modified date on each note is real and moves.
Response expectations
Mail is read in batches rather than continuously, and corrections are prioritised over everything else. A message asking for a verdict on a named token will usually receive a short note pointing at this page rather than an analysis, which is policy rather than rudeness, and the reasoning behind it is on the workshop page.