VoltArb blog

Editorial principles

How we prepare articles

So you can verify a source, understand an example and assess the limits of a conclusion.

Updated 18 October 2026

Who is responsible for the content

This blog is published by VoltArb, a project focused on arbitrage and market analytics. We explain tool metrics, market mechanics and calculation limits. A VoltArb byline is not an independent review of our product. If an article has an individual author or reviewer, we will describe only their actual contribution.

How we prepare and check articles

AI tools may assist preparation. For new articles and substantive updates, we check important conditions against primary sources, compare interface instructions with working features and verify arithmetic separately. A successful software build does not establish the correctness of a trading conclusion. Unverified conditions remain unknown.

What the numbers represent

An educational example demonstrates a calculation and is labeled accordingly. A historical case uses saved observations with a source and time; raw data and methodology are provided where possible. A screenshot records the interface at capture time. It does not promise the same prices, rates, availability or return today.

What an update date means

The publication date records the article’s first publication. We change the update date for a substantive revision, such as checking a calculation, a source rule or an interface instruction. A change to shared navigation does not mean every older article has been reviewed again. Historical cases retain their original observation window.

Sources and commercial links

Check exchange rules at the official sources provided: availability depends on the market, account and region, and terms can change. Exchange registration links may be affiliate links. Such a link is not a reliability assessment or a trade recommendation. Check the Pro page for current VoltArb features and pricing.

How to report a correction

Open VoltArb on Telegram using the link below and send the article URL, the relevant passage and a primary source or calculation. Do not send access keys, account documents or other private data. A correction should be verifiable; no particular response time is promised here.

We use cookies only for essential UI functionality. No analytics or marketing is enabled. You can accept or decline cookies to continue.