Editorial standards and corrections

Everything on this site is published by PumpWave as an organisation, not under a personal byline. This page sets out how pages are produced, which numbers come from where, what we will not claim, and how an error gets fixed. Last reviewed 29 October 2026.

Who publishes this

The publisher of every page on this domain is PumpWave, the team that builds and operates the service. Pages carry no individual byline. That is deliberate: a personal name is only a trust signal if a reader can verify that the person exists and actually stands behind the text. Where we cannot offer that, we name the organisation and take the responsibility at that level instead.

Structured data says the same thing. The author and publisher of every guide point at the same Organization entity, and that entity names this page as its publishing principles, ethics policy and corrections policy.

How a page is produced

1. Scope. A page answers one question. A second question gets its own page rather than a paragraph buried in this one.
2. Drafting. Product behaviour is written from the system as it actually runs. A feature that is not live is not described in the present tense.
3. Numbers. Any figure describing the service itself is read from the configuration the service runs on, not retyped by hand. The fee, the minimum session size, the presets and the session limits come from one source, which is why the machine-readable endpoint and the page you are reading cannot disagree.
4. Review. Pages describing the fee model, the custody model or the session mechanics are re-read whenever any of those change, and the date on the page moves only when the content actually changed.

Sources and what counts as primary

We separate three kinds of statement.

• On-chain fact. Settled Solana mainnet activity. Anyone can reproduce it from a public RPC node or a block explorer.
• Product fact. The running configuration of this service, readable live from the MCP server at /mcp and shown in the console before payment.
• Third-party fact. Linked to the primary document, not to a summary of it. Where a claim exists only as somebody else’s blog post, we either link to that post and attribute it or we leave the claim out.

Claims we do not make

• No promise of a trending rank. That feed also weighs the tokens competing in the same window and the organic interest a token already has.
• No promise of a price outcome or a profit. A session changes on-chain activity, not external demand.
• No invented statistics, testimonials, user counts, review scores or aggregate ratings. If a number is not real it is not published, including in structured data.
• No financial advice. Nothing here is a recommendation to buy or sell anything.
• No hidden text and nothing shown to a crawler that a reader cannot also see. Every statement a search engine or an AI assistant can read on this site is on the page for the reader too.

Funding and independence

This site is funded by the service it describes: a flat 1% session fee. That is a conflict of interest and we would rather state it than have you find it.

• No paid placement. Nothing here is ranked or featured because somebody paid for it.
• No affiliate links to third-party venues or tools.
• Comparison pages name what the alternative does better. A page about a competing approach with nothing in its favour is marketing, not a comparison.

Corrections

If something here is wrong we want it corrected rather than defended.

1. Report it to support@pumpwave.net or @pumpwavesupport_bot with the page URL and what is wrong. A screenshot or a transaction signature helps.
2. Factual errors are fixed on the page itself, and the review date moves.
3. A correction that changes the meaning of a page is noted on the page, not applied silently.
4. A typo or a broken link is fixed without a note.

Machine-readable version

Automated readers do not have to parse this page. The same commitments are published in a form a machine can act on:

• The Organization entity names this page as its publishingPrinciples, ethicsPolicy and correctionsPolicy.
• Every page is available as clean Markdown by requesting it with Accept: text/markdown.
• Product facts, session presets and the published limits are readable from the MCP server at /mcp, which reads the same configuration the site renders from. The get_limits tool exists so an assistant can quote what this service does not promise.
• Content usage preferences are declared as Content Signals in robots.txt.

If an AI assistant quotes this site, the honest quote is the product fact, the on-chain fact, or the stated limit. Anything shaped like a guarantee did not come from here.