Corrections
Vultax publishes figures about market integrity, so our own record needs to be inspectable. This page lists every material correction we have made to a published claim, with the date and what changed.
How corrections work
A published claim that turns out to be wrong gets changed and recorded here. The log is public because a corrections policy nobody can inspect is not a policy.
- Material errors — a wrong figure, an unsupportable claim, a contradiction between two pages — are corrected and logged with the date.
- Figures are corrected at the source, so every surface that renders the figure changes at the same time.
- Typographical and layout fixes are not logged. Changes to what the site claims are.
- Entries are appended. We do not remove corrections once recorded.
Report an error
If something here is wrong, we would rather hear it from you than leave it standing.
- Email [email protected] with the page and the specific claim.
- For exchange operators: if you believe a venue-quality figure misrepresents your market, include the venue and pair and we will review the observation window behind it.
- See the editorial policy for how claims are sourced and reviewed before publication.
Log
Most recent first. Dates are the date the correction shipped.
2026-08-31
The arbitrage scanner comparison stated that Vultax plans start at $29.98/mo “with API access included.” REST and WebSocket API access is available on the Pro plan at $99.98/mo; the Essential and Premium plans do not include API access. Corrected, and both the pricing page and editorial copy now derive from one entitlement table.
2026-08-31
The arbitrage scanner comparison described Vultax as “the only retail-accessible scanner” detecting 2-leg, triangular single-venue and triangular multi-venue routes. We had not tested every competing product and could not support “only.” The claim was removed.
2026-08-31
The homepage hero reported 14.0M whale transactions tracked while other surfaces reported 14.2M. 14.2M is correct. All surfaces now render the figure from a single source.
2026-08-31
Sub-100ms latency was presented as an achieved characteristic in some copy while the Terms describe it as a best-effort target. It is a target, and is now described that way everywhere.
2026-08-31
A wash-trading feature panel displayed “Venue score 98 / 22,” which read as a single malformed score. It is a range across observed venues and is now labelled as one.
2026-08-29
The homepage FAQ described Vi IQ as combining “seven real-time factors” and listed a taxonomy that did not match the score the product computes. Vi IQ compresses six signal domains: market quality, liquidity health, arbitrage potential, order flow, volatility, and news sentiment. Corrected, and the methodology page now documents the composition.
2026-08-29
Homepage statistics rendered as “0+” to clients that do not run the count-up animation, including search crawlers. The real figures are now present in the served HTML and the animation is a progressive enhancement.