Skip to content
Satoshi Gazette
Data Desk

Method

Every dataset, and where it comes from

Source classes
Chain
Consensus data anyone can reproduce on their own node, on the chain named below.
Mempool view
One operator’s mempool under its relay policy; another node can see a different queue.
Issuer
A filing or an issuer’s own statement, as of the date it gives.
Calculation
The Gazette’s arithmetic over named inputs.
Gossip view
One operator’s node’s view of the public Lightning gossip; another node sees a different graph.
+ Heuristic
Added when a figure rests on a labelling rule rather than a record, such as pool attribution.
  • Fee estimates and the queue

    Mempool viewRead from mempool.space when the page is served, never stored.

    Details: the full rule for Fee estimates and the queue
    Live
    Read when the page loads; the Data Desk page’s card reuses an earlier response and prints its time
    Checks
    Each field is checked on its own. A missing or malformed value prints Not available, never 0, and a rate is never padded up to a whole sat/vB.
    Limits
    • Projected blocks are mempool.space’s template of what would be mined next, filled by fee rate; the last one holds the rest of the queue.
    • Endpoint links answer with a later reading; they are not archived copies.
    Source terms
    mempool.space’s terms of service grant no data licence and forbid no reuse; accuracy is disclaimed.
    Dataset ID
    sg-network-fees
  • Node software on reachable nodes

    Calculation + HeuristicEvery peer in KIT’s network snapshot, by the software it announces.Dated snapshot · KIT snapshot of 13 Nov 2026

    Details: the full rule for Node software on reachable nodes
    Cadence
    Each KIT snapshot day, at most three a run
    Method
    1.2.0
    Formula
    Peers announcing an implementation ÷ every peer in the snapshot
    As of
    13 Nov 2026, 12:52 UTC
    Checks
    The headline counts every reachable clearnet peer KIT’s monitor was connected to when the snapshot was taken; the peers whose connection began within 24 hours sit beside it, not instead of it, because they over-weight nodes that reconnect often. User agents are self-reported and sorted by published rules, first match wins, so the shares count what nodes say they run. The two Knots service flags are counted the same way, as peers announce them: a missing or unreadable services number is unknown, never neither, and no flag says which chain a peer follows. A day is held and nothing is written when the newest snapshot is more than 48 hours old, holds fewer than 1,000 peers or moves more than 25% from the median of the rows before it, or when 2% or more of peers, or 5% or more of those connected within 24 hours, announce no readable software. Rows hold counts only, and a share is printed to one decimal only for 1,000 nodes or more.
    Source terms
    KIT’s snapshots are licensed CC BY 4.0; cited as Neudecker, Till; Grundmann, Matthias; Hartenstein, Hannes. Bitcoin Peer-To-Peer Network Monitoring. Zenodo. doi:10.5281/zenodo.14627525. The Gazette reduces per-peer records to daily counts and republishes no per-peer data.
    Dataset ID
    sg-node-software
  • Node software releases

    Issuerbitcoincore.org’s support windows and advisories, with Knots releases beside them.Dated snapshot · read 15 Nov 2026

    Details: the full rule for Node software releases
    Cadence
    Each release and Bitcoin Core end of life, on its day; advisories as bitcoincore.org lists them
    Refreshed by
    The data job · Node software releases: Its rule →
    Method
    1.2.0
    As of
    15 Nov 2026, 04:30 UTC
    Checks
    Release lines must run newest first with their dates in order, and no advisory or Knots tag may repeat. A date the table does not publish stays blank: a line it marks “after v34.0” stays maintained until that release is dated, never projected. The date in a Knots tag is its version date, not a release date, and GitHub’s feed time is kept apart from it.
    Source terms
    bitcoincore.org is MIT-licensed, every file unless it says otherwise. The Knots releases are read from GitHub’s public Atom feed and its public release record for the MIT-licensed Knots repository; only tags, titles and dates are kept.
    Dataset ID
    sg-core-lifecycle
  • Lightning and BTCPay Server releases

    IssuerReleases of LND, Core Lightning, Eclair and BTCPay Server, from GitHub’s release record.Dated snapshot · GitHub’s release record · read 15 Nov 2026

    Details: the full rule for Lightning and BTCPay Server releases
    Cadence
    No set day
    Refreshed by
    By hand, after review
    Method
    1.0.0
    As of
    11 Nov 2026, 20:41 UTC
    Checks
    Each row is a release in GitHub’s release record for the project’s own repository, with the time GitHub says it was published; a bare tag is not a release. A final release is a tag in the form the project gives its final releases that GitHub does not mark a pre-release, so a release candidate is never one. A release’s notes are read once, when it is new to the file, and kept as a sha256 and a length; a later edit is not followed. A release that leaves the record is marked, never taken out. A read that fails or is partial writes nothing.
    Source terms
    The releases are read from GitHub’s public release record for each project’s repository: LND, MIT; Core Lightning, BSD-MIT; Eclair, Apache-2.0; BTCPay Server, MIT. Only tags, names, times, a digest of the notes and at most one sentence of them are kept.
    Dataset ID
    sg-lightning-releases
  • BIP status

    IssuerEvery BIP’s status in the BIP repository’s own words, and the changes the Gazette has seen.Dated snapshot · bitcoin/bips at commit f9cff97 · read 7 Nov 2026

    Details: the full rule for BIP status
    Cadence
    The data job, at each status change the BIP repository records
    Refreshed by
    The data job · BIP status: Its rule →
    Method
    1.0.0
    As of
    7 Nov 2026, 04:30 UTC
    Checks
    Each row is the BIP’s own preamble, read at one commit of the repository and matched against the repository’s index on number, layer, type and status. A preamble that does not read as BIP 3 lays it out, or disagrees with the index, is held at what was last recorded, with its reason; nothing is guessed. The four statuses are BIP 3’s own words, checked against BIP 3’s text on each read, and nothing is mapped onto them. A status is not an endorsement and does not say a consensus change has activated. A change is recorded on the day the Gazette sees it, not the day it happened, and a recorded change is never rewritten. A read that fails or is partial writes nothing.
    Source terms
    The BIPs repository carries no licence of its own. BIP 3, itself BSD-2-Clause, accepts only freely licensed BIPs and has each new one name its licence in its preamble; some older BIPs name none. The BIPs repository is public on GitHub and is read without an account: its commits feed and its raw files only. Each BIP names its own licence in its preamble where it has one. The Gazette keeps facts from the index and the preambles (number, title, layer, type, status, the date a number was assigned, the BIPs a preamble names as replaced or as a proposed replacement, and a count of author lines) and none of a BIP's text.
    Dataset ID
    sg-bip-status
  • Difficulty period, halvings and subsidy

    ChainThe difficulty period, the halvings and the block subsidy, fixed by block height.

    Details: the full rule for Difficulty period, halvings and subsidy
    Live
    Read when the page loads: on Fees & blocks the newest block height and the retarget projection from mempool.space; on Supply the block the difficulty periods were read through; the rules themselves from Bitcoin Core at one pinned commit
    Formula
    Blocks left in the period: 2,016 − (block height mod 2,016); a halving every 210,000 blocks; the subsidy 50 BTC halved at each, in whole satoshis, 0 sat from block 6,930,000
    Checks
    The count is arithmetic on the block height any node can repeat. The next difficulty and its date are mempool.space’s projection, printed as such until the period ends. A halving’s time is its block’s header time; the next halving has a height and no date. The subsidy follows GetBlockSubsidy in whole satoshis. A missing or malformed height prints Not available, never 0.
    Limits
    • The projected difficulty and its date are mempool.space’s estimate, not the chain’s.
    • A block height read from mempool.space can trail a node’s by a block.
    • Endpoint links answer with a later reading; they are not archived copies.
    Source terms
    mempool.space’s terms of service grant no data licence and forbid no reuse; accuracy is disclaimed. Bitcoin Core is MIT-licensed.
    Dataset ID
    sg-protocol-schedule
  • Public Lightning network

    Gossip viewPublic channels, capacity and nodes a day, as one operator’s node received the gossip.Dated snapshot · public network of 14 Nov 2026 · read 15 Nov 2026

    Details: the full rule for Public Lightning network
    Cadence
    Each day the source has ended, at most three a run
    Refreshed by
    The data job · Public Lightning network: Its rule →
    Method
    1.0.0
    As of
    14 Nov 2026
    Checks
    Each row is the source’s own row for one UTC day, taken once the day has ended by the source’s clock, from a response that already holds the next day’s row. Nodes are the sum of the source’s four node counts by address type, checked on every read against the node total on its latest row. A day with fewer than 1,000 channels or 1,000 nodes, or with channels, nodes or capacity more than 25% from the median of the seven rows before it, is held and nothing is written. A day the source holds no row for is written down as not recorded, never filled. Capacity is kept in satoshis and printed in BTC, cut. Private channels cannot be counted.
    Source terms
    mempool.emzy.de serves mempool’s terms for an unofficial instance, which grant no data licence and forbid no reuse; accuracy is disclaimed.
    Dataset ID
    sg-lightning-network
  • Hashprice at difficulty

    CalculationThe Gazette’s arithmetic on three mempool.space readings, live.

    Details: the full rule for Hashprice at difficulty
    Live
    Read when the page loads; a response is reused for up to five minutes
    Method
    3
    Formula
    (subsidy + average fee) sats × 86,400 × 10¹² ÷ (difficulty × 2³²)
    Checks
    The reward window must be exactly 144 consecutive blocks, with fees no larger than the reward. An input that is missing, or older than its window allows, makes the figure stale or unavailable, never 0. A reading is stale after 15 minutes or a failed refresh and unavailable after six hours; the daily hashrate series, after 36 hours and three days.
    Limits
    • Both totals rest on mempool.space alone.
    Source terms
    mempool.space’s terms of service grant no data licence and forbid no reuse; accuracy is disclaimed.
    Dataset ID
    sg-hashprice
  • Difficulty

    ChainEvery difficulty period since genesis, its difficulty exact from the block header.Dated snapshot · through block 975,789 · read 14 Nov 2026

    Details: the full rule for Difficulty
    Cadence
    The data job, at each retarget (every 2,016 blocks)
    Refreshed by
    The data job · Difficulty: Its rule →
    Method
    1.1.0
    Formula
    0xffff × 2²⁰⁸ ÷ the target its header’s nBits encodes, kept exact, cut to two places
    As of
    14 Nov 2026, 11:54 UTC
    Checks
    Headers were read on mempool.space. Every header read must hash to its block id, link to its parent and meet the target its nBits encodes, and each period’s first block is matched on Blockstream’s Esplora. Each retarget is recomputed by the consensus rule from the period before and must match the header. In blocks 628,992 to 832,607, the periods the reward ledger has read, every header is checked; in every other period, before and after, the 15 headers around the retarget. Difficulty is kept as an exact fraction and cut, never rounded. A period sets a new high only when its difficulty is strictly above every earlier period’s, compared on the exact targets its header bits encode; a stretch without a new high runs from the first block of the period that set the high to the first block of the period that beat it.
    Source terms
    mempool.space’s terms of service grant no data licence and forbid no reuse; accuracy is disclaimed. Blockstream’s public Esplora API, the second operator, states no data terms the Gazette could find; its software is MIT-licensed.
    Dataset ID
    sg-difficulty-ledger
  • Block rewards, fees and pool labels

    Chain + HeuristicReward, fees and pool labels per period, blocks 628,992 to 832,607 so far.Dated snapshot · through block 832,607 · read 1 Oct 2026Read through block 832,607 as of 14 Nov 2026; not level with the chain.

    Details: the full rule for Block rewards, fees and pool labels
    Cadence
    No set day
    Refreshed by
    By hand, after review
    Method
    1.1.0
    As of
    1 Mar 2024, 00:45 UTC
    Checks
    Every block was read from mempool.space, with Blockstream’s Esplora as second operator. Each claimed reward is proved on Blockstream’s Esplora: the block’s full transaction list must rebuild the merkle root in its checked header, and the coinbase must carry its height and pay exactly that reward. History is sampled, 5 blocks a period with the retarget block among them (505 proved so far), and once the ledger has reached its tip the run that adds new blocks proves every one in full. Fees rest on mempool.space alone. The ledger counts on-chain fees only: fees paid to pools out of band are not visible. Before block 628,992 nothing is read, and those periods print blank, never zero. Pool labels are mempool.space’s own. A pool label is a labelling rule, not ownership.
    Source terms
    mempool.space’s terms of service grant no data licence and forbid no reuse; accuracy is disclaimed. Blockstream’s public Esplora API, the second operator, states no data terms the Gazette could find; its software is MIT-licensed. The attribution rules are MIT-licensed.
    Dataset ID
    sg-block-ledger
  • Public miners

    IssuerMined, sold and held per quarter, as the 11 listed miners on the roster filed it.Dated snapshot · quarters through 30 Sep 2026 · read 10 Nov 2026

    Details: the full rule for Public miners
    Cadence
    No set day. A quarter is added when a company’s report for it has been read twice from the filing and every difference settled
    Refreshed by
    By hand, after review
    Method
    1.0.0
    As of
    30 Sep 2026
    Read twice, then checked
    Each figure is read from the filing itself by one reader and read again by a second reader who is shown the place and not the number; a script compares the two and a person settles every difference. Nothing is computed from money, no sale or purchase is inferred from a change in holdings, and nothing is taken from a tracker or from a press release outside EDGAR; a filing’s machine-readable tags are a cross-check only. A figure a filing does not state in units has no number and says why: unknown, not zero. A reported nil is 0. A quarter no report states by itself is derived from stated numbers, each listed with its sign, and its arithmetic reproduces to the satoshi; a quantity stated only for a longer period is kept whole and never divided among its quarters. The first-reported value stands and a later one is recorded beside it. Mined minus sold and the roll-forward remainder are worked out on the page and stored nowhere. A listed parent is shown with its listed subsidiary taken out, so no bitcoin is counted twice. Mined is bitcoin the filing states the company earned in the period from hashrate it ran for its own account, or received from that mining where the filing counts only what was received, under the filing's own name for the number and with the filing's pool-fee basis beside it; a share of a joint venture's production, bitcoin earned by customers whose machines it hosts or who buy its hashrate, and bitcoin received as fees are not mined. Sold is bitcoin the filing states the company sold for cash. Held is the number of bitcoin the filing states on the quarter's last day, with a note saying what that number contains. A company is on the roster when it files its quarterly and annual reports with the SEC on the forms United States companies use (10-Q and 10-K) and those reports state that it mined at least 100 bitcoin for its own account in a calendar quarter of the window. It enters with the first quarter its reports give for it and is never removed: a company that stops mining, merges or stops filing is closed with a date and a reason, and its rows stay. A listed parent that consolidates a company on the roster is carried beside it, read from its own consolidated reports and shown with the subsidiary taken out, so that no bitcoin is counted twice. Companies that report on the forms foreign issuers use (20-F or 40-F, with interim results on 6-K) are named and not read yet. The roster was set on 5 October 2026. Miners listed only outside the United States, private miners and state miners are outside it.
    Limits
    • These are the statements of the SEC registrants named, not of public miners as a whole: the companies named as not read have no rows, and miners listed only outside the United States, private miners and state miners are outside the file. Figures from quarterly reports are unaudited. A company can sell bitcoin it mined in earlier periods, so sold can exceed mined; pledged, posted and lent bitcoin are not sold; and a quarter the filings do not state in units is unknown, not zero. Nothing before 1 January 2025 is here, so the selling of 2022 lies outside the window.
    Source terms
    SEC filings are US federal records in the public domain; each row cites its accession. The SEC’s fair-access notice allows ten requests a second from a declared user agent; the reader stays under five.
    Dataset ID
    sg-public-miners
  • Pool block share

    Chain + Heuristicmempool.space’s pool labels for three windows, read once a week and filed.

    Details: the full rule for Pool block share
    Cadence
    Once a week
    Refreshed by
    The data job · Pool block share: Its rule →
    Method
    1.1.0
    Formula
    Blocks attributed to a label ÷ every block in its window, to two places; the three labels’ hashrate share is a Wilson score 95% interval on the week’s blocks, rounded outward to whole percents
    As of
    11 Nov 2026, 04:30 UTC
    Checks
    Each window’s rows add up to its block total; a longer window holds no fewer blocks than a shorter one; the three windows rank the same three labels first, in the same order; the three responses are served within 60 seconds of each other.
    Limits
    • The snapshot is dated by the latest HTTP Date header mempool.space served in the session, the source’s own clock; the counts can trail it by the cache lifetime the responses declared, which the method states, and the three windows are not an atomic chain-tip snapshot.
    • Labels change when mempool.space’s identification rules change, and past blocks can be re-labelled.
    • The interval covers block-finding luck only, not attribution error.
    Source terms
    mempool.space’s terms of service grant no data licence and forbid no reuse; accuracy is disclaimed. The attribution rules are MIT-licensed.
    Dataset ID
    sg-pool-blocks
  • Company treasuries

    IssuerEach company’s latest filing.

    Details: the full rule for Company treasuries
    Cadence
    Strategy’s row every day; the others on review
    Refreshed by
    The data job (Strategy’s row); by hand or read from the filing by Satoshi Gazette (the others) · Company treasuries: Its rule →
    Method
    2
    Formula
    Sum the latest active verified BTC observation for each selected entity using exact decimal arithmetic.
    As of
    8 Nov 2026
    Checks
    Companies are ordered by disclosed BTC amount from largest to smallest, with alphabetical tie-breaking; no complete-market rank is assigned. A later filing appends a new observation and never rewrites the one before it. Figures are shortened for reading, never rounded up: whole bitcoin above 10,000, one decimal between 100 and 10,000, every satoshi below that, so a printed figure is never larger than the disclosure it came from; the disclosures keep their exact amounts. Strategy’s row moves only when its 8-K’s own BTC Update table states the holding, a second, independent read of the table agrees cell for cell, and the move is 5 percent or less. A sale, an amendment, a restatement or a sentence instead of the table goes to a person.
    Limits
    • ETFs, funds, trusts, custodians, exchanges, and client assets.
    • governments and sovereign reserves.
    • wallet-attribution estimates and secondary-source-only claims.
    • synthetic or tokenized Bitcoin exposure.
    • mNAV, until a licensed, reliable equity-price feed is available.
    • Secondary database rows without a primary source.
    Source terms
    SEC filings are US federal records in the public domain; each row cites its accession. Metaplanet Inc.: terms not yet reviewed, so the row is read by hand.
    Dataset ID
    sg-treasury-ledger
  • Strategy’s filed totals

    IssuerEvery bitcoin total Strategy has stated in an 8-K, 10-Q or 10-K since 2020, one row each.Dated snapshot · filings through 9 Nov 2026 · read 10 Nov 2026

    Details: the full rule for Strategy’s filed totals
    Cadence
    Each new filing, once Strategy’s row in Company treasuries reaches its date
    Refreshed by
    The data job · Strategy’s filed totals: Its rule →
    Method
    1.0.0
    As of
    8 Nov 2026
    Checks
    A total is taken only from a sentence or a table cell that states it with its own date, in a wording the file lists; nothing is added up from purchases. From a 10-Q or 10-K only totals dated on or after its period end are taken. Where two filings state one date both rows are kept and the later is marked as restating. Each step is checked against the purchases and sales its own 8-K reports and is flagged, never corrected, when they differ. A filing that mentions a holding the reader cannot date is listed as unparsed, not skipped. These are filed totals, not wallet balances.
    Source terms
    SEC filings are US federal records in the public domain; each row cites its accession. The SEC’s fair-access notice allows ten requests a second from a declared user agent; the reader stays under five.
    Dataset ID
    sg-strategy-filings
  • Claims floor

    CalculationEach holder’s latest disclosure, summed against issued supply at a pinned block.

    Details: the full rule for Claims floor
    Cadence
    When Strategy’s row or the spot ETF rows move; the other rows on review
    Refreshed by
    The data job (when Strategy’s row or the spot ETF rows move); by hand or read from the filing by Satoshi Gazette (the other rows) · Claims floor: Its rule →
    Method
    2.3.0
    Formula
    The sum of disclosures ÷ issued supply at the pinned block, cut to four places
    As of
    10 Nov 2026
    Checks
    Every counted quantity must be a named entity row with its own exact BTC amount, as-of date, primary source and document locator. Only holdings disclosed by the holder in a filing, an audited report, or a direct public statement are counted. Anything requiring an inference about who controls an address is excluded, so no undisclosed holding can enter the figure. A claim on a claim is not counted again: a company's row counts the bitcoin the company's own disclosure states it holds, and a fund's row the bitcoin on the fund's own schedule of investments. Shares of a fund are a claim on bitcoin already in that fund's row, so they are never counted as bitcoin in a company's row or in another fund's, and where one counted company consolidates another, the parent's row leaves out the bitcoin in the subsidiary's row. Issued supply is computed deterministically from the pinned block height using the protocol's own subsidy schedule: 50 BTC for the first 210,000 blocks, halving every 210,000 blocks thereafter. It is not fetched from a third party. Percentages are computed against issued supply at the pinned block height using exact decimal arithmetic. The floor is cut to four places, never rounded up, and the unclassified remainder is 100 minus it, so the two always sum to 100. The pinned block is never older than the newest disclosure the floor counts; older disclosures keep their own dates. Figures are shortened for reading, never rounded up: whole bitcoin above 10,000, one decimal between 100 and 10,000, every satoshi below that, so a printed figure is never larger than the disclosure it came from; the disclosures keep their exact amounts. The company rows must match Company treasuries to the unit or nothing is written. The spot ETF rows must equal each read, listed trust’s latest filed quantity in the spot ETF dataset: the site’s tests hold the two files to each other, and the data job runs those tests before it publishes.
    Limits
    • Holders that disclose nothing are left out.
    • A holder that sold after its disclosure could hold less at the pinned block; the floor counts what each disclosure states as of its own date.
    • The unclassified remainder is not evidence of self-custody.
    • Exchange reserves, which require address-clustering heuristics rather than disclosure.
    • Custodians who publish no holdings.
    • Any inference about who controls an unlabelled address.
    • Lost, dormant, and never-moved coins, whose status nobody can verify.
    Source terms
    SEC filings are US federal records in the public domain; each row cites its accession. El Salvador’s National Bitcoin Office publishes its wallet through an endpoint operated by the company that runs mempool.space, so mempool.space’s terms govern it: no data licence, no reuse forbidden. Metaplanet Inc.: terms not yet reviewed, so the row is read by hand.
    Dataset ID
    sg-claims-floor
  • Spot ETF trusts

    IssuerBitcoin at each quarter end in 14 of the 16 trusts on the list, from their 10-Q and 10-K.Dated snapshot · quarter ends through 30 Sep 2026 · read 13 Nov 2026

    Details: the full rule for Spot ETF trusts
    Cadence
    The data job, at each report a trust files, in reads at least seven days apart: in the rows so far a quarterly report was filed 32 to 48 days after its period end, and an annual report 56 to 92 days after
    Refreshed by
    The data job · Spot ETF trusts: Its rule →
    Method
    1.0.0
    As of
    30 Sep 2026
    Checks
    Each quantity is the Schedule of Investments row for bitcoin in the trust’s own report, dated by the cell’s inline XBRL context where the filing tags it with an instant, and by the schedule’s heading where the tag names a period or the cell has no tag; a tag and a heading must agree, and the date must be the report’s period end. A report the rule cannot read stops the run and nothing is written. A restated figure is kept beside the one it restates. A quarter not yet reported has no row and nothing is carried forward. Trusts the rule cannot read are listed as not read, with the reason, and are in no total: unknown, not zero. No value, price or flow is read. These are filed quarter-end quantities, not today’s holdings.
    Source terms
    SEC filings are US federal records in the public domain; each row cites its accession. The Commission’s orders the list rests on are federal records too. The SEC’s fair-access notice allows ten requests a second from a declared user agent; the reader stays under five.
    Dataset ID
    sg-etf-trusts
  • El Salvador’s disclosed wallet

    ChainThe 20 addresses El Salvador discloses, re-summed on a second operator’s index.Dated snapshot · at block 975,741 · read 14 Nov 2026

    Details: the full rule for El Salvador’s disclosed wallet
    Cadence
    Each block that moved the balance. The claims floor keeps the endpoint’s reading of 18 Sep 2026 until a person moves its row
    Method
    1.0.0
    As of
    14 Nov 2026, 04:06 UTC
    Checks
    The endpoint is operated by Mempool Holdings S.A. de C.V., which runs mempool.space, so every disclosed address is re-summed on Blockstream’s Esplora while its tip holds at one block, and a reading is kept only when the two agree to the satoshi, address by address. Unconfirmed amounts are kept apart from the total. Coins outside the disclosed addresses are unknown, not zero.
    Source terms
    El Salvador’s National Bitcoin Office publishes its wallet through an endpoint operated by the company that runs mempool.space, so mempool.space’s terms govern it: no data licence, no reuse forbidden. Blockstream’s public Esplora API, the second operator, states no data terms the Gazette could find; its software is MIT-licensed.
    Dataset ID
    sg-onbtc-wallet

