Corrections log
Things this site got wrong, and things that changed underneath it. Dated, described, and left in place rather than edited away.
Why keep this page?
Because a page that has been silently corrected is indistinguishable from a page that was right all along, and that difference matters to a reader deciding how much to trust the rest of the site.
Almost every figure here about an exchange — a fee, a tier, a limit, a confirmation count — is a snapshot of something the exchange controls and changes at will. Some of what is published today will be wrong within months. The useful question is not whether a site avoids that, because none do, but whether it tells you when it happens.
Entries below cover the site’s own errors, material changes to figures, and changes to how the site itself works. Typo fixes and wording tidies are not logged. Each row carries a label: Error means something published here was wrong and you may have read it before it was put right; Change means the site itself changed and nothing published had been incorrect.
The log
Nineteen entries so far. The fifteen dated August are from the build period, before the site went live; the four dated September are not.
| Date | Page | What changed |
|---|---|---|
| 2026-09-12 | Error Clarifying the editorial process | The editorial policy overstated manual source checking and how comprehensively old figures and external links were rechecked. It now describes AI-assisted drafting, source review and language adaptation, distinguishes historical snapshots from newly verified figures, and states the limits of automated and language checks. The three editions have been aligned. This correction changes the description of the process; it does not certify a fresh check of every figure on the site. |
| 2026-09-12 | Error Tool validation and calculation assumptions |
Bitcoin address checks now reject invalid witness versions, lengths, padding and checksum encodings as well as bad checksums. A selected transfer network with an invalid fee now stops the comparison; a failed clipboard fallback no longer reports success. Fee break-even and funding-settlement labels state their estimation limits. P2P tables distinguish a gap measured against the mid-price from loss on cash spent, and liquidation derivations state their simplified assumptions. The security-hold guidance now uses task-specific Binance instructions: 24 hours after a password change, up to 48 hours after changing Authenticator, subject to the account notice. This refines the broader wording in the earlier entry. Fee and USDT guides also explain how to reconcile charges and verify a test transfer. |
| 2026-09-12 | Error Language alignment and tool result labels |
The Swahili network picker incorrectly said a transfer on an unsupported network returns; it now says it does not return automatically. The Swahili liquidation calculator also used opening where it meant closing a position. In all three address checkers, a failed checksum still displayed a verified-checksum label; that label now follows the actual result. French and Swahili fee tables and the Swahili funding example have been brought into line with the dated English figures and scenarios. The withdrawal security-hold section and FAQ now use Binance’s stated typical 24- or 48-hour password-change hold, with the account notice taking precedence. Missing or misplaced details in the translated corrections logs have been restored to their corresponding entries. |
| 2026-09-03 | Error French edition, and the disclosure wording (all three editions) |
The French edition was published on this date: 28 pages written for readers in West and Central Africa rather than translated for France, with costs in CFA francs and the deposit routes that actually apply there. It carries a third referral link, equivalent to the English and Kiswahili ones, on its own copy of the account setup guide. Two things were wrong until this entry. The disclosure page and the disclosure sitting beside the link itself both said the link appeared on one page and nowhere else on either edition — wording written when there were two editions and left standing when there were three, which understated the number of referral links on the site at the exact place a reader is deciding whether to use one. Both have been corrected. No native French editor has read the edition, which the editorial policy now states in the same terms it already used for Kiswahili. |
| 2026-08-31 | Change Contact, privacy, footer and security.txt (English and Kiswahili editions) |
The site went live without a published contact address, and said so — on the contact page, in the privacy policy and in the known gaps below. There is now an address: goxeva@goxeva.com. It appears on the contact page, in the footer of every page and in /.well-known/security.txt, which previously pointed a security report at a page that admitted it had nowhere to send one. The passages describing the gap were rewritten rather than quietly deleted, and the known-gap entry about there being no contact channel is retired with this entry. |
| 2026-08-31 | Change Funding, slippage and withdrawal limits (English and Kiswahili editions) |
These three ran on programmatic cover art alone, so each gained a dated screenshot of the public page it depends on: the real-time funding rate table, which shows the settlement interval as a per-contract column and several contracts paying negative funding at the moment of capture; a logged-out spot order book, which shows the finite quantity resting at each price level that the slippage arithmetic is about; and a published withdrawal-hold notice stating in the platform's own words that the restriction cannot be lifted early. The generic BNB Chain homepage link added earlier the same day was removed as redundant next to the two specific Fusion sources. |
| 2026-08-31 | Error P2P prices (English and Kiswahili editions) |
The page described the P2P fee line as reading zero without noting that the platform publishes a P2P fee schedule at all. It does, it varies by fiat market and trade zone, and the maker/taker split applies there too. A dated screenshot of that schedule was added beside the benchmarking section, with a caption saying that zero is common for the taking side but is a schedule rather than a law. The premium is still the dominant cost; it is no longer presented as the only one. |
| 2026-08-31 | Error Liquidation price calculator (English and Kiswahili editions) |
The tool computed entry × (1 − 1/L + MMR) and then called it “the whole formula”. That expression is a shortcut, not the solved result: maintenance margin is charged on the position value at the liquidation price, which puts the rate in the denominator. At an entry of 60,000, 20× and 0.4% the shortcut returned 57,240 where the solved figure is 57,228.92. The tool now solves entry × (1 − 1/L) ÷ (1 − MMR) for longs and the matching expression for shorts, the “whole formula” claim is gone, and the derivation on the liquidation math page now says explicitly which of the two the calculator runs. This site’s own long-form page had the correct derivation all along, so the tool and the article were contradicting each other. The same pass also revised the warning added on 2026-08-30, which said flatly that liquidation costs the whole of the margin: some venues reduce a large position in stages first, so the pages now say most or all of it and name the full wipe as the case to plan for rather than a certainty. |
| 2026-08-31 | Error Transfer networks (English and Kiswahili editions) |
The BEP2 paragraph read as though an interface might still offer BEP2 and BEP20 side by side, leaving BEP20 as the better of two live options. BNB Beacon Chain was retired through BNB Chain Fusion, with validators stopping at the end of 2024, and the official recovery path has since been wound down in turn. BEP2 is now presented as a retired standard and a recovery problem, with a warning that a bnb1 address turning up in 2026 means a stale interface, an unmigrated legacy balance or a scam. A dated screenshot of BNB Chain’s own Fusion page was added beside it. |
| 2026-08-31 | Error Address checker (English and Kiswahili editions) |
The title, H1 and structured-data description asked and answered “which network is this address on?”, which the code cannot do: an 0x string is valid on Ethereum, BNB Smart Chain, Polygon and every other EVM chain, and the address carries no information about which one was intended. The page body had always said so; the high-visibility parts had not. All three now describe it as a format and network-family checker, and the readout carries the same qualification. |
| 2026-08-31 | Error Kiswahili write-up index |
The word counts shown against each Kiswahili article were carried over from the English versions, overstating several of them by more than double. Every figure on both indexes is now measured from the page it labels and rounded down. Three Kiswahili pages that had genuinely been cut short — missing deposits, pending withdrawals and liquidation math — were rewritten to carry the decision branches their English counterparts have, rather than having the numbers quietly corrected downwards. |
| 2026-08-31 | Error Verification, account setup, withdrawals, P2P |
A number of claims about how platforms behave internally were written as settled fact: that an expired document is the single most common rejection, that a second account is usually met with both being frozen, that no priority queue exists, that a broadcast transaction cannot be replaced by anyone. Each of these is either an inference or a platform policy that varies, so each is now stated as such, with the platform’s own terms named as the binding text. The unconfirmed-transaction case now mentions replacement (RBF, same-nonce) accurately rather than ruling it out. |
| 2026-08-30 | Error Binance fees, line by line |
A draft of the tier table was built from third-party summaries, which gave VIP 1 as requiring 25 BNB and VIP 3 as 0.070% maker. Checking Binance’s own public fee schedule on this date showed 5 BNB for VIP 1 and 0.040% / 0.060% at VIP 3. The table was rebuilt from the source page and a dated screenshot of it was added. Caught before publication. |
| 2026-08-30 | Error Break-even price calculator (retired) |
The tool described adding the entry and exit fee percentages together as if it were exact. It is an approximation, because the exit fee is charged on the exit value rather than the entry value. The difference is far below the tick size of anything it was used on, but implying precision it did not have was wrong. The page has since been retired — see the entry below — and the same figure now appears in the trading fee calculator as the move needed to cover a round trip. |
| 2026-08-30 | Error Site-wide |
Early copy described the referral benefit as “20% off trading fees”. That is a rate set by the exchange, varies with their promotions and is shown at sign-up, so every instance was changed to “up to 20%” with a footnote. Stating it as a fixed entitlement would have been a promise this site is in no position to make. |
| 2026-08-30 | Change Footer, and the homepage |
The footer on every page, and a paragraph on the homepage, spelled out the commercial side of the referral arrangement in detail. Accurate, but the wrong place for it: on a page whose job is not to sell you anything, the disclosure only needs to say that a referral link exists. Both now state that and leave the detail to the disclosure page, where it belongs and is set out at length. The footer also gained an explicit statement that this is not an exchange and holds nobody’s funds. |
| 2026-08-30 | Error Liquidation math and the futures tools |
These pages explained the mechanism of a liquidation carefully and never said plainly what it costs. Avoiding overclaiming is not the same as warning someone. All three now state before the arithmetic that being liquidated means losing the whole of the margin behind the position, and that most retail accounts trading leveraged crypto lose money over time. |
| 2026-08-30 | Change Tools |
The site launched with five calculators, which made it worse at the thing it claims to be about: the two questions that lose people the most money are “which network” and “is this address right”, and neither is arithmetic. The withdrawal fee impact calculator and the break-even price calculator were retired — their arithmetic survives inside the network picker and the fee calculator respectively — and replaced with the network picker and an address checker. Their old URLs now return a 404 rather than redirecting, which is the honest signal for a page that is gone. |
| 2026-08-30 | Change Kiswahili edition |
The Kiswahili edition of this site was published on this date. It was written from the English edition by an editor working in Kiswahili — not a word-for-word translation, but new prose carrying the same figures, formulas and dates. No native Kiswahili speaker has read it. Language errors, badly chosen technical terms and sentences that do not sit right to a native ear are therefore expected, and corrections to the Kiswahili itself are as welcome as corrections to a figure. When they arrive they will be logged here. |
Known gaps
Stated here rather than left to be discovered.
- Screenshots age. The thirteen dated screenshots on this site show interfaces that the exchange and BNB Chain redesign regularly. They are labelled with the month they were captured and will be reviewed rather than left to drift.
- Two dead URLs. The retired calculators leave
/tools/withdrawal-fee-impact/and/tools/breakeven-price-calculator/returning 404. Nothing on this site links to them any more, but an external link or a bookmark would land on the not-found page. Redirecting instead would be tidier and would also pretend the pages still exist somewhere; they do not.
What counts as a correction here?
Any change to a fact, figure, formula or instruction, whether the error originated here or the underlying thing changed.
Both get logged, and the entry says which it was. “We were wrong” and “the exchange changed this” are different admissions and collapsing them into one would be a way of never quite owning the first.
Not logged: spelling, punctuation, phrasing that has been tightened without changing meaning, and layout work. Those happen continuously and logging them would bury the entries that matter.