Skip to content
Satoshi Gazette
Data DeskCC BY 4.0

Downloads

The desk’s saved datasets as files, at addresses that do not change. Each carries its sources, its own date and a line to cite.

Licence

Free to reuse, with credit

The Gazette licenses its own compilation, selection and annotations in these files under CC BY 4.0: anyone may copy, adapt and republish them, for any purpose, with credit to the Satoshi Gazette Data Desk, a link to the licence and a note of any change. Each dataset below carries a line to cite. The licence covers the Gazette’s part of these files, not the Gazette’s articles, which stay under copyright.

Creative Commons Attribution 4.0 International, the licence’s deed ↗

Upstream records keep their own terms, and each dataset prints them as the register reads them: KIT’s network snapshots are CC BY 4.0 and ask for their own attribution, SEC filings are public domain, and mempool.space grants no data licence and forbids no reuse.

Nothing in a download is a market price. No file has a price field, and the desk fetched no price. Where a company’s filing states what a purchase cost or how it was funded, the treasury ledger’s funding and limitation notes repeat the filing’s own dollar amounts; no other field in any file names a currency.

Files

Every dataset, and its files

Ten of the register’s 13 datasets have a file today. JSON is the file as the site reads it; CSV is offered where a dataset is one table. A dataset with no file says why.