Downloads →Dictionary →

Which chain the figures describe

Every figure marked Chain in the register above, and every reading the Gazette takes from mempool.space or Blockstream’s Esplora, describes one chain: the one those two operators serve, under Bitcoin Core’s consensus rules. The Gazette names it by its block at height 961,632.

Block hash
00000000000000000000d1e01392faa65ceeaed307f0a3159144b84146ff24ba
Timestamp
Version
0x20006000, which does not set bit 4
Read
On Blockstream’s Esplora, 2 Oct 2026; the same hash opens difficulty period 477 in the Difficulty dataset, read from mempool.space.

BIP 110 had nodes reject any block from 961,632 to 963,647 that does not signal bit 4, and this block does not. Bitcoin Knots releases that enforce BIP 110, from 29.3.knots20260508 (published 9 May 2026), and from 29.4.1 (published 2 Sep 2026) a BLAKE2b proof of work, follow a different chain, which these figures do not cover.

The Gazette reads the chain through those two operators and runs no node of its own.

What the data job publishes

One job, the data job, runs once a day. It may change the datasets named in the rules below, each only from the primary record its rule names, under that rule’s own checks, and nothing else.

Filed as entries

  1. Strategy’s row in Company treasuries, every day.

    It reads Strategy’s newest 8-K on EDGAR and moves the row only when the filing’s own BTC Update table states the holding, a second read of the raw table that does not use the first reader agrees cell for cell, and the move is 5 percent or less.

    Writes nothing and waits for a person when:

    • any filing in the window reports bitcoin sold
    • the filing is an amended 8-K, a restatement, or one of two filings that disagree about a date
    • the holding is stated in a sentence rather than the table, or called approximate
    • the move is more than 5 percent, or the reported purchases miss the change by more than 1 BTC
    • the second read disagrees or a filing in the window cannot be settled
    • an earlier reading is still waiting for a person

    While a filing waits and the row is older than it, Company treasuries and the claims floor say so beside their figure, name the filing and print no figure from it.

  2. The claims floor, when that row or the spot ETF rows move.

    The company rows are copied from Company treasuries and must match it to the unit; the spot ETF rows take each listed trust’s latest filed quantity from the spot ETF reports the job files; issued supply is re-pinned at the chain tip when Strategy’s row moves, and the floor is recomputed with exact arithmetic, cut, never rounded up; the job leaves the state row as it is: a person moves it.

  3. The pool sample, once a week.

    The three mempool.space windows are read through the site’s own validator, and the responses are filed beside the snapshot.

    Writes nothing when:

    • a read fails or is partial
  4. Difficulty, at each retarget.

    It reads block headers alone: every header must hash to its block id, link to its parent and meet the target its own nBits encodes; the retarget’s nBits must be the one the consensus rule gives from the period before; and the retarget block’s hash must match on a second operator.

    Writes nothing when:

    • a read fails or is partial
    • a read finds more than three new retargets, and waits for a person
  5. BIP statuses, at each change the repository records.

    It reads the BIP repository at one commit, every BIP’s own preamble against the repository’s index on number, layer, type and status, and the four statuses, Draft, Complete, Deployed and Closed, against BIP 3’s own text; the status changes one read records, one to five, are one entry, dated the day the Gazette saw them, and a recorded change is never rewritten.

    Writes nothing when:

    • a read fails or is partial
    • a newer commit changes no status
    • a read finds more than five status changes, and waits for a person
  6. Node software releases, as each project publishes them.

    It files a release of software that follows the chain the Gazette covers and that 1 percent or more of the reachable nodes in KIT’s newest snapshot announce, peers announcing Knots’ BLAKE2b flag left out: a Bitcoin Core release on the day its bitcoincore.org page gives, a Bitcoin Knots release on the day GitHub published it, and a Bitcoin Core line’s end of life on the day bitcoincore.org’s lifecycle table gives; release candidates are not filed, nor Knots releases from 29.3.knots20260508 on, which change Knots’ chain rules. It files a Bitcoin Core security advisory new to bitcoincore.org’s index from its own post, read once: its title, its severity and the versions affected in the post’s own words, and the releases its timeline lists with a fix.

    Writes nothing and waits for a person when:

    • a date on file reads differently
    • a date falls a day after the read
    • more than three releases come at once
    • there is no KIT snapshot from the week before
    • an advisory’s post states its severity, the versions affected or a fix in no shape the reader reads
    • a release and an advisory, or more than three advisories, come at once
  7. El Salvador’s disclosed wallet, block by block.

    It reads the address list El Salvador’s National Bitcoin Office publishes and re-sums every address on a second operator’s index, Blockstream’s Esplora, while the chain tip holds at one block; each block that moved the balance is one row, a block that credits two bitcoin or more is filed as an entry, and every other row, the usual one-bitcoin step among them, is added with no entry.

    Writes nothing when:

    • the Office’s own total and the re-sum do not agree to the satoshi, address by address
    • a read finds a debit of 0.01 BTC or more, and waits for a person
    • a read finds a debit of any size in a block that credits two bitcoin or more, and waits for a person
    • a read finds more than three credits of two bitcoin or more, and waits for a person
    • a read finds a saved block that has left the chain, and waits for a person
    • the address list changes, and waits for a person
  8. Spot ETF trusts, at most once a week.

    It reads each listed trust’s 10-Q and 10-K on EDGAR for the Schedule of Investments row for bitcoin, dated by the report’s own period end, on which the cell’s tag and the schedule’s heading must agree; the first-filed reports one read adds are one entry, and the claims floor’s spot ETF rows move to them as a second entry, filed with the first or not at all.

    Writes nothing when:

    • a read fails or a report cannot be read
    • a report restates a figure already on file, and waits for a person
    • a read would change or drop a report already on file, and waits for a person
    • the reports read cannot be put into one entry, and waits for a person
    • a spot ETF row would leave the claims floor, and waits for a person

