How this desk explains things
A short statement of scope and method. What this site is for, how a page gets written, what counts as a source, and the things this desk refuses to publish even when they would make the pages more persuasive.
What this site is for
Plain Solana exists because the vocabulary of Solana trading automation is taught almost entirely by people selling something. If you arrive without background, the first ten pages you read will use bonding curve, slippage, RPC and volume bot as though you already know them, and the eleventh will offer to sell you one. This desk writes the sentence that would have helped on the first page.
The audience is a newcomer who is not stupid and is not in a hurry to buy anything. That assumption shapes everything: definitions come before opinions, one idea gets one section, and no page assumes you have read another one first, though reading them in order is easier.
Who writes it
Pages are written and maintained by the Plain Solana Desk, which is the editorial name for the people who produce this site. There is no invented expert with a photograph and a list of credentials, because that would be a fabrication and this site would then be one more thing you have to check.
What that means in practice is that no page here asks you to trust a person. It asks you to check a claim. Protocol behaviour is stated in a way you can verify from public documentation, arithmetic is shown in full so you can redo it, and anything on chain can be looked up on an explorer with the same access everybody has.
The rules every page follows
Definitions before judgement
Each explainer opens with the plainest true sentence the desk can write about its subject, and every page carries that sentence in a box at the top. Judgement appears later and is labelled as judgement. If a page cannot state its subject in one sentence, the page is not finished.
One idea per section
A section introduces a single concept and completes it. Where a second concept is needed, it gets its own heading rather than a parenthesis you are expected to hold in your head. This makes pages slightly longer and considerably easier to read once rather than three times.
Numbers only when they can be checked
Figures on this site are one of three things: a protocol constant such as the lamport denomination or the base fee per signature, arithmetic worked in full and labelled as illustrative, or a figure from a named public source. The desk publishes no statistics of its own, no success rates, no benchmarks and no ratings, because it has no way to verify them and neither would you.
Limits stated in the paragraph
Where something cannot do what people assume it does, the page says so where the assumption occurs, not in small print at the bottom. The sixth explainer exists largely to say what this category of software cannot achieve, and it is deliberately the least flattering page here.
Nothing that endangers your keys
No page describes a procedure requiring a seed phrase, a private key export or a wallet handover. Where a real workflow involves key material, the page describes the risk rather than walking you into it, and the safety explainer lists the requests that are theft every time.
What this desk does not publish
- Earnings claims. Nothing here tells you what a token will do, what a campaign will return, or what anybody made. The mechanisms described on this site have no way of producing those outcomes, so writing about them would be fiction.
- Invented evidence. No fabricated statistics, no review counts, no star ratings, no testimonials, no case studies with numbers nobody can check, and no backdated publication dates.
- Verdicts on named products. This is an explainer desk, not a review site. Pages describe how a class of tool works and what questions to ask of any of them; they do not rank vendors or accuse them.
- Advice. Nothing here is financial, legal or tax advice. The page on legality says explicitly that the question belongs to a qualified lawyer in your jurisdiction, and that remains true however carefully we describe the concepts.
How a page gets written
A page starts as a question somebody actually asked, usually one that other guides answer with a term the asker did not know either. The desk writes the one-sentence answer first. If that sentence cannot be written without three other undefined words, those words get glossary entries and the page gets restructured until it can.
Claims about protocol behaviour are checked against public documentation. Arithmetic is worked out and written into the page so a reader can follow it and disagree. Where a figure changes over time, such as a venue fee rate, the page says the figure is an assumption and tells you where to read the current one, rather than freezing a number that will quietly go stale.
Corrections
This subject changes, and a reference site that never corrects itself is simply an old site. If a definition here is wrong, out of date, or written in a way that misleads, the desk would rather hear about it. Corrections that identify the page and the specific sentence are acted on fastest, and the contact page explains what makes a report easy to use.
Where a correction changes the substance of a page rather than a typo, the change is made in the text itself rather than appended as a note, because a reader arriving next month should read the correct version and not an archaeology of the wrong one.
Commercial disclosure
This site links to a hosted volume automation console in a small number of places, including a button in the header. Those links are commercial. They are the reason the site can be maintained, and they are marked by being buttons and by naming what is on the other side.
What that arrangement does not do is change what the explainers say. The sixth explainer argues at length that this category of tool is a promotion mechanism rather than a profit machine, lists six things it cannot do, and tells you that not spending is a real option. That page would be shorter and friendlier if the commercial relationship were steering it.