<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Numiscue</title>
    <link>https://numiscue.com/</link>
    <description>An independent archive of digital-asset mechanics. Fourteen coin records, four guides and five reference tables.</description>
    <language>en</language>
    <lastBuildDate>Sun, 23 Aug 2026 00:00:00 +0000</lastBuildDate>
    <ttl>1440</ttl>
    <item>
      <title>How to read a token&#x27;s supply and emission schedule</title>
      <link>https://numiscue.com/guides/token-supply-and-emission-schedule/</link>
      <guid isPermaLink="true">https://numiscue.com/guides/token-supply-and-emission-schedule/</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>Total supply, maximum supply and circulating supply are three different numbers, and market capitalisation and fully diluted valuation are two more built on top of them. Confusing any pair of those is the most common way to misread a project entirely. This guide works through what each one measures, the five shapes an emission schedule can take and how each behaves over time, the difference between a cliff and linear vesting, how burns fit against issuance, and the question nobody asks about who actually receives newly created tokens. It closes with an ordered list of where to check, from source code down to data aggregators, and one habit worth keeping: write down the date you looked.</description>
    </item>
    <item>
      <title>Layer 1 vs layer 2: what the difference costs you</title>
      <link>https://numiscue.com/guides/layer-1-vs-layer-2/</link>
      <guid isPermaLink="true">https://numiscue.com/guides/layer-1-vs-layer-2/</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>Almost every explanation of layer 2 networks opens with an architecture diagram, which is the wrong end of the problem. This one starts from the fee you pay, the waiting you do, and the question of which network your balance is actually sitting on. It covers where the cost saving comes from, why a withdrawal back to the base chain can take days on some designs, why the same address string is valid on twenty different networks, and why bridges have been among the most attacked pieces of infrastructure in the industry. The architecture arrives last, once the practical consequences make it worth having.</description>
    </item>
    <item>
      <title>Stablecoins: what actually backs the big ones</title>
      <link>https://numiscue.com/guides/what-backs-stablecoins/</link>
      <guid isPermaLink="true">https://numiscue.com/guides/what-backs-stablecoins/</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>Fiat-reserved, overcollateralised and algorithmic stablecoins all describe themselves as backed one to one, and they mean three different things by it. This guide sets out what the backing asset is in each case, who holds it, what the reporting actually covers, and how each design fails when it fails. It also spends time on the question most explainers skip: whether you personally can redeem the token for what backs it. For most holders the answer is no, and understanding why that matters even to people who never redeem is the point of the piece.</description>
    </item>
    <item>
      <title>Bitcoin: the 21 million cap and how issuance ends</title>
      <link>https://numiscue.com/coins/bitcoin/</link>
      <guid isPermaLink="true">https://numiscue.com/coins/bitcoin/</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>Bitcoin&#x27;s supply cap is a rule enforced by every node rather than a promise made by anyone, and the difference between those two things is what this record is about. It covers the halving schedule as a constant in the source code, where issuance actually stands as of August 2026, and the property most summaries miss: because each step is half the last, the great majority of the supply arrived years ago. The genuinely open question, stated as open, is whether transaction fees will fund enough security once the subsidy is negligible. Bitcoin&#x27;s own documentation says probably, and that word is carrying real weight.</description>
    </item>
    <item>
      <title>Ethereum: how ETH is issued and burned at once</title>
      <link>https://numiscue.com/coins/ethereum/</link>
      <guid isPermaLink="true">https://numiscue.com/coins/ethereum/</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>After the Merge, Ethereum runs two supply flows at once: new ether issued to validators, and ether destroyed by the base fee on every transaction. Issuance is fairly steady, the burn follows demand for block space, and the net can be positive or negative. That is not what deflationary means, and this record explains why the distinction matters when you are trying to reason about supply. Includes the reference point from Ethereum&#x27;s own documentation about the gas price at which the burn clears issuance, the size of the drop at the Merge, and where staking concentration sits as a risk.</description>
    </item>
    <item>
      <title>BNB: how the burn works and what it is tied to</title>
      <link>https://numiscue.com/coins/bnb/</link>
      <guid isPermaLink="true">https://numiscue.com/coins/bnb/</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>BNB launched with two hundred million tokens and is being reduced toward a stated floor of one hundred million by two separate mechanisms: a quarterly burn calculated from a published formula, and a continuous burn of part of every block&#x27;s gas fees. This record sets out both, and draws a distinction that usually gets lost — the floor is a programme target maintained by an entity, not a consensus rule enforced by nodes. It also declares the conflict of interest at the top rather than in a footer: this archive holds a registered referral arrangement with the exchange that issues the token, and the record was written to the same risk standard regardless.</description>
    </item>
    <item>
      <title>Tether (USDT): what an attestation actually says</title>
      <link>https://numiscue.com/coins/tether-usdt/</link>
      <guid isPermaLink="true">https://numiscue.com/coins/tether-usdt/</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>Tether publishes quarterly assurance opinions prepared by an accounting firm. Those are attestations, not financial statement audits, and this record spends most of its length on what that distinction actually means: what is examined, who sets the scope, what the conclusion covers, and what it says nothing about. It deliberately quotes no reserve percentages, because those change every quarter and would make the page wrong on a schedule. What it gives instead is the structure — a private issuer, a reserve pool the issuer manages, a quarterly opinion on a report the issuer prepares — plus the practical business of USDT existing on several chains at once.</description>
    </item>
    <item>
      <title>USDC: how its backing differs from Tether&#x27;s</title>
      <link>https://numiscue.com/coins/usdc/</link>
      <guid isPermaLink="true">https://numiscue.com/coins/usdc/</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>USDC and Tether hold the same peg through different plumbing, and this record lays the two structures side by side without ranking them. It covers the reserve fund USDC&#x27;s backing mostly sits in, who manages it, what that vehicle is permitted to hold, the monthly attestation cadence, and the separate matter of the issuer&#x27;s own financial statement audit. It also covers the March 2023 episode when the token traded below a dollar after part of its reserve was disclosed at a bank that failed — the clearest available demonstration that cash held at a bank is a credit position rather than an absence of risk.</description>
    </item>
    <item>
      <title>XRP: the escrow schedule and how supply is released</title>
      <link>https://numiscue.com/coins/xrp/</link>
      <guid isPermaLink="true">https://numiscue.com/coins/xrp/</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>Every XRP that will ever exist was created in 2012. There is no mining, no staking reward and no issuance function, which makes the interesting question not how supply grows but how it reaches the market. The answer is escrow: fifty-five contracts of a billion each, one expiring every month, with whatever goes unused returning to the back of the queue so the schedule stretches rather than ends. This record explains what that mechanism does and does not achieve, and covers the small amount of XRP that every transaction destroys as an anti-spam measure.</description>
    </item>
    <item>
      <title>Solana: the SOL inflation schedule, read properly</title>
      <link>https://numiscue.com/coins/solana/</link>
      <guid isPermaLink="true">https://numiscue.com/coins/solana/</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>Solana&#x27;s token supply follows a published curve with three parameters: a starting inflation rate, an annual reduction applied to that rate, and a long-term floor it approaches without going below. The most common error is applying the reduction to the supply rather than to the rate, so this record works through the arithmetic. It also reports something a static article usually gets wrong: a proposal to double the pace of decay exists, and as of August 2026 it was still under discussion rather than adopted. The record shows both paths and dates the status.</description>
    </item>
    <item>
      <title>Dogecoin: no supply cap, and what that means</title>
      <link>https://numiscue.com/coins/dogecoin/</link>
      <guid isPermaLink="true">https://numiscue.com/coins/dogecoin/</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>Dogecoin has no maximum supply constant and no end date to issuance. It pays a fixed ten thousand coins per block, which works out at roughly five billion a year, forever. Most introductions skip past that to talk about the community; this record treats it as the main event, because fixed issuance against a growing base produces a falling inflation rate with no halving mechanism at all. It also gives space to the project&#x27;s own argument that this does not make supply unlimited, since issuance per block, per day and per year is strictly bounded.</description>
    </item>
    <item>
      <title>Token supply structure: fourteen assets side by side</title>
      <link>https://numiscue.com/tools/supply-structure/</link>
      <guid isPermaLink="true">https://numiscue.com/tools/supply-structure/</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>All fourteen assets in the archive on one sortable table: maximum supply where one exists, what kind of ceiling it is, how new units appear, whether any mechanism destroys them, and whether a schedule governs release. The most useful column is the second one, which distinguishes a consensus rule enforced by every node from a fixed initial mint with no issuance function, from a programme target maintained by an entity, from a ceiling introduced by governance vote. All four get called a hard cap in general coverage, and they are four different kinds of assurance. Circulating supply is deliberately absent.</description>
    </item>
    <item>
      <title>Which chain might this address format belong to?</title>
      <link>https://numiscue.com/tools/address-chain-identifier/</link>
      <guid isPermaLink="true">https://numiscue.com/tools/address-chain-identifier/</guid>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <description>Paste a blockchain address and this page identifies compatible format families, verifies the checksum where the format has one, and says when the intended network cannot be inferred. It handles Bitcoin in both legacy and native segwit forms, EVM addresses including their capitalisation-based checksum, TRON, and Solana. Everything runs in the browser: the hash functions are implemented in the page itself, so nothing you paste is transmitted anywhere and the tool works offline. Where it cannot verify something — XRP uses a different alphabet — it says so rather than implying otherwise.</description>
    </item>
  </channel>
</rss>
