Send the Desk a Correction
There is one address and one purpose. The desk reads corrections, questions about mechanisms described on the site, and reports that something has changed on chain since a page was written. It does not answer requests for trading advice.
Write to [email protected]. It is a plain mailbox rather than a ticketing system, there is no form on this site, and nothing you send is added to a mailing list because there is no mailing list.
What makes a correction easy to act on
The desk amends pages on evidence, so a message that supplies evidence moves faster than one that supplies an opinion. Four things make the difference, and none of them takes long to include.
- Name the page. The full address, or the code in the corner of the page such as FLT-02, which identifies it unambiguously.
- Quote the sentence. A direct quotation removes any argument about what was meant, and it is the fastest way to locate the claim in the source.
- Say what is wrong with it. Whether the mechanism is described incorrectly, the arithmetic does not work, or the behaviour has changed since the page was written.
- Point at something checkable. Protocol documentation, a program repository, or an address and signature the desk can read for itself. A claim the desk can verify becomes an amendment; one it cannot verify stays an open question.
What happens next
Accepted corrections change the page, and a correction that changes the substance of a claim is noted on the page rather than applied silently. The modification date on a page reflects the real edit, and no page is ever backdated to make a change look older than it is.
Where a report is credible but the desk cannot establish the answer either way, the page says so. That outcome is uncomfortable and it is better than the alternative, which is publishing a confident sentence to fill a gap.
What the desk will not answer
- Whether to enter a specific token. That is a market view, and this desk does not hold one publicly or privately on any individual launch.
- Configuration requests. No liquidity floor, concentration limit or delay value will be recommended, because the correct value depends on a position size only you know. The reasoning behind every threshold is on the relevant page instead.
- Tool endorsements. The desk does not rank providers, benchmark endpoints or comment on which product performs best. Those are commercial claims that cannot be verified from outside.
- Requests for code. Rules are published as rules and thresholds in prose. The desk does not send working entry automation, and it does not help with anything designed to make a launch pass somebody else's screening.
- Recovery of lost funds. Nobody at this desk can reverse a transaction, recover a key or intervene in anything on chain. Messages of this kind get a short reply pointing that out.
Anything else worth sending
Mechanisms the site has not covered are welcome, particularly ones with an on-chain signature that a rule could be written against. So are descriptions of failure modes encountered in a real screening pipeline, which are the hardest thing to obtain and the most useful thing to write about.
If you would rather not be quoted, say so and nothing you send will appear on the site. The desk does not publish correspondence, names or addresses in any case, and the only outcome of a message is a change to a page or a reply.