Downloads
The Gazette’s saved datasets as files, at addresses that do not change.
Licence
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: 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 Gazette fetched no price. 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; no other field in any file names a currency.
Files
Fee estimates and the queue
Read from mempool.space when the page is served, never stored.
No download: its values are read when a page is served and are not saved.
Node software on reachable nodes
Every peer in KIT’s network snapshot, by the software it announces.
- Node software on reachable nodes, JSON · 62 kB
- Node software on reachable nodes, CSV · 13 kB
- Node software on reachable nodes, Metadata · 10 kB
- Licence
- CC BY 4.0 ↗
- 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.
- Cite this
Satoshi Gazette Data Desk, Node software on reachable nodes (sg-node-software), version 1.2.0, data through 15 Nov 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.
Not recorded: 16 Oct 2026, 69 of the 2,700 peers seen opened in a day announced no readable software, over the rule's 2 percent, against 2 to 8 on every day before.
Not recorded: 27 Oct 2026, no KIT snapshot.
Not recorded: 31 Oct 2026, no KIT snapshot.
Recorded as read: 17 Oct 2026, 2,643 peers connected within the day, against a median of 1,873 over the seven days before; reachable peers rose from 8,704 on 15 October to 9,682.
JSON sha256 c0e96fcf00a366267a9fee07452abd4bd27a125b57d3b99fd617fef5f8ad6f54
CSV sha256 5894ba452050cce681a65daecc19da34ac8946baf1d6b7105fc95e00f166f185
One row per KIT snapshot day recorded; 3 days not recorded are listed in the JSON’s gaps and in the notes. 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.
- 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.
Node software releases
bitcoincore.org’s support windows and advisories, with Knots releases beside them.
JSON only: the file holds five lists (release lines, security advisories, Core releases, the Knots feed and Knots’ release record), not one table.
- Licence
- CC BY 4.0 ↗
- 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.
- Cite this
Satoshi Gazette Data Desk, Node software releases (sg-core-lifecycle), version 1.2.0, data through 15 Nov 2026. https://satoshigazette.org/data/downloads/sg-core-lifecycle.json
Notes and checksums for Node software releases
JSON sha256 0ac02af8c005bc4dac2ca8b2c790b5814a7c3bc4238601642cbf405d0bf396eb
Lightning and BTCPay Server releases
Releases of LND, Core Lightning, Eclair and BTCPay Server, from GitHub’s release record.
- Lightning and BTCPay Server releases, JSON · 59 kB
- Lightning and BTCPay Server releases, Metadata · 2 kB
JSON only: the file holds one list of releases for each of four projects, not one table.
- Licence
- CC BY 4.0 ↗
- 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.
- Cite this
Satoshi Gazette Data Desk, Lightning and BTCPay Server releases (sg-lightning-releases), version 1.0.0, data through 11 Nov 2026. https://satoshigazette.org/data/downloads/sg-lightning-releases.json
Notes and checksums for Lightning and BTCPay Server releases
JSON sha256 913bd290b14af0b7e2e6418b287583c51fcba08723a8345f82a5d066eef40baf
BIP status
Every BIP’s status in the BIP repository’s own words, and the changes recorded.
- Fields
- BIP status: Dictionary →
- Licence
- CC BY 4.0 ↗
- 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.
- Cite this
Satoshi Gazette Data Desk, BIP status (sg-bip-status), version 1.0.0, data through 21 Nov 2026. https://satoshigazette.org/data/downloads/sg-bip-status.json
Columns, notes and checksums (15 columns) for BIP status
The JSON also holds every status change the Gazette 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 823a929bd09b0605edfe515f645c716b8246859b12418766ebce261c1d76dee2
CSV sha256 80b18337a3f66ab9cc7d33648a077d04119d38a77c29e8ad74f5c5a4d7592d3c
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.
- 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 Gazette 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.
Difficulty period, halvings and subsidy
The difficulty period, the halvings and the block subsidy, fixed by block height.
No download: its values are read when a page is served and are not saved.
Public Lightning network
Public channels, capacity and nodes a day, as one operator’s node received the gossip.
- Public Lightning network, JSON · 213 kB
- Public Lightning network, CSV · 139 kB
- Public Lightning network, Metadata · 5 kB
- Licence
- CC BY 4.0 ↗
- 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.
- Cite this
Satoshi Gazette Data Desk, Public Lightning network (sg-lightning-network), version 1.0.0, data through 20 Nov 2026. https://satoshigazette.org/data/downloads/sg-lightning-network.json
Columns, notes and checksums (8 columns) for Public Lightning network
Read from mempool.emzy.de, an instance of mempool’s software run by Stephan Oeste (Emzy). Private channels cannot be counted. Capacity is the bitcoin locked in public channels, not the amount that can be sent through them. Counts are the public network as mempool.emzy.de’s node received it that day; other collectors’ counts differ.
Not recorded: 17 Sep 2024, mempool.emzy.de’s statistics hold no row.
Not recorded: 18 Sep 2024, mempool.emzy.de’s statistics hold no row.
Not recorded: 19 Sep 2024, mempool.emzy.de’s statistics hold no row.
Not recorded: 20 Sep 2024, mempool.emzy.de’s statistics hold no row.
Not recorded: 21 Sep 2024, mempool.emzy.de’s statistics hold no row.
Not recorded: 22 Sep 2024, mempool.emzy.de’s statistics hold no row.
Not recorded: 31 Aug 2026, mempool.emzy.de’s statistics hold no row.
Not recorded: 1 Sep 2026, mempool.emzy.de’s statistics hold no row.
Not recorded: 2 Sep 2026, mempool.emzy.de’s statistics hold no row.
Not recorded: 3 Sep 2026, mempool.emzy.de’s statistics hold no row.
Not recorded: 4 Sep 2026, mempool.emzy.de’s statistics hold no row.
Not recorded: 5 Sep 2026, mempool.emzy.de’s statistics hold no row.
Not recorded: 6 Sep 2026, mempool.emzy.de’s statistics hold no row.
Not recorded: 7 Sep 2026, mempool.emzy.de’s statistics hold no row.
Recorded as read: 25 Aug 2025, Nodes rose from 11,593 to 16,987 in a day while channels and capacity held; every later day in mempool.emzy.de’s history keeps the new level.
JSON sha256 1383958082471e4a724da958d66e1b8d7a55a5adeb1932aeba791701931b3dc9
CSV sha256 8be6d6a46da73532935b917688cfe7be9ba9d2078eec7489b40b88c52f472bd4
One row per UTC day recorded; 14 days not recorded are listed in the JSON’s gaps and in the notes. UTF-8 with one header row. An empty cell is never zero.
- day
- The UTC day the row counts.
- channels
- Public channels in the source’s row for the day.
- nodes
- Public nodes: the sum of the source’s four node counts by address type.
- capacity_sats
- Bitcoin locked in those channels, in satoshis.
- capacity_btc
- The same, in BTC, exact to the satoshi.
- endpoint
- Which of the source’s reads the row was taken from: statistics/all or statistics/1m.
- served_at
- The source’s Date header on that read, UTC.
- sha256
- sha256 of that response as served.
Hashprice at difficulty
The Gazette’s arithmetic on three mempool.space readings, live.
No download: its values are read when a page is served and are not saved.
Difficulty
Every difficulty period since genesis, its difficulty exact from the block header.
- Fields
- Difficulty: Dictionary →
- Licence
- CC BY 4.0 ↗
- 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.
- Cite this
Satoshi Gazette Data Desk, Difficulty (sg-difficulty-ledger), version 1.1.0, data through 14 Nov 2026. https://satoshigazette.org/data/downloads/sg-difficulty-ledger.json
Columns, notes and checksums (17 columns) for Difficulty
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 09d7e7fab9457bcc0e2de8c0e41c4fbeae4274350f559dc93acfd9d1f16be71b
CSV sha256 e2eb5d2cbbc7d3a8d55ef56c32077e25dc4c0cc79180a199694cbbc694d8f353
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.
- 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 yet complete: the ledger runs from block 628,992 through block 832,607, and the period file that holds it runs through block 975,789, read on 14 Nov 2026. Its files will be offered once the ledger reaches that block.
Public miners
Mined, sold and held per quarter, as the 11 listed miners on the roster filed it.
- Licence
- CC BY 4.0 ↗
- 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 Gazette’s reads stay under five.
- Cite this
Satoshi Gazette Data Desk, Public miners (sg-public-miners), version 1.0.0, data through 30 Sep 2026. https://satoshigazette.org/data/downloads/sg-public-miners.json
Columns, notes and checksums (26 columns) for Public miners
Filed figures, read from each company’s own SEC reports: not a count of what public miners as a whole mined or sold. A figure with no number has an empty value_btc and a state that says why, which is unknown, not zero. The file holds no amount of money: its numbers are bitcoin quantities, and beside them stand dates, form types, accession numbers and the Gazette’s notes in words; mined minus sold and the roll-forward remainder are worked out on the page and are in no file.
JSON sha256 4100d9a8ae3a71cb8b555b888c9d6b227fd6b98a69d4e2e81db12f5da70e3bd1
CSV sha256 a8433a230783dd5f0faf514e57d801e4cd1e2560d94600ebda63c03548fa7040
One row per figure: a company, a calendar quarter and one quantity, with its state and the first place its number is printed. Quantities stated only for a longer period, the roster, the log of documents read, and every further place and quote are in the JSON. UTF-8 with one header row. An empty cell is never zero.
- entity
- The company’s key in the file.
- company
- The company’s name at the end of the window.
- cik
- The registrant’s CIK on EDGAR.
- ticker
- Its ticker.
- basis
- The basis of the company’s rows, as its own reports state them: consolidated, subsidiary or parent_excluding_subsidiary.
- period_start
- First day of the calendar quarter.
- period_end
- Last day of the calendar quarter.
- fiscal_label
- The quarter as the company’s reports name it in its fiscal year, in the Gazette’s words.
- field
- Which quantity the row is: held_start, mined, sold, purchased, other_in, other_out, held_end, pledged_or_posted, lent or joint_venture_share.
- label
- The filing’s own name for the row or the movement; words in square brackets are the Gazette’s.
- state
- stated, derived, not_stated_in_units, none_in_complete_rollforward or not_separable; only the first two carry a number.
- value_btc
- The quantity, an exact decimal in BTC; empty where the state carries no number, which is unknown, not zero. A reported nil is 0.
- approximate
- true when the filing says approximately, or the like, of this number.
- pool_fee_basis
- For a mined figure with a number, as the filing says of that number: after_pool_fees, before_pool_fees, or not_said where it is silent or says both.
- derivation
- For a derived figure, the arithmetic in words; its components are in the JSON.
- basis_note
- What the number contains or leaves out, and for a pledged, posted or lent quantity whether it sits inside the held figure or beside it.
- sources
- How many places the JSON holds for the figure.
- receipt_form
- The form of the filing the number is printed in; for a derived figure, the first number of its arithmetic.
- receipt_accession
- That filing’s EDGAR accession number.
- receipt_filed_on
- The day that filing was made.
- receipt_document_url
- Address of the document the number is printed in, on sec.gov.
- receipt_locator
- Where in that document the number stands.
- receipt_covers_start
- First day of the period the printed number covers; the day itself for a balance.
- receipt_covers_end
- Last day of the period the printed number covers.
- longer_period
- true when the row has no number and the JSON’s spans hold this quantity for a longer period that takes in the quarter; the longer period’s number is in the JSON and is never divided.
- later_values
- How many different numbers later reports print for the same period; each is in the JSON, and the first-reported value stands.
Pool block share
mempool.space’s pool labels for three windows, read once a week and filed.
- Licence
- CC BY 4.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, Pool block share (sg-pool-blocks), version 1.1.0, data through 18 Nov 2026. https://satoshigazette.org/data/downloads/sg-pool-blocks.json
Columns, notes and checksums (7 columns) for Pool block share
JSON sha256 479c18db993f71c935159e8b00f4162c9411f5109fdea4bb6228f91b89e5916c
CSV sha256 3b3388345292afaeb31a772cc180c1164140036d5281e1b1bd4426ea0b8cfe39
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.
- 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.
Company treasuries
Each company’s latest filing.
- Licence
- CC BY 4.0 ↗
- Source terms
- SEC filings are US federal records in the public domain; each row cites its accession. Metaplanet Inc.: its own terms apply.
- Cite this
Satoshi Gazette Data Desk, Company treasuries (sg-treasury-ledger), version 2, data through 15 Nov 2026. https://satoshigazette.org/data/downloads/sg-treasury-ledger.json
Columns, notes and checksums (25 columns) for Company treasuries
No field is a price, and the Gazette 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 95da81142b4b75c20afdb8d335b849661a53811c110f6445a17eadaaa76c00aa
CSV sha256 9144bb0aaeb7209d9f06614779c56b51280a313f4dcc2522fcf2b638b7378fd4
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.
- 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 Gazette’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 totals
Every bitcoin total Strategy has stated in an 8-K, 10-Q or 10-K since 2020, one row each.
- Strategy’s filed totals, JSON · 206 kB
- Strategy’s filed totals, CSV · 71 kB
- Strategy’s filed totals, Metadata · 5 kB
- Licence
- CC BY 4.0 ↗
- 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 Gazette’s reads stay under five.
- Cite this
Satoshi Gazette Data Desk, Strategy’s filed totals (sg-strategy-filings), version 1.0.0, data through 15 Nov 2026. https://satoshigazette.org/data/downloads/sg-strategy-filings.json
Columns, notes and checksums (19 columns) for Strategy’s filed 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 374d2b75c54fe2ae0e4012bfa5c82a5038a906019d1472825aa8fede0bff7aca
CSV sha256 167a4202cfc585fe0651a487262c115eae9f2f555a5611986f6dec855381d98b
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.
- 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.
Claims floor
Each holder’s latest disclosure, summed against issued supply at a pinned block.
- Licence
- CC BY 4.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.: its own terms apply.
- Cite this
Satoshi Gazette Data Desk, Claims floor (sg-claims-floor), version 2.3.0, data through 17 Nov 2026. https://satoshigazette.org/data/downloads/sg-claims-floor.json
Columns, notes and checksums (11 columns) for Claims floor
A sum of dated disclosures, not a count at one moment: each row keeps its own as-of date, and the block pins issued supply only. The spot ETF rows are each read, listed trust’s latest filed quarter-end quantity, the same figures the spot ETF dataset (sg-etf-trusts) holds, not today’s holdings; a trust on that dataset’s list that is not read has no row here: unknown, not zero.
JSON sha256 3a0f51ad33ee8c78a0abc213e351cce4defe923a5b262f8aecd681070eb78883
CSV sha256 be9dd4f8d72e5b016ca1859b6b7b9c7b41d84ee4d64ce0bfe2b80c971bb5cdf1
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.
- 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.
Spot ETF trusts
Bitcoin at each quarter end in 14 of the 16 trusts on the list, from their 10-Q and 10-K.
- Licence
- CC BY 4.0 ↗
- 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 Gazette’s reads stay under five.
- Cite this
Satoshi Gazette Data Desk, Spot ETF trusts (sg-etf-trusts), version 1.0.0, data through 30 Sep 2026. https://satoshigazette.org/data/downloads/sg-etf-trusts.json
Columns, notes and checksums (11 columns) for 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 1c3a1eee38c237c5cfe20c2752807e77d3a6801035fb631fa700cbf2288572ee
CSV sha256 839f40403495a33d2af5476a7cab35305911b221d0eabef9a77d86d89887cfba
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.
- 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.
- El Salvador’s disclosed wallet, JSON · 71 kB
- El Salvador’s disclosed wallet, CSV · 52 kB
- El Salvador’s disclosed wallet, Metadata · 3 kB
- Licence
- CC BY 4.0 ↗
- 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.
- Cite this
Satoshi Gazette Data Desk, El Salvador’s disclosed wallet (sg-onbtc-wallet), version 1.0.0, data through 21 Nov 2026. https://satoshigazette.org/data/downloads/sg-onbtc-wallet.json
Columns, notes and checksums (5 columns) for El Salvador’s disclosed wallet
JSON sha256 e12e651bf0bd44d642579a43e76097c9867dc861d9375141d00aff7cc29f4271
CSV sha256 91f10e27045f2ea6da6646289b391ffce103d2990d11518ab8efc4d011206cd1
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.
- 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.