Numiscue An independent archive of digital-asset mechanics · fourteen records · checked August 2026

Colophon

Corrections

Colophon plate reading: corrections
Kept in public, including the ones caught before anyone else saw them.

Every change to a factual claim on this site is logged here with its date and what changed, including corrections made to drafts before publication.

Why the pre-publication ones are here too

Most correction pages only list errors that reached readers. This one also lists the ones caught during compilation, for a specific reason: they are the clearest evidence of what the checking process actually does, and each one is a mistake that a page written from secondary sources would have shipped.

They are marked as such so nobody mistakes them for errors that were live.

Log

25 August 2026 · Published change · Funding disclosure

Until this date the site stated that no referral code or commercial registration link was registered, and it published none. The owner has since registered a Binance referral code for this site. The code is now shown on the home page frontispiece, with a copy control and the disclosure beside it; the registration link itself appears once, in the commercial-link block of the buying guide, marked as a referral link. The home page carries no outbound commercial link. The funding disclosure, privacy, disclaimer, about and contact pages, the guides index and the footer line were rewritten in the same change, so that no page is left claiming the old status.

The BNB record is where this creates a conflict of interest, because that token is issued by the same exchange. Its opening note now declares the arrangement instead of denying one. Nothing else in the record moved: the risk list, the enforcement history and the sourcing are as they were before the code existed.

23 August 2026 · Caught before publication · Polkadot record

The draft stated that Polkadot issues a fixed 120 million DOT a year, sourced from the Polkadot wiki's DOT token page, which says exactly that. A check of the Polkadot forum found Referendum 1710 had since cut annual issuance to roughly 55.8 million DOT and introduced a long-term ceiling of 2.1 billion — a change the wiki page had not picked up.

The record was rewritten to describe the sequence of governance decisions instead of quoting a single current figure, and now tells readers to check the live wiki or a block explorer rather than trusting the page. The disagreement between Polkadot's own sources is reported on the record rather than resolved there.

23 August 2026 · Caught before publication · Solana record

The draft treated SIMD-0411, which would double Solana's disinflation rate from −15% to −30% a year, as an adopted change. Reading the proposal's own thread showed it marked as under discussion with the voting timeline still to be determined.

The record now presents the documented −15% schedule as the one in force and shows the proposed faster path as a separate, clearly labelled line on the chart. The status is dated, so a reader in future knows to check whether it has moved.

23 August 2026 · Caught before publication · Dogecoin record

The draft described Dogecoin as having “unlimited supply”. Dogecoin's own documentation argues against that wording, on the grounds that issuance per block, per day and per year is strictly bounded and that the coin is only infinite over infinite time.

The record was changed to say there is no maximum supply constant and no end date to issuance, and then to set out the project's own counter-argument so a reader can weigh it, rather than picking a slogan on their behalf.

23 August 2026 · Caught before publication · Bitcoin record

The draft gave the amount of bitcoin issued so far as an approximate figure carried over from secondary coverage. It was replaced with a value read directly from public block explorers, which also confirmed the chain height and therefore that the current block subsidy is 3.125 BTC.

The figure is now written as a magnitude with the month it was checked, and the record points readers at an explorer for a current number rather than presenting a static one as if it were live.

How to report an error

Email [email protected] with the page, the sentence, and a link to a primary source that says otherwise. Project documentation, source code, governance records and block explorers all count; secondary coverage is a useful pointer but is not what gets cited.

Anything that turns out to be a genuine factual error is fixed and appears here with its date. Nothing is quietly edited, and no correction is removed from this page once it has been made. More on how records are compiled in the first place is on the about page.