Only kept level, with no entry

  • Node software on reachable nodes, each snapshot day.

    It reads one source, KIT’s daily snapshot of the reachable nodes its monitor is connected to, and records each snapshot file’s sha256 beside the row counted from it; it adds one row a snapshot day, at most three a run and oldest first, and never changes a recorded count; each Core release line is classed against the release table on file, and each row records the day that table was read.

    Writes nothing when:

    • a read fails or is partial
    • a day has fewer than 1,000 peers, and waits for a person
    • 2 percent or more of a day’s peers, or 5 percent or more of those connected within 24 hours, announce no readable software, and waits for a person
    • a day is more than 25 percent from the median of the rows before it, and waits for a person

    No day is added until then. It files no entry.

  • Strategy’s filed totals, behind Company treasuries.

    It reads EDGAR’s listing of Strategy’s filings and each new 8-K, 10-Q and 10-K, and takes every total a filing states with its own date; nothing is added up from purchases; a filing’s totals are added only on a morning the job has read Strategy’s filings without holding one for a person, and only when each is dated on or before Strategy’s row in Company treasuries and, on that row’s own date, states the row’s figure.

    Writes nothing and waits for a person when:

    • a filing waits for a person
    • a total is dated after that row
    • a 10-Q or 10-K total is for a date no 8-K stated
    • a total for a date already filed states another figure
    • a filing cannot be read for a total

    So does every filing after it. It files no entry: the Company treasuries entry is the record of the filing.

  • The public Lightning network, each day.

    It reads one source, mempool.emzy.de’s Lightning statistics, as one operator’s node received the gossip; it adds one row for each day the source has ended, at most three a run and oldest first, and never changes a recorded row.

    Writes nothing when:

    • a read fails or is partial
    • the source holds no row for its own day
    • a day has fewer than 1,000 channels or 1,000 nodes, and waits for a person
    • channels, nodes or capacity are more than 25 percent from the median of the rows before, and waits for a person

    No day is added until then. It files no entry.