The data dictionary: what every field in these files holds, and what an empty value means →

  • Fee estimates and the queue

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

    No file

    No download: its values are read when a page is served and are not saved, so there is no file to offer.

  • Node software on reachable nodes

    Every peer in KIT’s network snapshot, by the software it announces.

    Latest record 30 Sep 2026, 12:13 UTCMethod 1.1.0Dated snapshot · KIT snapshot of 30 Sep 2026

    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 desk reduces per-peer records to daily counts and republishes no per-peer data.
    Cite this

    Satoshi Gazette Data Desk, Node software on reachable nodes (sg-node-software), version 1.1.0, data through 30 Sep 2026. https://satoshigazette.org/data/downloads/sg-node-software.json

    Columns, notes and checksums (43 columns) for Node software on reachable nodes

    Derived from KIT’s snapshots, licensed CC BY 4.0, which asks for its own attribution: Neudecker, Till; Grundmann, Matthias; Hartenstein, Hannes. Bitcoin Peer-To-Peer Network Monitoring. Zenodo. doi:10.5281/zenodo.14627525.

    JSON sha256 101b3a0812424abf62b67c4ea29ab56bc7a60f6355378a1fe67b18c7c3efc53b

    CSV sha256 5e3edc8bc92eea4031e4390d2aa514f65cd3b66c4bde3adaa6ea211dfcbc93b2

    One row per KIT snapshot day recorded. Core peers by release line vary by day and are in the JSON only. UTF-8 with one header row. An empty cell is never zero; the data dictionary says what it means in each column. In a spreadsheet, import the columns as text, so that no figure is reformatted or shortened.

    day
    The snapshot’s UTC date.
    snapshot
    KIT’s name for the snapshot file, its time in UTC.
    snapshot_at
    The same time as an ISO 8601 timestamp.
    clock_offset_minutes
    Minutes KIT’s lastConnect clock ran ahead of UTC, derived from the file.
    lifecycle_as_of
    The day of the Core lifecycle table the row was classified with.
    sha256
    sha256 of KIT’s snapshot file as served.
    possible_cap
    true when the snapshot held exactly 9,000 peers, which may be a cap on KIT’s file.
    connected_nodes
    All connected peers: peers counted.
    connected_ipv4
    All connected peers: reached over IPv4.
    connected_ipv6
    All connected peers: reached over IPv6.
    connected_ip_unknown
    All connected peers: IP version not recorded.
    connected_core
    All connected peers: user agent sorted as core by the rules in the JSON.
    connected_knots
    All connected peers: user agent sorted as knots by the rules in the JSON.
    connected_btcd
    All connected peers: user agent sorted as btcd by the rules in the JSON.
    connected_other
    All connected peers: user agent sorted as other by the rules in the JSON.
    connected_unknown
    All connected peers: user agent sorted as unknown by the rules in the JSON.
    connected_core_maintained
    All connected peers: Core peers on a release line that was maintained on the snapshot day.
    connected_core_end_of_life
    All connected peers: Core peers on a release line that was end of life on the snapshot day.
    connected_core_unreleased
    All connected peers: Core peers on a release line not yet released on the snapshot day, or on an x.99 development build.
    connected_core_not_listed
    All connected peers: Core peers on a release line the life cycle table does not carry, or announcing a version that does not parse.
    opened_24h_nodes
    Peers whose connection began within 24 hours: peers counted.
    opened_24h_ipv4
    Peers whose connection began within 24 hours: reached over IPv4.
    opened_24h_ipv6
    Peers whose connection began within 24 hours: reached over IPv6.
    opened_24h_ip_unknown
    Peers whose connection began within 24 hours: IP version not recorded.
    opened_24h_core
    Peers whose connection began within 24 hours: user agent sorted as core by the rules in the JSON.
    opened_24h_knots
    Peers whose connection began within 24 hours: user agent sorted as knots by the rules in the JSON.
    opened_24h_btcd
    Peers whose connection began within 24 hours: user agent sorted as btcd by the rules in the JSON.
    opened_24h_other
    Peers whose connection began within 24 hours: user agent sorted as other by the rules in the JSON.
    opened_24h_unknown
    Peers whose connection began within 24 hours: user agent sorted as unknown by the rules in the JSON.
    opened_24h_core_maintained
    Peers whose connection began within 24 hours: Core peers on a release line that was maintained on the snapshot day.
    opened_24h_core_end_of_life
    Peers whose connection began within 24 hours: Core peers on a release line that was end of life on the snapshot day.
    opened_24h_core_unreleased
    Peers whose connection began within 24 hours: Core peers on a release line not yet released on the snapshot day, or on an x.99 development build.
    opened_24h_core_not_listed
    Peers whose connection began within 24 hours: Core peers on a release line the life cycle table does not carry, or announcing a version that does not parse.
    flags_connected_blake2b_only
    All connected peers announcing the BLAKE2b flag only; empty when the split was not counted.
    flags_connected_reduced_data_only
    All connected peers announcing the reduced-data flag only; empty when the split was not counted.
    flags_connected_both
    All connected peers announcing both flags; empty when the split was not counted.
    flags_connected_neither
    All connected peers announcing neither flag; empty when the split was not counted.
    flags_connected_unknown
    All connected peers whose services number was missing or unreadable: unknown, never neither; empty when the split was not counted.
    flags_knots_blake2b_only
    Knots peers announcing the BLAKE2b flag only; empty when the split was not counted.
    flags_knots_reduced_data_only
    Knots peers announcing the reduced-data flag only; empty when the split was not counted.
    flags_knots_both
    Knots peers announcing both flags; empty when the split was not counted.
    flags_knots_neither
    Knots peers announcing neither flag; empty when the split was not counted.
    flags_knots_unknown
    Knots peers whose services number was missing or unreadable: unknown, never neither; empty when the split was not counted.

  • Bitcoin Core release lifecycle

    bitcoincore.org’s support windows and advisories, with Knots releases beside them.

    Latest record 1 Oct 2026, 09:44 UTCMethod 1.0.0Dated snapshot · read 1 Oct 2026

    JSON only: the file holds three lists (release lines, security advisories and Knots releases), not one table.

    Source terms
    bitcoincore.org is MIT-licensed, every file unless it says otherwise. The Knots releases are read from GitHub’s public Atom feed for the MIT-licensed Knots repository; only tags, titles and dates are kept.
    Cite this

    Satoshi Gazette Data Desk, Bitcoin Core release lifecycle (sg-core-lifecycle), version 1.0.0, data through 1 Oct 2026. https://satoshigazette.org/data/downloads/sg-core-lifecycle.json

    Notes and checksums for Bitcoin Core release lifecycle

    JSON sha256 e8f2aa76c821012288f89bebcff0e64aca64c0abec680506c3624dcf42388bd4

  • Bitcoin Improvement Proposals by status

    Every BIP’s status in the BIP repository’s own words, and the changes the desk has seen.

    Latest record 3 Oct 2026, 14:43 UTCMethod 1.0.0Dated snapshot · bitcoin/bips at commit 927b6de · read 3 Oct 2026

    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 desk 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.
    Cite this

    Satoshi Gazette Data Desk, Bitcoin Improvement Proposals by status (sg-bip-status), version 1.0.0, data through 3 Oct 2026. https://satoshigazette.org/data/downloads/sg-bip-status.json

    Columns, notes and checksums (15 columns) for Bitcoin Improvement Proposals by status

    The JSON also holds every status change the desk has recorded and the numbers the index lists without a document. A status is the BIP repository’s label for a document: not an endorsement, and not an activation.

    JSON sha256 e8901995d2ad65a8958b6576ca267b379d3bcebd4622c83fec7f9c7a7a19505c

    CSV sha256 bd9daf28952b31dedc52a1e0ef0363e8ce3fbd88097766084d538301a1ede892

    One row per BIP the repository’s index links, by number. The recorded status changes and the numbers allocated without a document are in the JSON. UTF-8 with one header row. An empty cell is never zero; the data dictionary says what it means in each column. In a spreadsheet, import the columns as text, so that no figure is reformatted or shortened.

    number
    The BIP’s number.
    file
    The BIP’s own file in the repository.
    title
    The Title header of the BIP’s preamble.
    layer
    The Layer header; empty when the preamble names none.
    type
    The Type header: Specification, Informational or Process.
    status
    The Status header: Draft, Complete, Deployed or Closed. The repository’s label, not an endorsement and not an activation.
    authors
    Lines in the Authors header; one line can name more than one person.
    assigned
    The Assigned header: the date the number was assigned.
    replaces
    BIP numbers in the Replaces header, separated by spaces.
    proposed_replacement
    BIP numbers in the Proposed-Replacement header, separated by spaces.
    held
    true when the last read could not read the row; its fields are then what the desk last recorded.
    held_since
    The day the hold began; empty when the row is not held.
    held_reason
    Why the row is held; empty when it is not.
    commit
    The repository commit the rows were read at.
    url
    The BIP’s file on GitHub at that commit.

  • Hashprice at difficulty

    The desk’s arithmetic on three mempool.space readings, live.

    No file

    No download: its values are read when a page is served and are not saved, so there is no file to offer.

  • Difficulty by retarget period

    Every retarget period since genesis, its difficulty exact from the block header.

    Latest record 1 Oct 2026, 08:55 UTCMethod 1.0.0Dated snapshot · through block 969,431 · read 1 Oct 2026

    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 desk could find; its software is MIT-licensed.
    Cite this

    Satoshi Gazette Data Desk, Difficulty by retarget period (sg-difficulty-ledger), version 1.0.0, data through 1 Oct 2026. https://satoshigazette.org/data/downloads/sg-difficulty-ledger.json

    Columns, notes and checksums (17 columns) for Difficulty by retarget period

    This file carries the difficulty dataset, sg-difficulty-ledger, only. The reward ledger, sg-block-ledger, is offered as its own file once it reaches the chain tip, so here ledger_through_height, ledger_tip_hash and every period’s ledger are null and coinbase_proved is empty: left out of this file, not zero and not unread. header_check states the retarget-window check the difficulty pass gives every period. For a period the reward ledger has read, every header was checked as well; this file states the weaker check, never a stronger one.

    In a spreadsheet, import every column of the CSV as text. Opened by double-click, a spreadsheet reads an nBits value such as 17042e95 as a number, reads the fraction 1/1 as a date and keeps only 15 digits of a longer figure. The JSON is unaffected.

    JSON sha256 343876495bc2e52bf6e8098a6eb98e92aa4d29a0c270fa758124509b3231e2f2

    CSV sha256 980e5ccc0667080151d9154c2e69a9a9695f842016a87b9529460d1952b7e718

    One row per 2,016-block retarget period since the genesis block; the latest period is still open. UTF-8 with one header row. An empty cell is never zero; the data dictionary says what it means in each column. In a spreadsheet, import the columns as text, so that no figure is reformatted or shortened.

    epoch
    The retarget period, counted from 0.
    start_height
    Height of the period’s first block, the retarget block.
    end_height
    Height of the last block read in the period.
    blocks
    Blocks in the period so far; 2,016 when complete.
    complete
    true when the period holds all 2,016 blocks.
    first_block_time
    Header time of the first block, UTC.
    last_block_time
    Header time of the last block read, UTC.
    retarget_hash
    Hash of the first block.
    last_block_hash
    Hash of the last block read.
    bits
    nBits of the first block’s header, eight hex digits.
    difficulty_fraction
    Exact difficulty as a reduced fraction: 0xffff × 2^208 over the target.
    difficulty_decimal
    The fraction cut, never rounded, to 8 decimals.
    difficulty_core_float
    Bitcoin Core’s double-precision difficulty, written out exactly.
    ratio_to_previous
    The previous period’s target over this one, cut to 10 decimals; empty at genesis.
    subsidy_sats
    Subsidy of the period’s blocks, from the halving schedule, in sats.
    second_operator_hash
    true when the first block’s hash was matched on Blockstream’s Esplora.
    retarget_rule
    true when the nBits equals what the consensus rule requires from the period before; empty at genesis.

  • Block rewards, fees and pool labels

    Reward, fees and pool labels per period, blocks 628,992 to 832,607 so far.

    Not offered yetDated snapshot · through block 832,607 · read 1 Oct 2026

    Not yet complete: the ledger runs from block 628,992 through block 832,607, and the period file that holds it runs through block 969,431, read on 1 Oct 2026. Its files will be offered once the ledger reaches that block.

  • Blocks by pool label

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

    Latest record 30 Sep 2026, 02:11 UTCMethod 1.1.0

    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.
    Cite this

    Satoshi Gazette Data Desk, Blocks by pool label (sg-pool-blocks), version 1.1.0, data through 30 Sep 2026. https://satoshigazette.org/data/downloads/sg-pool-blocks.json

    Columns, notes and checksums (7 columns) for Blocks by pool label

    JSON sha256 54474e39eed385f5b205f86082420a44aae07ae46ae5694a42e9645e4f63ca19

    CSV sha256 bf24e2f1f7a640041244dc2d7f67a46047644684843566953b6a1f51c71c929b

    One row per pool label per window, in the source’s rank order. A label is a labelling rule, not ownership. UTF-8 with one header row. An empty cell is never zero; the data dictionary says what it means in each column. In a spreadsheet, import the columns as text, so that no figure is reformatted or shortened.

    observed_at
    When mempool.space served the three windows, UTC.
    window_key
    1w, 1m or 3m.
    window_label
    The window in words.
    observed_blocks
    Blocks in the window.
    rank
    The label’s place in the window by blocks, counted from 1.
    label
    mempool.space’s pool label; Unknown is its row for blocks its rules could not attribute.
    blocks
    Blocks carrying the label in the window.

  • Selected corporate treasuries

    One filing per company; Strategy’s row is checked every day.

    Latest record 27 Sep 2026Method v2

    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.
    Cite this

    Satoshi Gazette Data Desk, Selected corporate treasuries (sg-treasury-ledger), version 2, data through 27 Sep 2026. https://satoshigazette.org/data/downloads/sg-treasury-ledger.json

    Columns, notes and checksums (25 columns) for Selected corporate treasuries

    No field is a price, and the desk fetched none. Where a company’s filing states what a purchase cost or how it was funded, capital.funding_path and limitation repeat the filing’s own amounts, in the currency it reports; in the CSV those are the columns capital_funding_path and limitation.

    JSON sha256 402b517414cddc2c6cfe0a85e71ef5e8187dad4d188bd984d14185a5239abc32

    CSV sha256 8a8f06215eaff2e2ecb3f15b6cfc2f228d70b71d29b73f0061cbafe9fdd1ded9

    One row per company, each from one filing or disclosure, largest holding first. UTF-8 with one header row. An empty cell is never zero; the data dictionary says what it means in each column. In a spreadsheet, import the columns as text, so that no figure is reformatted or shortened.

    name
    The company’s name.
    entity_type
    public_company or private_company.
    ticker
    Its ticker; empty when it has none.
    exchange
    Where the ticker trades; empty when it has none.
    jurisdiction
    Where the company is incorporated.
    btc_amount
    Bitcoin the filing states, an exact decimal in BTC.
    as_of_date
    The date the filing states the holding for.
    evidence_type
    regulatory_filing, audited_report or company_disclosure.
    source_url
    Address of the filing or disclosure the row rests on.
    source_title
    Title of that filing or disclosure.
    source_locator
    Where in it the holding is stated.
    source_published_on
    The day it was published.
    confidence
    The desk’s confidence in the row: high, medium or low.
    limitation
    What the row does not establish.
    change_previous_btc
    The holding at the start of the change period; empty when no change is recorded.
    change_btc_delta
    The change over the period in BTC; negative for a reduction.
    change_period_start
    First day of the change period.
    change_period_end
    Last day of the change period.
    capital_funding_path
    How the filing says the bitcoin was funded, with the filing’s own amounts; empty when not recorded.
    capital_basic_share_change
    The change in basic shares the filing reports.
    capital_diluted_share_change
    The change in diluted shares the filing reports.
    capital_btc_per_share_change
    The change in bitcoin per share, where the filing supports one.
    control_restricted_btc
    Bitcoin the filing reports as restricted; empty when it states none.
    control_loaned_btc
    Bitcoin the filing reports as loaned; empty when it states none.
    control_note
    What the filing establishes about custody and control.

  • Strategy’s filed bitcoin totals

    Every bitcoin total Strategy has stated in an 8-K, 10-Q or 10-K since 2020, one row each.

    Latest record 27 Sep 2026Method 1.0.0Dated snapshot · filings through 1 Oct 2026 · read 3 Oct 2026

    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.
    Cite this

    Satoshi Gazette Data Desk, Strategy’s filed bitcoin totals (sg-strategy-filings), version 1.0.0, data through 27 Sep 2026. https://satoshigazette.org/data/downloads/sg-strategy-filings.json

    Columns, notes and checksums (19 columns) for Strategy’s filed bitcoin totals

    Filed totals, not wallet balances: each row is a number the company stated to the SEC, with the date the filing gives it. Every row carries the address of its own filing; a restated date keeps both rows, and a step its filing’s reported purchases do not match is flagged, never corrected.

    JSON sha256 9058a4221051da4b180728c8fb31e4295072b195a8a2d8433a58a35b04c82c1f

    CSV sha256 98bce3af9bd001d8efb4e4eb11636b83526ee6ef9800b3046b68992e037be303

    One row per total a filing states. The log of every filing read, and the filings listed without a total, are in the JSON. UTF-8 with one header row. An empty cell is never zero; the data dictionary says what it means in each column. In a spreadsheet, import the columns as text, so that no figure is reformatted or shortened.

    as_of_date
    The date the filing states the total for.
    btc_amount
    Bitcoin the filing states, an exact decimal in BTC, as filed.
    approximate
    true when the filing says approximately.
    form
    The SEC form: 8-K, 10-Q, 10-K or an amendment.
    accession
    The filing’s SEC accession number.
    filed_on
    The day the filing was made.
    url
    Address of the document the statement is in, on sec.gov.
    locator
    Where in that document the total is stated.
    wording_class
    Which of the wordings listed in the JSON the total was read from.
    restates
    Accession of the filing that first stated a total for this date; empty for the row that draws the step.
    reported_period_start
    First day of the period the filing reports purchases or sales for; empty when it gives none.
    reported_period_end
    Last day of that period.
    reported_acquired_btc
    Bitcoin the filing reports bought in the period; 0 when it reports none bought, empty when it reports no purchases.
    reported_sold_btc
    Bitcoin the filing reports sold in the period; 0 when it reports none sold, empty when it reports no sales.
    continuity_status
    matches or differs: the step against what the filing reports; empty when it is not checked.
    continuity_baseline_as_of_date
    The date of the filed total the step is measured from.
    continuity_baseline_accession
    The filing that stated that total.
    continuity_change_btc
    This total less the baseline, in BTC; negative for a decrease.
    continuity_reported_net_btc
    Purchases less sales as the filing reports them, in BTC.

  • Bitcoin held through disclosed claims

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

    Latest record 30 Sep 2026Method 2.2.0

    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.
    Cite this

    Satoshi Gazette Data Desk, Bitcoin held through disclosed claims (sg-claims-floor), version 2.2.0, data through 30 Sep 2026. https://satoshigazette.org/data/downloads/sg-claims-floor.json

    Columns, notes and checksums (11 columns) for Bitcoin held through disclosed claims

    JSON sha256 f2fab9b98394f2bad8acc067e9a99c01f4fc294ca3f8a780b4535ef098a3c123

    CSV sha256 a5ea2d9ee43c23323eb103ad6ec49cb9ede416906ba0cf83109d77313751760d

    One row per holder’s latest disclosure. The pinned block, issued supply and the floor are in the JSON. UTF-8 with one header row. An empty cell is never zero; the data dictionary says what it means in each column. In a spreadsheet, import the columns as text, so that no figure is reformatted or shortened.

    category_key
    spot_etf, public_company_treasury or government.
    category_label
    The category in words.
    category_status
    compiled, or not_yet_compiled for a category with no rows yet.
    entity_key
    A stable key for the holder; empty on the one row of a category not yet compiled.
    entity_name
    The holder’s name.
    btc_amount
    Bitcoin the disclosure states, an exact decimal in BTC.
    as_of_date
    The date the disclosure states the holding for.
    evidence_kind
    regulatory_filing, audited_report, company_disclosure or official_disclosure.
    evidence_title
    Title of the record the row rests on.
    evidence_url
    Address of that record.
    evidence_locator
    Where in it the holding is stated.

  • Bitcoin in US spot ETF trusts

    Bitcoin at each quarter end in 14 of the 16 trusts on the list, from their 10-Q and 10-K.

    Latest record 30 Jun 2026Method 1.0.0Dated snapshot · quarter ends through 30 Jun 2026 · read 3 Oct 2026

    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.
    Cite this

    Satoshi Gazette Data Desk, Bitcoin in US spot ETF trusts (sg-etf-trusts), version 1.0.0, data through 30 Jun 2026. https://satoshigazette.org/data/downloads/sg-etf-trusts.json

    Columns, notes and checksums (11 columns) for Bitcoin in US spot ETF trusts

    Filed quarter-end quantities, not today’s holdings. A quarter a trust has not reported has no row. A restated figure keeps both rows, the later one naming the accession it restates. Trusts listed as not read have no rows: unknown, not zero. Every row carries the address of its own report.

    JSON sha256 1086fc3605830bd40fe84c2d222d4a0e14e6276a080d1178ba6eb467ac3b55a1

    CSV sha256 1e19453cfba65c7be766ee37da70a35d2925e7b5b4bfb8b877d84376ea9cd7e7

    One row per filed quantity: a trust, a quarter end and the report that states it. The list of trusts, with those not read, is in the JSON. UTF-8 with one header row. An empty cell is never zero; the data dictionary says what it means in each column. In a spreadsheet, import the columns as text, so that no figure is reformatted or shortened.

    trust
    The trust’s name as the list gives it.
    ticker
    Its ticker.
    cik
    The registrant’s CIK on EDGAR.
    period_end
    The quarter end the quantity is stated for.
    btc_amount
    Bitcoin held, exactly as the report prints it, an exact decimal in BTC.
    form
    10-Q, 10-K, 10-Q/A or 10-K/A.
    accession
    The report’s EDGAR accession number.
    filed_on
    The day the report was filed.
    document_url
    Address of the report’s primary document.
    locator
    Where in it the quantity is stated, and how it is dated.
    restates
    The accession of the row this one restates; empty for a figure as first filed.

  • El Salvador’s disclosed wallet

    The 20 addresses El Salvador discloses, re-summed on a second operator’s index.

    Latest record 1 Oct 2026, 09:32 UTCMethod 1.0.0Dated snapshot · at block 969,436 · read 1 Oct 2026

    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 desk could find; its software is MIT-licensed.
    Cite this

    Satoshi Gazette Data Desk, El Salvador’s disclosed wallet (sg-onbtc-wallet), version 1.0.0, data through 1 Oct 2026. https://satoshigazette.org/data/downloads/sg-onbtc-wallet.json

    Columns, notes and checksums (5 columns) for El Salvador’s disclosed wallet

    JSON sha256 ec937152df6d58e72ce81020952278c44ff585c8c61afbb1dfb79cf7fd263663

    CSV sha256 b85e68b16473eccd3a705b5196fea3254bd97548440d3f0feb674a88f4113e38

    One row per block that moved the balance. The disclosed addresses and their balances are in the JSON. UTF-8 with one header row. An empty cell is never zero; the data dictionary says what it means in each column. In a spreadsheet, import the columns as text, so that no figure is reformatted or shortened.

    block_height
    A block in which confirmed transactions moved bitcoin into or out of the disclosed addresses.
    block_time
    The block’s header time, in Unix seconds.
    delta_sats
    Net change in the block, in sats; negative for a spend.
    cumulative_sats
    The confirmed balance after the block, in sats; the last row’s is the confirmed total the JSON gives.
    tx_count
    Transactions in the block that touched the addresses.