About the index

What this desk covers

Three subjects, deliberately narrow. The taxonomy of automation: which classes exist, what each optimises for, and how they differ in capital shape and failure mode. The execution layer: how transactions reach a block on Solana, what fees and bundles actually buy, and what the whole stack costs. And risk: token screening, key custody, permission scope, and the operational failures that repeat across every implementation.

The intended reader is someone deciding whether to automate, someone who has already bought a tool and does not understand its behaviour, or someone building and comparing execution approaches. Every page is written to be useful to all three, which means mechanism first and marketing vocabulary translated back into specification.

Who writes it

Pages are published under the byline The Sniper Bot Index Desk. That is the honest description: an editorial desk rather than a named individual. We do not invent author personas, credentials, photographs or biographies, and we would rather carry the weaker authority signal of an unnamed desk than the false one of a fabricated expert.

What the byline commits us to is method rather than reputation. Every claim on this site should trace to a documented protocol behaviour, a public program interface, or an observation any reader can reproduce with an RPC endpoint and a block explorer. Where a claim cannot meet that bar, it is either labelled as an assumption or it is not published.

How pages are researched and maintained

Technical claims are checked against protocol and program documentation rather than against other articles in this niche, which recycle each other's errors with remarkable persistence. Where a behaviour is observable, we prefer describing how a reader can observe it themselves over asserting a number they would have to trust.

Pages are revised when the underlying behaviour changes. Solana ships changes to fee mechanics, client behaviour and program interfaces regularly, and any page here can go stale. When that happens we amend the page and say what changed, rather than quietly rewriting it. Publication dates are the real build dates and are never backdated to look established.

What is deliberately excluded

• Vendor rankings and scores. A private execution engine cannot be audited from outside. Any score we published would carry more authority than the evidence behind it.
• Performance claims and returns. We do not publish profit figures, win rates or backtests, our own or anyone else's.
• Fabricated trust signals. No review counts, no star ratings, no testimonials, no invented case studies. This niche is saturated with them, which is precisely why we do not add more.
• Signals, calls and strategy. We describe how tools work, not what to buy. There is no signal channel and there never will be.
• Paid placement. Nobody can buy a mention, a position or a favourable description on this site.

How the site is funded

A small number of links on this site point to a commercial automation platform, and those links may be commercially beneficial to us. There are six of them across the entire site and they are placed where a reader asking that specific question would reasonably want a concrete example: the home page hero and console section, the footer, and three articles where a named implementation makes an abstract class tangible.

Two commitments follow from that. First, no page's conclusions are shaped by the arrangement: the evaluation framework applies to the platforms we link as strictly as to any other, and we publish no score for any vendor including them. Second, we do not add more. The ceiling is fixed and stated here so that readers can count them.

Numbers policy

Figures on this site fall into exactly three categories. Protocol constants, such as the slot target or the blockhash validity window, are stated as constants. Illustrative arithmetic is labelled illustrative, shows its inputs, and exists so that readers can substitute their own figures. Anything else is attributed to a named public source. There is no fourth category, and in particular there are no unsourced statistics presented as industry facts.

Corrections

If something here is wrong, we want to know, and specific corrections with a reference are far more useful than general disagreement. The editorial policy sets out how corrections are handled and what we will and will not change. Contact details are on the contact page.