These eight things are what the Gazette files into its record with no person reading them first: they are filed by the data job, from the records named above, under the rules above. Each entry it files is marked in the record below, “Filed by the data job; no person read it first”, and the mark leads here. It also keeps five dated series level with their sources, with no entry and no person reading the new rows first: Bitcoin Core’s security advisories, as bitcoincore.org lists them; the software reachable nodes announce, one row a snapshot day; El Salvador’s disclosed wallet, block by block; Strategy’s bitcoin totals as its 8-K, 10-Q and 10-K filings state them, never ahead of its row in Company treasuries; and the public Lightning network’s channels, capacity and nodes, one row a day. Each of those prints the block or the day it runs through, and the job’s last report names what it published. Every Wire, Story and Brief is read by an editor before it goes live. The job files figures and the template sentences of its entries in the record, never a Wire, Story or Brief. Satoshi Gazette’s AI also files what it reads from a filing with no person reading it first, under the mark “Read from the filing by Satoshi Gazette”.

An editor can switch off the job’s publishing, or hold one dataset; a held dataset keeps its last figure and date. Today the switch is on, and no dataset is held. The job last reported on 15 Nov 2026 at 04:30 UTC: it published the node software releases and the public Lightning network, and nothing failed.

Every other row is added by a person or read from its filing by Satoshi Gazette; every method change and every correction is filed in the record below.

No price, no affiliate links

No Data Desk page carries an affiliate, exchange or referral link, and no market price feeds any Data Desk figure: the Gazette states amounts in bitcoin or sats and fee rates in sat/vB, and converts none into a currency. Where a company’s filing states what a purchase cost or how it was funded, Company treasuries’ funding and limitation notes repeat the filing’s own dollar amounts. The ticker’s 1 BTC and 1 sat are the site’s only price; no Data Desk figure uses it.

The record

  1. Difficulty

    Difficulty fell 9.12 percent at block 975,744

    Difficulty fell 9.12 percent at block 975,744 on 14 November 2026, to 134,823,837,323,272.65 from 148,364,561,003,867.39. On the subsidy alone, 3.125 BTC a block at that height, one TH/s earns an expected 46.63 sats a day.

    Difficulty fell 9.12 percent at block 975,744: Hashprice & difficulty →Difficulty fell 9.12 percent at block 975,744: This entry’s own page →

    Filed by the data job; no person read it first →

  2. Spot ETF trusts

    Spot ETF trusts: ten trusts filed reports for 30 September 2026

    IBIT: 801,033 bitcoin at 30 September, against 734,261 at 30 June; 10-Q of 6 November. GBTC: 126,987 bitcoin at 30 September, against 138,505 at 30 June; 10-Q of 5 November. FBTC: 183,167 bitcoin at 30 September, against 174,383 at 30 June; 10-Q of 6 November. ARKB: 34,578 bitcoin at 30 September, against 32,178 at 30 June; 10-Q of 6 November. BITB: 37,926 bitcoin at 30 September, against 36,207 at 30 June; 10-Q of 6 November. BTCO: 5,102 bitcoin at 30 September, against 5,345 at 30 June; 10-Q of 6 November. BRRR: 5,706 bitcoin at 30 September, against 5,864 at 30 June; 10-Q of 12 November. BTC: 63,087 bitcoin at 30 September, against 54,280 at 30 June; 10-Q of 5 November. OBTC: 933 bitcoin at 30 September, against 945 at 30 June; 10-Q of 12 November. BITA: 777 bitcoin at 30 September, against 484 at 30 June; 10-Q of 6 November. Ten of the trusts the Gazette reads have reported for 30 September 2026. These are quarter-end quantities from reports filed weeks later, not today's holdings.

    Spot ETF trusts: ten trusts filed reports for 30 September 2026: Claims floor →Spot ETF trusts: ten trusts filed reports for 30 September 2026: This entry’s own page →

    Filed by the data job; no person read it first →

  3. Claims floor

    Spot ETF reports moved the floor to 11.7546 percent at block 975,256

    The spot ETF category moves from 1,211,728 to 1,288,573 BTC with ten new filed figures, so the disclosed floor is 2,363,880 BTC, 11.7546 percent of the 20,110,178.125 BTC issued at block 975,256, against 11.3725 percent before. The company rows, the state row and the block are unchanged.

    Spot ETF reports moved the floor to 11.7546 percent at block 975,256: Claims floor →Spot ETF reports moved the floor to 11.7546 percent at block 975,256: This entry’s own page →

    Filed by the data job; no person read it first →

