Ponsflow

Editorial standards and corrections

Everything on this site is published by Ponsflow, operated by Hexbridge Systems, as an organisation rather than 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 Ponsflow, operated by Hexbridge Systems. 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 page 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. Engine behaviour is written from the system as it actually runs. A capability 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 1% fee, the volume range, the maker wallet range and the run window all 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 run limits 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, and the engine pages are built so you can check the first kind yourself.

  • On-chain fact. Read from Robinhood Chain block by block. Token names, tickers and logos come from the token contract itself, not from a launchpad feed or a third-party index. Anyone can reproduce them from Robinscan or a public RPC node.
  • Product fact. The running configuration of this service, readable live from the free JSON API and from the MCP server at /mcp.
  • Third-party fact. Linked to the primary document, not to a summary of it. Where a claim exists only as somebody else’s 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 price outcome, a ranking or a profit. A run changes on-chain trading activity; it does not create 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% fee on the volume ordered. That is a conflict of interest and we would rather state it than have you find it. In practice it means no paid placement, no affiliate links, and comparison pages that name what the alternative does better.

Ponsflow is independent of Pons and of the venues orders are routed through. We are not affiliated with them and do not speak for them.

Corrections

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

  1. Report it to desk@ponsvolumebot.net with the page URL and what is wrong. A transaction hash or a block number 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

  • The Organization entity names this page as its publishingPrinciples, ethicsPolicy and correctionsPolicy.
  • Every published page is available as clean Markdown by requesting it with Accept: text/markdown.
  • Product facts, run limits and live chain telemetry are readable from the MCP server at /mcp, which reads the same configuration and the same node the site renders from.
  • 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.