Contact the Migration Desk
One address, read by the people who write the pages. Corrections are the most welcome message the desk receives, because a mechanism that changed is a page that is now wrong and the desk would rather hear it from you than not at all.
Where to write
Email the desk at [email protected]. There is no form on this page, no newsletter capture and no tracking pixel, because none of those would make a correction arrive faster.
What the desk wants to hear
- Corrections. A claim on a page that is wrong, or was right and has since stopped being right. A link to the primary source settles it fastest.
- Parameter changes. If a launchpad has changed a threshold, a retained share or a graduation destination, the desk wants to know so pages describing the old behaviour can be updated.
- Mechanism questions. Something about the handover that the site does not explain, or explains badly. Questions frequently become pages.
- Broken things. A dead internal link, a page that renders badly, an address in an example that resolves to something unexpected.
- Disagreements. Particularly with anything labelled as inference, which is labelled precisely so it can be argued with.
What the desk does not do
The desk does not accept payment for coverage in any form, including sponsored articles, paid placements, affiliate arrangements presented as editorial, or a link inserted into an existing page for a fee. There is no rate card because there is nothing to buy.
It does not publish submitted articles or guest posts. Everything here is written by the desk, which is the only way the byline means anything.
It does not write about a specific token because somebody asked. Tokens appear on this site only as illustrations of a mechanism, and no page here assesses whether any particular token is worth holding.
It does not give trading advice, answer questions about whether to buy something, or comment on price. Those are outside what a desk describing a mechanism can honestly do.
And it does not provide technical support for third-party products. If a wallet, an aggregator or a launchpad is not behaving, the operator of that product is the correct place to take it.
What helps a correction land
Say which page, quote the sentence, and say what is wrong with it. If a protocol parameter changed, a link to the source is worth more than any amount of explanation. If a behaviour was observed on chain, a transaction signature is the strongest possible evidence and takes seconds to include.
The desk does not need to be persuaded that being wrong is bad. It needs to be shown the specific thing, because the pages are long and a general note that something seems off is difficult to act on.
Response
Messages are read by the people who write the pages. Corrections are prioritised over everything else. A correction that changes the meaning of a claim is described on the page rather than applied silently, so readers who saw the earlier version can see what changed.
Not every message receives a reply, and the desk would rather say that plainly than imply a service level it does not maintain. A correction that arrives and is acted on has done its work whether or not it gets an answer.
Independence, restated
This publication is not affiliated with any launchpad, exchange or protocol it writes about. If you are contacting the desk believing it can act on behalf of one of them, it cannot, and the operator of that product is the only place that request can go. The full statement of what this desk is and is not sits on the about page.