Transparent · checkable
Corrections
We get things wrong. Tutorial content goes stale especially fast — a platform changes its back end, a library renames a field, a fee gets adjusted. When we're wrong we don't delete the post and pretend it never happened; we log it here in the open: which page, how it originally read, what it changed to, why, and when. You can hold this record against the article and judge for yourself whether we got the fix right.
How we handle a correction
- Factual errors that would mislead your actions (such as a wrong field or a parameter stated backwards): we fix the article as soon as possible and leave a record on this page.
- Out-of-date information (platform UI, API or fees changed): we update the article and note "follow what the OKX site currently shows."
- Pure wording, no effect on understanding (typos, formatting): fixed directly, usually without a separate record.
If you find a piece that's wrong or out of date, write to [email protected], or see the contact page. Corrections we adopt go in the log below.
Log
| Date | Page | Original → fix | Reason |
|---|---|---|---|
| 2026-09-08 | How to use the demo account, OKX API quant from scratch | The text said writing 'options': {'sandboxMode': True} in the config had "the same effect" as set_sandbox_mode(True), and that the live API Key could be reused for the demo → changed to: only set_sandbox_mode(True) gets you onto the demo — the demo header x-simulated-trading: 1 is added by that method itself and writing the value into the constructor's options never calls it; and the demo needs its own Demo Trading API Key, created inside the demo environment. We also added that demo and live share one REST host and are separated only by that header, plus a self-check print line in both code blocks. |
The "clarification" we added on 2026-06-03 was itself wrong, and it is corrected here along with the Key claim. Together the two errors let a reader believe they were on the demo while the request carried no demo flag — and if the Key in hand was a live one with trade permission, the orders going out were real. This time the conclusions were checked against ccxt's own implementation of set_sandbox_mode and the demo-trading section of OKX's API docs. |
| 2026-06-08 | OKX API quant from scratch | The original described the ccxt password field loosely as "enter your password" → changed to spell out "enter the Passphrase you set when creating the API key — it is neither your login password nor the secret." |
The old wording made it easy for readers to enter their login password, leading to a constant auth-failure error. This is the highest-frequency beginner trap and had to be made clear. |
| 2026-06-06 | Setting up an OKX grid bot | The original example described the relationship between grid "count" and "per-grid profit margin" too absolutely (as "more grids means higher profit per grid") → changed to "within a fixed range, more grids means a smaller step per grid, so per-grid profit falls and triggers more often," with a worked set of example parameters added. | The original had the cause and effect backwards and could mislead readers into blindly raising the grid count. The fix matches how the grid actually works. |
| 2026-06-05 | OKX fees + rebate | The original gave specific maker/taker fee figures → changed to only explain that rates are "split by tier and by maker/taker," with a consistent note added: "follow the current figures published on the OKX site." | Exchange fees get adjusted, and hard-coded figures go stale and mislead. Pointing to the official site keeps readers from acting on outdated numbers. |
| 2026-06-03 | Using the demo account | The original only mentioned switching to the demo account via set_sandbox_mode(True) in ccxt → added "some versions also support setting 'options': {'sandboxMode': True} in the config; either one works," with a note that the syntax can differ across ccxt versions. |
A reader reported that the single approach didn't take effect in certain versions. Adding the second approach gives wider coverage and reduces cases of getting stuck on "can't switch to the demo account." |
This log will keep growing. Its point isn't just "owning up" — it's also one basis for you to judge whether this site is worth trusting: a site willing to show in the open where it has changed things is worth more of your time than one that's somehow "never wrong."