About this desk
Launch Feed is a small editorial desk with one subject: reading a public stream of new token launches from the outside. This page states the scope, the method, the sourcing rules and the things that will not appear here.
What this desk covers
One narrow subject. A public feed of newly created tokens produces rows faster than anybody can read them, and the fields displayed most prominently on those rows are the ones easiest to produce deliberately. This desk writes about how to read such a feed anyway: what a row is made of, what the opening minutes support, and where the reading stops.
The perspective is deliberately external. These pages are about watching other people launches, not about running one and not about managing a position in one. That is a different job with different questions, and mixing the two produces writing that serves neither.
Who writes it
Pages are published by The Launch Feed Desk, which is the editorial name for the people who write and check them. There is no invented author with a fabricated biography attached to any page on this site, no photographs of people who do not exist and no credentials claimed on anybody behalf.
The desk holds no token it writes about, operates no launch, runs no trading and sells nothing. It is independent of Pump.fun and of every other venue named on these pages, and it uses no third-party logo or brand mark anywhere.
How a page gets written
Protocol behaviour is read from published documentation and, where it matters, from the ledger itself. Where a program parameter has changed over time, the page says that it changes and points at the venue rather than printing a number that was accurate on some earlier date. Static figures about moving systems are one of the more common ways an article rots quietly.
Every interpretive claim on this site is written with a refutation attached. If a page says a pattern usually indicates something, it also says what observation would show that the reading was wrong. This is not a stylistic choice; a claim with no falsifying condition cannot be checked, and an unfalsifiable claim about a market is worth nothing to a reader.
What this desk will not publish
- Predictions about any token, and any statement that resembles a signal or a call.
- Commentary on any named real token, positive or negative.
- Statistics we cannot source, including counts of how often anything happens.
- Ratings, review counts, testimonials or aggregate scores of any kind.
- Screenshots of feeds, invented example tokens, or illustrative data presented as if it were recorded.
- Accusations against any named project, operator or individual.
- Legal, tax or financial advice, all three of which are outside what this desk can competently give.
The line on the fifth item deserves a sentence of its own. An article can be made much more persuasive with a plausible-looking capture of a feed and a made-up ticker, and the persuasion comes from the reader assuming the capture is real. That is a small dishonesty with a large effect, so this site uses none.
Numbers on this site
Numbers appear in three forms only. Protocol facts, such as the target interval between Solana slots, which can be checked against documentation. Clearly labelled illustrations, which use round figures, describe no real launch or person, and always carry a sentence saying so. And figures from a named public source, cited where they appear.
No other numbers appear. There are no wallet balances, no profit or loss examples drawn from real accounts, and no measurements of any specific launch anywhere on this site.
Corrections
When something published here is wrong, the page gets a visible correction rather than a silent edit. This matters more than it sounds: a desk that quietly rewrites its own record has no standing to ask a reader to check anything, and the whole method on this site is built around checking.
Protocol details go stale faster than anything else, so a reader who spots a parameter that has changed is doing the single most useful thing that can be done with these pages. The route is on the contact page, and it is read.
Where this desk stops
Three limits are permanent rather than temporary. Addresses cannot be resolved into people, so every count of participants published here is an upper bound. Intent is never written to a chain, so no page can tell you why anything happened. And the coordination that occurs in private channels is invisible from the ledger, so any account built purely from on-chain data has a hole in it of unknown size.
Naming those limits is not a disclaimer at the bottom of the page. It is the shape of what the desk can honestly offer: a bounded, dated, checkable description of participation in a launch, which is smaller than what most launch commentary promises and is the part that survives being looked at again.