Earlier changes (60)
  1. Pool block share

    The three largest pool labels' one-week share fell to 61.56 percent

    The top three labels, Foundry USA, AntPool and F2Pool, hold 559 of 908 blocks in the one-week window, 61.56 percent, against 61.73 percent on 4 November. The one-month window is 62.65 percent and the three-month 61.20 percent. The previous snapshot and the endpoint responses are preserved beside it.

    The three largest pool labels' one-week share fell to 61.56 percent: Pools →The three largest pool labels' one-week share fell to 61.56 percent: This entry’s own page →

    Filed by the data job; no person read it first →

  2. Company treasuries

    Strategy advanced to 850,364 BTC as of 8 November

    Strategy's 8-K of 9 November reports 850,364 BTC as of 8 November, with 1,036 bought from 2 to 8 November. The row had stood at 849,327 as of 1 November, and the companies’ total moves from 1,066,492 to 1,067,529 BTC. The filing states whole bitcoin and does not reconcile to the unit: 1,036 bought against a 1,037 change in the filed aggregates, and Company treasuries records the change in the aggregates.

    Strategy advanced to 850,364 BTC as of 8 November: Company treasuries →Strategy advanced to 850,364 BTC as of 8 November: This entry’s own page →

    Filed by the data job; no person read it first →

  3. Claims floor

    Strategy's filing raised its holding by 1,037 BTC; the floor is 11.3725 percent at block 975,256

    The corporate category rises by 1,037 BTC to 1,067,529, so the disclosed floor is 2,287,035 BTC, 11.3725 percent of the 20,110,178.125 BTC issued at block 975,256, against 11.3688 percent at block 974,399. The ETF and state rows are unchanged.

    Strategy's filing raised its holding by 1,037 BTC; the floor is 11.3725 percent at block 975,256: Claims floor →Strategy's filing raised its holding by 1,037 BTC; the floor is 11.3725 percent at block 975,256: This entry’s own page →

    Filed by the data job; no person read it first →

  4. Method

    The data job files spot ETF reports, and the claims floor’s spot ETF rows with them

    From this entry’s day the Gazette’s data job files the reports the spot ETF trusts file, at most once a week, one entry a read, and moves the claims floor’s spot ETF rows with them in a second entry, under the rules on the method page.

    The data job files spot ETF reports, and the claims floor’s spot ETF rows with them: This entry’s own page →

  5. BIP status

    BIP 394 is listed as Draft; no earlier status on record

    The BIP repository lists BIP 394 as Draft; the Gazette had recorded no status for it before. The Gazette saw the change on 7 November 2026 at commit f9cff97; the repository may have made it on any day since the Gazette's previous read. A status is the repository's label for a document: it is not an endorsement, and it does not say a consensus change has activated.

    BIP 394 is listed as Draft; no earlier status on record: Protocol →BIP 394 is listed as Draft; no earlier status on record: This entry’s own page →

    Filed by the data job; no person read it first →

  6. Pool block share

    The three largest pool labels' one-week share fell to 61.73 percent

    The top three labels, Foundry USA, AntPool and F2Pool, hold 608 of 985 blocks in the one-week window, 61.73 percent, against 63.91 percent on 28 October. The one-month window is 63.15 percent and the three-month 60.96 percent. The previous snapshot and the endpoint responses are preserved beside it.

    The three largest pool labels' one-week share fell to 61.73 percent: Pools →The three largest pool labels' one-week share fell to 61.73 percent: This entry’s own page →

    Filed by the data job; no person read it first →

  7. BIP status

    Two BIP status changes seen at commit 61ff3f1

    The BIP repository lists BIP 459 as Draft; the Gazette had recorded no status for it before. The BIP repository lists BIP 460 as Draft; the Gazette had recorded no status for it before. The Gazette saw the changes on 4 November 2026 at commit 61ff3f1; the repository may have made them on any day since the Gazette's previous read. A status is the repository's label for a document: it is not an endorsement, and it does not say a consensus change has activated.

    Two BIP status changes seen at commit 61ff3f1: Protocol →Two BIP status changes seen at commit 61ff3f1: This entry’s own page →

    Filed by the data job; no person read it first →

  8. Company treasuries

    Strategy advanced to 849,327 BTC as of 1 November

    Strategy's 8-K of 2 November reports 849,327 BTC as of 1 November, with 811 bought from 26 October to 1 November. The row had stood at 848,517 as of 25 October, and the companies’ total moves from 1,065,682 to 1,066,492 BTC. The filing states whole bitcoin and does not reconcile to the unit: 811 bought against an 810 change in the filed aggregates, and Company treasuries records the change in the aggregates.

    Strategy advanced to 849,327 BTC as of 1 November: Company treasuries →Strategy advanced to 849,327 BTC as of 1 November: This entry’s own page →

    Read from the filing by Satoshi Gazette

  9. Claims floor

    Strategy's filing raised its holding by 810 BTC; the floor is 11.3688 percent at block 974,399

    The corporate category rises by 810 BTC to 1,066,492, so the disclosed floor is 2,285,998 BTC, 11.3688 percent of the 20,107,500 BTC issued at block 974,399, against 11.3659 percent at block 973,795. The ETF and state rows are unchanged.

    Strategy's filing raised its holding by 810 BTC; the floor is 11.3688 percent at block 974,399: Claims floor →Strategy's filing raised its holding by 810 BTC; the floor is 11.3688 percent at block 974,399: This entry’s own page →

    Read from the filing by Satoshi Gazette

  10. BIP status

    BIP 458 is listed as Draft; no earlier status on record

    The BIP repository lists BIP 458 as Draft; the Gazette had recorded no status for it before. The Gazette saw the change on 3 November 2026 at commit ada3419; the repository may have made it on any day since the Gazette's previous read. A status is the repository's label for a document: it is not an endorsement, and it does not say a consensus change has activated.

    BIP 458 is listed as Draft; no earlier status on record: Protocol →BIP 458 is listed as Draft; no earlier status on record: This entry’s own page →

    Filed by the data job; no person read it first →

  11. Method

    The data job keeps the public Lightning network level

    From this entry’s day the Gazette’s data job keeps the public Lightning network level: it adds one row for each day mempool.emzy.de’s statistics have ended, at most three a run, with no entry in this log and no person reading the new rows first. A day the reader’s own checks refuse waits for a person.

    The data job keeps the public Lightning network level: This entry’s own page →

  12. Method

    Node counts: a line of its own for peers connected within 24 hours

    A day now stops when 2 percent of all connected peers announce no readable software, or 5 percent of those connected within 24 hours; the second figure was 2 percent. The days of 22 to 30 October were recorded under this rule, three of which the old one stopped, and 16 October stays not recorded.

    Node counts: a line of its own for peers connected within 24 hours: This entry’s own page →

  13. Node software releases

    Bitcoin Core 31.2, 30.4 and 29.5 are released

    bitcoincore.org's release pages date Bitcoin Core 31.2 to 28 October 2026, 30.4 to 28 October 2026 and 29.5 to 28 October 2026. In KIT's snapshot of 30 October 2026, 8,076 of the 9,368 reachable nodes its monitor was connected to announced a Bitcoin Core version. A version is what a peer announces.

    Bitcoin Core 31.2, 30.4 and 29.5 are released: Nodes & releases →Bitcoin Core 31.2, 30.4 and 29.5 are released: This entry’s own page →

    Read from the filing by Satoshi Gazette

  14. Node software releases

    Bitcoin Core 32.1 is released and 29.x reaches end of life

    bitcoincore.org's release page dates Bitcoin Core 32.1 to 27 October 2026. bitcoincore.org's lifecycle table dates the end of life of Bitcoin Core 29.x to 27 October 2026. In KIT's snapshot of 30 October 2026, 8,076 of the 9,368 reachable nodes its monitor was connected to announced a Bitcoin Core version, 596 of them a 29.x version. A version is what a peer announces.

    Bitcoin Core 32.1 is released and 29.x reaches end of life: Nodes & releases →Bitcoin Core 32.1 is released and 29.x reaches end of life: This entry’s own page →

    Read from the filing by Satoshi Gazette

  15. Method

    A third mark on the record: read from the filing by Satoshi Gazette

    From this entry’s day an entry Satoshi Gazette’s AI read from the filing and filed, with no person reading it first, says so: Read from the filing by Satoshi Gazette. The six entries of 29 and 30 October on Strategy, Strive and Metaplanet take this mark. They had said a person filed them, and no person had read those filings. Their figures do not change.

    A third mark on the record: read from the filing by Satoshi Gazette: This entry’s own page →

  16. Company treasuries

    Metaplanet advanced to 44,000 BTC as of 30 September

    Metaplanet's notice of 5 October reports 44,000 BTC as of 30 September, with 1,000 bought from 1 July to 30 September on a net basis: the notice states 10,000 BTC sold and 11,000 bought in the quarter, a sale and repurchase to demonstrate liquidity. The row had stood at 43,000 as of 30 June, and the companies’ total moves from 1,064,682 to 1,065,682 BTC.

    Metaplanet advanced to 44,000 BTC as of 30 September: Company treasuries →Metaplanet advanced to 44,000 BTC as of 30 September: This entry’s own page →

    Read from the filing by Satoshi Gazette

  17. Claims floor

    Metaplanet's filing raised its holding by 1,000 BTC; the floor is 11.3659 percent at block 973,795

    The corporate category rises by 1,000 BTC to 1,065,682, so the disclosed floor is 2,285,188 BTC, 11.3659 percent of the 20,105,612.5 BTC issued at block 973,795, against 11.3609 percent before. The ETF and state rows and the observation height are unchanged.

    Metaplanet's filing raised its holding by 1,000 BTC; the floor is 11.3659 percent at block 973,795: Claims floor →Metaplanet's filing raised its holding by 1,000 BTC; the floor is 11.3659 percent at block 973,795: This entry’s own page →

    Read from the filing by Satoshi Gazette

  18. Company treasuries

    Strive advanced to 43,000 BTC as of 23 October

    Strive's 8-K of 26 October reports 43,000 BTC as of 23 October, with 6,182 bought from 17 to 23 October. The row had stood at 23,156 as of 28 August, and the companies’ total moves from 1,044,838 to 1,064,682 BTC.

    Strive advanced to 43,000 BTC as of 23 October: Company treasuries →Strive advanced to 43,000 BTC as of 23 October: This entry’s own page →

    Read from the filing by Satoshi Gazette

  19. Claims floor

    Strive's filing raised its holding by 19,844 BTC; the floor is 11.3609 percent at block 973,795

    The corporate category rises by 19,844 BTC to 1,064,682, so the disclosed floor is 2,284,188 BTC, 11.3609 percent of the 20,105,612.5 BTC issued at block 973,795, against 11.2624 percent at block 973,692. The ETF and state rows are unchanged.

    Strive's filing raised its holding by 19,844 BTC; the floor is 11.3609 percent at block 973,795: Claims floor →Strive's filing raised its holding by 19,844 BTC; the floor is 11.3609 percent at block 973,795: This entry’s own page →

    Read from the filing by Satoshi Gazette

  20. Difficulty

    Difficulty rose 5.53 percent at block 973,728

    Difficulty rose 5.53 percent at block 973,728 on 29 October 2026, to 148,364,561,003,867.39 from 140,577,680,051,919.62. On the subsidy alone, 3.125 BTC a block at that height, one TH/s earns an expected 42.37 sats a day.

    Difficulty rose 5.53 percent at block 973,728: Hashprice & difficulty →Difficulty rose 5.53 percent at block 973,728: This entry’s own page →

    Filed by the data job; no person read it first →

  21. BIP status

    BIP 139 is listed as Draft; no earlier status on record

    The BIP repository lists BIP 139 as Draft; the Gazette had recorded no status for it before. The Gazette saw the change on 30 October 2026 at commit 5aadddb; the repository may have made it on any day since the Gazette's previous read. A status is the repository's label for a document: it is not an endorsement, and it does not say a consensus change has activated.

    BIP 139 is listed as Draft; no earlier status on record: Protocol →BIP 139 is listed as Draft; no earlier status on record: This entry’s own page →

    Filed by the data job; no person read it first →

  22. Method

    The data job files BIP status changes

    From this entry’s day the Gazette’s data job files the status changes the BIP repository records, one entry a read, under the rule on the method page.

    The data job files BIP status changes: This entry’s own page →

  23. Company treasuries

    Strategy held 848,517 BTC as of 25 October

    Strategy's 8-K of 26 October reports 848,517 BTC as of 25 October. The row had stood at 848,517 as of 18 October, and the companies’ total stays at 1,044,838 BTC.

    Strategy held 848,517 BTC as of 25 October: Company treasuries →Strategy held 848,517 BTC as of 25 October: This entry’s own page →

    Read from the filing by Satoshi Gazette

  24. Claims floor

    Strategy's filing left its holding unchanged; the floor is 11.2624 percent at block 973,692

    The corporate category is unchanged at 1,044,838 BTC, and so is the disclosed floor of 2,264,344 BTC. It is 11.2624 percent of the 20,105,290.625 BTC issued at block 973,692, against 11.2649 percent at block 972,262: the percent moved only because issued supply grew at the new height. The ETF and state rows are unchanged.

    Strategy's filing left its holding unchanged; the floor is 11.2624 percent at block 973,692: Claims floor →Strategy's filing left its holding unchanged; the floor is 11.2624 percent at block 973,692: This entry’s own page →

    Read from the filing by Satoshi Gazette

  25. Pool block share

    The three largest pool labels' one-week share rose to 63.91 percent

    The top three labels, Foundry USA, AntPool and F2Pool, hold 689 of 1,078 blocks in the one-week window, 63.91 percent, against 62.39 percent on 21 October. The one-month window is 63.59 percent and the three-month 60.90 percent. The previous snapshot and the endpoint responses are preserved beside it.

    The three largest pool labels' one-week share rose to 63.91 percent: Pools →The three largest pool labels' one-week share rose to 63.91 percent: This entry’s own page →

    Filed by the data job; no person read it first →

  26. Method

    The data job keeps Strategy’s filed totals level, behind the treasury ledger

    From this entry’s day the Gazette’s data job keeps Strategy’s filed totals level by itself, never ahead of Strategy’s row in the treasury ledger and with no entry of their own, under the rule on the method page. The totals through the 8-K filed 19 October were added by a person on this day.

    The data job keeps Strategy’s filed totals level, behind the treasury ledger: This entry’s own page →

  27. Pool block share

    One-week sample re-read; the leaders' share fell to 62.39 percent

    The top three labels, Foundry USA, AntPool and F2Pool, hold 667 of 1,069 blocks in the one-week window, 62.39 percent, against 64.12 percent on October 14. The one-month window is 62.98 percent and the three-month 60.62 percent. The previous snapshot and the endpoint receipts are preserved beside it.

    One-week sample re-read; the leaders' share fell to 62.39 percent: Pools →One-week sample re-read; the leaders' share fell to 62.39 percent: This entry’s own page →

    Filed by the data job; no person read it first →

  28. Company treasuries

    Strategy advanced to 848,517 BTC as of October 18

    Strategy's October 19 8-K reports 848,517 BTC as of October 18, with 267 bought from October 12 to October 18. The row had stood at 848,250 as of October 11, and the selected total moves from 1,044,571 to 1,044,838 BTC.

    Strategy advanced to 848,517 BTC as of October 18: Company treasuries →Strategy advanced to 848,517 BTC as of October 18: This entry’s own page →

    Filed by the data job; no person read it first →

  29. Claims floor

    Strategy's filing moved the floor to 11.2649 percent at block 972,262

    The corporate category rises by 267 BTC to 1,044,838, so the disclosed floor is 2,264,344 BTC, 11.2649 percent of the 20,100,821.875 BTC issued at block 972,262, against 11.2641 percent at block 971,944. The ETF and state rows are unchanged; the height moved to the chain tip so that no counted holding is dated after it.

    Strategy's filing moved the floor to 11.2649 percent at block 972,262: Claims floor →Strategy's filing moved the floor to 11.2649 percent at block 972,262: This entry’s own page →

    Filed by the data job; no person read it first →

  30. Method

    The data job files node software releases

    From this entry’s day the Gazette’s data job keeps Bitcoin Core’s security advisories level and files node software releases and Bitcoin Core end-of-life dates by itself, under the rule on the method page.

    The data job files node software releases: This entry’s own page →

  31. Method

    The data job keeps the wallet El Salvador discloses level, and files a credit of two bitcoin or more

    From this entry’s day the Gazette’s data job keeps El Salvador’s disclosed wallet level: it adds each block that moved the balance to the series on Holdings, with no entry in this log and no person reading the new rows first. It also files a fifth thing by itself: a block that credits two bitcoin or more, as an entry under the desk El Salvador’s wallet, with the job’s mark. A read that finds a debit of 0.01 BTC or more writes nothing and waits for a person, under the rule printed on the method page. On Holdings the wallet’s section gains a table of the credits of two bitcoin or more, to the satoshi. The wallet’s download gains one field, filed_by, for each block’s step: data-job or person where an entry names the block, and nothing for every other step. Its JSON file and its CSV file change, and so do their checksums. The claims floor’s row for El Salvador stays a person’s to move. The blocks added on this day, to block 971,928, were read by a person. The statement on the editorial page and on the method page now names the two series the job keeps level; the node counts were the first.

    The data job keeps the wallet El Salvador discloses level, and files a credit of two bitcoin or more: This entry’s own page →

  32. Company treasuries

    Strategy advanced to 848,250 BTC as of October 11

    Strategy's October 13 8-K reports 848,250 BTC as of October 11, with 250 bought from October 5 to October 11. The row had stood at 848,000 as of October 4, and the selected total moves from 1,044,321 to 1,044,571 BTC.

    Strategy advanced to 848,250 BTC as of October 11: Company treasuries →Strategy advanced to 848,250 BTC as of October 11: This entry’s own page →

    Filed by the data job; no person read it first →

  33. Claims floor

    Strategy's filing moved the floor to 11.2641 percent at block 971,944

    The corporate category rises by 250 BTC to 1,044,571, so the disclosed floor is 2,264,077 BTC, 11.2641 percent of the 20,099,828.125 BTC issued at block 971,944, against 11.2656 percent at block 970,370. The ETF and state rows are unchanged; the height moved to the chain tip so that no counted holding is dated after it.

    Strategy's filing moved the floor to 11.2641 percent at block 971,944: Claims floor →Strategy's filing moved the floor to 11.2641 percent at block 971,944: This entry’s own page →

    Filed by the data job; no person read it first →

  34. Method

    The data job keeps the node software counts level

    From this entry’s day the Gazette’s data job keeps the node software series level: it adds one row for each of KIT’s snapshot days, at most three a run, with no entry in this log and no person reading the new rows first. It files nothing for this series: counts move every day, and none is an event. A day the reader’s own checks refuse is not written and waits for a person, and no day is added until then, under the rule printed on the method page. The snapshot days from 1 October 2026 to 15 October 2026 were added by a person on this day; the snapshot of 16 October 2026 is not recorded, because 69 of the 2,700 peers it saw open in a day announced no readable software, over the rule’s 2 percent. The statement on the method and editorial pages now names the series the job keeps level.

    The data job keeps the node software counts level: This entry’s own page →

  35. Difficulty

    Difficulty rose 5.92 percent at block 971,712

    Difficulty rose 5.92 percent at block 971,712 on 16 October 2026, to 140,577,680,051,919.62 from 132,716,002,350,731.27. On the subsidy alone, 3.125 BTC a block at that height, one TH/s earns an expected 44.72 sats a day. The retarget's nBits, 17020093, follow by the consensus rule from period 481's first and last block times, and the block's hash was matched on a second operator.

    Difficulty rose 5.92 percent at block 971,712: Hashprice & difficulty →Difficulty rose 5.92 percent at block 971,712: This entry’s own page →

    Filed by the data job; no person read it first →

  36. Pool block share

    One-week sample re-read; the leaders' share rose to 64.12 percent

    The top three labels, Foundry USA, AntPool and F2Pool, hold 681 of 1,062 blocks in the one-week window, 64.12 percent, against 63.75 percent on October 7. The one-month window is 62.65 percent and the three-month 60.73 percent. The previous snapshot and the endpoint receipts are preserved beside it.

    One-week sample re-read; the leaders' share rose to 64.12 percent: Pools →One-week sample re-read; the leaders' share rose to 64.12 percent: This entry’s own page →

    Filed by the data job; no person read it first →

  37. Method

    The data job files each difficulty retarget

    From this entry’s day the Gazette’s data job files a fourth thing by itself: each difficulty retarget, once its block is six deep. Each is an entry in this log under the desk Difficulty, with the job’s mark. The job reads block headers alone, under the rule printed on the method page, and writes the period file only at a retarget. On Mining the mark stands under the difficulty of each period the job filed, and under the days since the all-time high when the job filed either of the two periods the count is read from: the one that set the high, or the newest. The chart on the difficulty claim’s page carries the mark under the same count, on the same days. The lines of both charts, the list of stretches on the claim’s page and the node check under Reproduce this page carry none. The difficulty download gains one field, filed_by, on each period’s row: data-job, person, or nothing where the log does not say. Its JSON file and its CSV file change, and so do their checksums. The retarget at block 969,696 was read and filed by a person, in the entry under this one.

    The data job files each difficulty retarget: This entry’s own page →

  38. Difficulty

    Difficulty fell 0.03 percent at block 969,696

    Difficulty fell 0.03 percent at block 969,696 on 3 October 2026, to 132,716,002,350,731.27 from 132,757,073,449,487.51. On the subsidy alone, 3.125 BTC a block at that height, one TH/s earns an expected 47.37 sats a day. The retarget's nBits, 17021ef0, follow by the consensus rule from period 480's first and last block times, and the block's hash was matched on a second operator.

    Difficulty fell 0.03 percent at block 969,696: Hashprice & difficulty →Difficulty fell 0.03 percent at block 969,696: This entry’s own page →

  39. Company treasuries

    Strategy advanced to 848,000 BTC as of October 4

    Strategy's October 5 8-K reports 848,000 BTC as of October 4, with 334 bought from October 1 to October 4. The row had stood at 847,666 as of September 27, and the selected total moves from 1,043,987 to 1,044,321 BTC.

    Strategy advanced to 848,000 BTC as of October 4: Company treasuries →Strategy advanced to 848,000 BTC as of October 4: This entry’s own page →

  40. Claims floor

    Strategy's filing moved the floor to 11.2656 percent at block 970,370

    The corporate category rises by 334 BTC to 1,044,321, so the disclosed floor is 2,263,827 BTC, 11.2656 percent of the 20,094,909.375 BTC issued at block 970,370, against 11.2659 percent at block 969,248. The ETF and state rows are unchanged; the height moved to the chain tip so that no counted holding is dated after it.

    Strategy's filing moved the floor to 11.2656 percent at block 970,370: Claims floor →Strategy's filing moved the floor to 11.2656 percent at block 970,370: This entry’s own page →

  41. Pool block share

    One-week sample re-read; the leaders' share rose to 63.75 percent

    The top three labels, Foundry USA, AntPool and F2Pool, hold 656 of 1,029 blocks in the one-week window, 63.75 percent, against 61.72 percent on September 30. The one-month window is 61.12 percent and the three-month 60.50 percent. The previous snapshot and the endpoint receipts are preserved beside it.

    One-week sample re-read; the leaders' share rose to 63.75 percent: Pools →One-week sample re-read; the leaders' share rose to 63.75 percent: This entry’s own page →

    Filed by the data job; no person read it first →

  42. Claims floor

    The floor counts fourteen US spot ETF trusts; it is 11.2659 percent at block 969,248

    The claims floor's spot ETF category now counts fourteen US spot bitcoin trusts, each at the bitcoin quantity its latest quarterly report on Form 10-Q states, all as of 30 June 2026: 1,211,728.47121778 BTC between them. It had counted one, the iShares Bitcoin Trust, at the 734,261 BTC the same report states, so the category rises by 477,467.47121778 BTC. The floor moves from 1,786,026.37428655 to 2,263,493.84550433 BTC, from 8.8895 to 11.2659 percent of the 20,091,403.125 BTC issued at block 969,248. The height, the eleven company rows and the state row are unchanged. This is a change of scope, not a correction: the earlier figure was right for the one fund it counted. The fourteen rows are the latest filed figures of the spot ETF dataset on Holdings, copied by a script of the desk's that reads no source of its own; the site's tests hold the two files to each other, and Reproduce this page on Holdings names the script. A trust's holdings move every trading day as shares are created and redeemed, so a filed figure can be above or below what the trust holds today. Two trusts on the list are not counted, because the rule that reads the reports cannot take a quantity from their filings: the Hashdex Bitcoin ETF and the 7RCC Spot Bitcoin and Carbon Credit Futures ETF. What they hold is unknown, not zero. The iShares Bitcoin Premium Income ETF is counted only for the 484 BTC on its own schedule: the shares of the iShares Bitcoin Trust it also holds are a claim on bitcoin already in that trust's row. A claim on a claim is not counted again: a fund's shares are never counted as bitcoin in a company's row or in another fund's. The rows are dated apart, though, 30 June for the trusts and as late as 27 September for a company, so bitcoin one holder sold after its disclosure and another bought before its own can be in both rows; the method now says so. Methodology 2.3.0.

    The floor counts fourteen US spot ETF trusts; it is 11.2659 percent at block 969,248: Claims floor →The floor counts fourteen US spot ETF trusts; it is 11.2659 percent at block 969,248: This entry’s own page →

  43. Spot ETF trusts

    Spot ETF rows print whole bitcoin, cut, never rounded up

    In the list of US spot bitcoin ETF trusts on Holdings, each row's figure is now cut to whole bitcoin, never rounded up, and so are the figures under each trust's line by quarter end. One row had printed a decimal while the others printed whole bitcoin. The total still sums the exact filed quantities, so the rows as printed add to a little less than it, and the section now says so. The exact quantities stay in each trust's table and in the download. No quantity changed.

    Spot ETF rows print whole bitcoin, cut, never rounded up: Claims floor →Spot ETF rows print whole bitcoin, cut, never rounded up: This entry’s own page →

  44. Fee estimates and the queue

    Fee estimates now print below 1 sat/vB; economy read 1, not 0.20

    The desk read mempool.space's whole-number recommendation, which pads every rate up to a whole sat/vB, so estimates under 1 printed as 1 and the fee ladder drew equal bars. It now reads the precise estimator and prints two places under 10 sat/vB. Read together at 23:07 UTC on 30 September, the whole-number endpoint gave 1 for every rate; the precise estimator gave next block 1.02, half an hour 0.67, an hour 0.35, economy 0.20 and minimum 0.10 sat/vB, so economy 1 → 0.20. The ticker's next-block fee, the Settlement Bench and the mining desk's fee readings moved with it, and the pressure reading now uses the precise next-block rate.

    Fee estimates now print below 1 sat/vB; economy read 1, not 0.20: Fees & blocks →Fee estimates now print below 1 sat/vB; economy read 1, not 0.20: This entry’s own page →

  45. Claims floor

    IBIT is counted from its 10-Q; the floor is 8.8895 percent at block 969,248

    The iShares Bitcoin Trust row now carries the 734,261 BTC its quarterly report on Form 10-Q states as of 30 June, with the filing on EDGAR as its receipt. It had carried 782,623.42 BTC as of 16 September from the sponsor's daily holdings file, whose link no longer serves the figure the row counted. The ETF category falls by 48,362.42 BTC, and the floor moves from 1,834,388 to 1,786,026 BTC, from 9.1302 to 8.8895 percent of the 20,091,403.125 BTC issued at block 969,248. The height and the other rows are unchanged, and the summary was recomputed through the refresh job's own arithmetic. The method now says plainly what the floor sums: each holder's latest disclosure, dated 30 June to 27 September, against issued supply at the pinned block, so a holder that sold since its disclosure could hold less. Methodology 2.2.0.

    IBIT is counted from its 10-Q; the floor is 8.8895 percent at block 969,248: Claims floor →IBIT is counted from its 10-Q; the floor is 8.8895 percent at block 969,248: This entry’s own page →

  46. Method

    Hashprice is now printed in sats per TH/s per day, at difficulty

    The mining desk's hashprice is now the reward per block in sats × 86,400 × 10¹² ÷ (difficulty × 2³²): the sats one TH/s expects in a day at the current difficulty, taking the tip height's subsidy plus the average fees of the last 144 blocks as the reward. It needs no hashrate estimate and no price, and the formula is printed beside the figure. The three dollar models it replaces multiplied by a fetched price, and two of them divided by an estimated hashrate. For block 968,255, a reward of 313,369,555 sats at difficulty 132,757,073,449,487.52 gives 47.48. Mining method sg-mining.v3.

    Hashprice is now printed in sats per TH/s per day, at difficulty: Hashprice & difficulty →Hashprice is now printed in sats per TH/s per day, at difficulty: This entry’s own page →

  47. Method

    The Data Desk no longer uses a fetched price

    No Data Desk figure is multiplied by a market price any more, and the desk's loaders no longer read a price endpoint. The mining desk's BTC price and dollars-to-sats tiles are gone, and the Miner's Bench now prints expected sats a day, kWh a day and a break-even power price in sats per kWh, against which a reader can set their own tariff; nothing is converted. Bench links shared before today keep their machine and network inputs and drop the dollar ones. The ticker's 1 BTC and 1 sat remain the site's only price, read through a loader of their own.

    The Data Desk no longer uses a fetched price: Hashprice & difficulty →The Data Desk no longer uses a fetched price: This entry’s own page →

  48. Pool block share

    One-week sample re-read; the leaders' share rose to 61.72 percent

    The top three labels hold 632 of 1,024 blocks in the one-week window, 61.72 percent, against 60.04 percent on 18 September and the highest reading the desk has recorded. The three built one block more than on 18 September in a week of 27 fewer blocks; within them AntPool rose to 223 and F2Pool to 159 while Foundry USA fell to 250. The one-month window is 59.80 percent and the three-month 59.90 percent; fifteen labels are named in the week, and six blocks carry no label. The previous snapshot and the endpoint receipts are preserved beside it.

    One-week sample re-read; the leaders' share rose to 61.72 percent: Pools →One-week sample re-read; the leaders' share rose to 61.72 percent: This entry’s own page →

  49. Method

    Pool snapshots are built by script and dated by the source's clock

    The pool block-share snapshot is now built from the three endpoint responses and checked against the page's own validator before anything is written; a failed or partial read writes nothing. Its observation time is the source's HTTP Date header rather than the moment the receipt was assembled, and the date in its method text is generated from that observation. The 18 September file's method text named 12 September. Methodology 1.1.0; block counts and share arithmetic are unchanged.

    Pool snapshots are built by script and dated by the source's clock: This entry’s own page →

  50. Company treasuries

    Strategy advanced to 847,666 BTC as of September 27

    Strategy's 8-K of 28 September reports 847,666 BTC as of 27 September, with 1,665 bought that week; its 8-K of 21 September reported 950 bought and 846,000 held as of 20 September. The row had stood at 845,050 as of 30 August, and the selected total moves from 1,041,371 to 1,043,987 BTC. The filings state whole bitcoin and do not reconcile to the unit: the two purchases sum to 2,615 BTC while the filed aggregates differ by 2,616, and the ledger records the difference between the aggregates.

    Strategy advanced to 847,666 BTC as of September 27: Company treasuries →Strategy advanced to 847,666 BTC as of September 27: This entry’s own page →

  51. Claims floor

    Strategy's filing moved the floor to 9.1302 percent at block 969,248

    The corporate category rises by the same 2,616 BTC to 1,043,987, so the disclosed floor is 1,834,388 BTC, 9.1302 percent of the 20,091,403.125 BTC issued at block 969,248, against 9.1196 percent at block 967,564 on 18 September. The observation height moved to a block mined on 30 September, after Strategy's 27 September position, so that no counted holding is dated after the block its share is taken against. The ETF and state rows are unchanged, and the summary was recomputed through the loader's own arithmetic.

    Strategy's filing moved the floor to 9.1302 percent at block 969,248: Claims floor →Strategy's filing moved the floor to 9.1302 percent at block 969,248: This entry’s own page →

  52. Method

    The custody floor is cut, never rounded up

    The floor's share of issued bitcoin is now cut to four places rather than rounded, so it can never print above its evidence; the 18 September reading of 9.1196 percent was 9.11959 rounded up. The unclassified remainder is 100 minus the floor, and the homepage chart cuts each named part the same way. The pinned block is now required to follow the newest holding the floor counts. Methodology 2.1.0; no holding changed.

    The custody floor is cut, never rounded up: This entry’s own page →

  53. Pool block share

    One-week sample re-read; the leaders' share rose to 60.04 percent

    The top three labels hold 631 of 1,051 blocks in the one-week window, 60.04 percent, against 57.55 percent on 12 September and the highest reading the desk has recorded. Foundry USA built 275, AntPool 202 and F2Pool 154. The one-month window is 58.50 percent and the three-month 59.24 percent, so the move sits in the recent sample; sixteen labels are named in the week, and 13 blocks carry no label. The previous snapshot and the endpoint receipts are preserved beside it.

    One-week sample re-read; the leaders' share rose to 60.04 percent: Pools →One-week sample re-read; the leaders' share rose to 60.04 percent: This entry’s own page →

    Corrected 30 Sep 2026 · This entry first read "seventeen labels are named in the week". The week lists seventeen rows, but one of them is the Unknown row, 13 blocks that carry no label; sixteen labels are named. The snapshot was always right.

  54. Claims floor

    ETF and state holdings advanced; the floor is 9.1196 percent at block 967,564

    The iShares fund file moved to 782,623.42 BTC as of 16 September, about 3,894 higher than the 2 September reading, and the El Salvador wallet endpoint to 7,778.37 BTC. Strategy's 8-Ks of 8 and 14 September report 845,050 BTC as of 7 September and 13 September, and its 8-K of 1 September states no holding, so the corporate row is unchanged. The observation height moved to block 967,564 and the summary was recomputed through the loader's own arithmetic.

    ETF and state holdings advanced; the floor is 9.1196 percent at block 967,564: Claims floor →ETF and state holdings advanced; the floor is 9.1196 percent at block 967,564: This entry’s own page →

    Corrected 30 Sep 2026 · This entry first said Strategy's three September 8-Ks each report 845,050 BTC, and then that the 8 and 14 September filings each report it through 13 September. Only those two filings state that figure, the 8 September filing as of 7 September and the 14 September filing as of 13 September; the 8-K of 1 September is a dividend filing with no holdings statement. The corporate row was always right.

  55. Pool block share

    One-week sample re-read; the leaders' share fell to 57.55 percent

    The top three labels hold 610 of 1,060 blocks in the one-week window, 57.55 percent, against 59.88 percent on 3 September. The one-month window is 58.72 percent and the three-month 59.00 percent. Twenty-six labels are now named rather than folded into a remainder, and the per-block receipts are published beside the snapshot.

    One-week sample re-read; the leaders' share fell to 57.55 percent: Pools →One-week sample re-read; the leaders' share fell to 57.55 percent: This entry’s own page →

  56. Pool block share

    All three windows re-read from the same capture

    The top three labels hold 59.88 percent of the one-week window, against 57.59 percent on 29 August. The one-month and three-month windows barely moved, so the change sits in the recent sample rather than the trend.

    All three windows re-read from the same capture: Pools →All three windows re-read from the same capture: This entry’s own page →

    Corrected 14 Sep 2026 · This entry first read 59.86 percent. The preserved receipt for that capture is 609 of 1,017 blocks, which is 59.88 percent. The snapshot and the page were always right; the figure was mistyped here.

  57. Claims floor

    ETF and state holdings advanced to their newest disclosures

    The iShares fund file moved to 778,729.91 BTC as of 2 September, about 7,089 higher than the 25 August reading, and the El Salvador wallet endpoint to 7,763.37 BTC. The observation height moved to block 965,362.

    ETF and state holdings advanced to their newest disclosures: Claims floor →ETF and state holdings advanced to their newest disclosures: This entry’s own page →

  58. Company treasuries

    Cango advanced from a first-quarter to a second-quarter filing

    The company disclosed 1,056 BTC at 30 June against 1,026 at 31 March, with 656 BTC mined in the quarter. Its two September filings concern an NYSE listing matter and carry no bitcoin figures.

    Cango advanced from a first-quarter to a second-quarter filing: Company treasuries →Cango advanced from a first-quarter to a second-quarter filing: This entry’s own page →

  59. Company treasuries

    Strategy and Strive observations advanced to current filings

    The ledger now separates bitcoin acquired from the equity issued to fund it, and retains the share-count receipt beside the holding.

    Strategy and Strive observations advanced to current filings: Company treasuries →Strategy and Strive observations advanced to current filings: This entry’s own page →

  60. Pool block share

    One-week, one-month and three-month windows synchronized

    Pool labels remain a measure of block-building coordination, not miner ownership or control of hashrate.

    One-week, one-month and three-month windows synchronized: Pools →One-week, one-month and three-month windows synchronized: This entry’s own page →

Site changes (16)
  1. KIT’s files counted by services number, network and version range
  2. Three lines on the Data Desk reworded
  3. The record gains a page for each week, a feed of weeks and a front-page line
  4. Rows the data job filed carry its mark, and the downloads say who filed a figure
  5. The change log gains record pages, share cards, a feed and a front-page line
  6. Mining gains a Public miners page: bitcoin mined, sold and held, as listed miners filed it
  7. Network gains a Protocol page: every BIP by the status the BIP repository gives it
  8. Bitcoin in fourteen US spot ETF trusts, quarter by quarter, from their own filings
  9. Strategy, filing by filing: every bitcoin total the company has stated in an 8-K, 10-Q or 10-K
  10. The saved datasets can be downloaded as JSON and CSV, under CC BY 4.0
  11. A data dictionary: every field of the downloads, and what an empty value means
  12. Each Data Desk tab ends with Reproduce this page
  13. The method names the chain the figures describe, by block 961,632’s hash
  14. Difficulty since 2009, and Nodes & releases
  15. The desk is four tabs, and every earlier address redirects
  16. Observation-level provenance added