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

Colophon

About the Numiscue archive

Colophon plate reading: about this archive
The colophon.

Numiscue answers one question about digital assets — what is this thing, and how does its token actually work — and refuses the adjacent questions about whether to buy it.

What this site is

Fourteen coin records, four guides and five reference tables, first published in August 2026. They were compiled together as a set rather than accumulated over years, which is why every page carries the same publication date. That seemed more honest than staggering them to look organic.

The format came from a straightforward observation. Someone hears a coin's name, wants to understand it before spending money, and finds two kinds of page: promotional material written by whoever benefits from the coin's price, or an empty template with a price chart and no explanation. There was room for a third thing.

Who writes it

The records are compiled and edited by K. A. Vestergaard for the Numiscue archive desk.

That is a pen name. It is used because the work should be judged on whether the sources check out, not on who signs it, and because the alternative — inventing a biography with credentials nobody can verify — is a worse form of dishonesty than a byline that says up front what it is.

So there is no claim here of institutional affiliation, no list of qualifications, and no social media profiles. What there is instead is a source on every factual claim, and a corrections log that stays public. If a record is wrong, the source link is the fastest way to prove it, and the desk wants to hear about it.

How a record gets written

The same procedure every time.

  1. Find the primary source. The project's own documentation, its source code, a governance record, or the chain itself. Secondary coverage is used to find out what to look for, never as the citation.
  2. Write down what it says and when it was read. Every claim on this site has an entry in an internal ledger recording the source and the month it was checked. That is where the “checked August 2026” lines come from.
  3. Leave it out if it cannot be traced. An empty field is better than a plausible number from an unreliable place. There are several such gaps and they are noted where they occur.
  4. Write anything that moves as a range with a date. Circulating supply, staking participation, fee levels: these are given as magnitudes with a pointer to where the live figure is published, never as a precise number that will quietly rot.
  5. Find the one thing that makes this asset different and build the page around it. Fourteen pages of the same table would be worth nothing.

What this site will not publish

  • Price predictions. Not as forecasts, not as ranges, not as scenarios.
  • Investment advice. No page here concludes that anything is worth buying.
  • Scores or rankings. The risk section of each record lists facts. Facts do not come with a number out of ten.
  • Fabricated experience. No claims of having tested something that was not tested, no invented timestamps, no screenshots that do not exist.
  • Live-looking data that is not live. Where a page shows a snapshot, it says so at the top.

Where the money comes from

From one referral link, on the practical buying guide, which pays this site a share of the fees if a reader registers through it. There is no advertising, no sponsored writing and no paid placement. The funding disclosure records the code, the destination, what the arrangement pays and the rules it has to keep to.

The relationship is not used as an editorial credential or as a reason to prefer one venue. The archive still covers BNB — the exchange's own token, and so the clearest conflict on the site — on the same source-led basis as the other thirteen records.

What is coming

More records, added at a pace that keeps the checking honest rather than filling a quota. The existing fourteen get revisited when a source changes — governance votes and documentation updates are the usual reasons — and any change to a factual claim goes in the corrections log with the date.

Suggestions for which asset to add next are welcome at the desk.