On-chain censusBitcoinJan 2009 – Sep 2026

Embeddings in Bitcoin: what people hid in the chain after the genesis block.

Seventeen years and 965,000 blocks separate the newspaper headline in Bitcoin's first block from today. We went looking for everything written after it: in the same field Satoshi used, in the output Bitcoin later set aside for data, and in the fake addresses and fake keys people reached for when there was no sanctioned place at all. Most of it is machine memos. Some of it is a library.

At a glance
Bitcoin's first block carries a newspaper headline that its inventor typed into a field only miners can write. We read all 965,135 blocks to find what everyone else wrote after it, in the four places a transaction can hold text. Miners' personal notes peaked in 2015 and are gone. The real library is hidden in fake addresses: 3,286 transactions spelled out documents, from a tribute to a murdered cryptographer to a papal encyclical, in 96,231 outputs that no node can ever delete. And since the 80-byte OP_RETURN cap was lifted in October 2025, the chain has become a billboard, with one 5-day smear campaign of 13,062 transactions costing its sender 0.10 BTC.
4
Places a transaction can hide text
96,231
Unspendable outputs spelling documents
3.2 BTC
Locked in them for good
13,062
Transactions in one 5-day smear, for 0.10 BTC

On the morning of 3 January 2009 the front page of The Times carried the headline "Chancellor on brink of second bailout for banks". Some time that day Satoshi Nakamoto typed it, with the date, into the first block of Bitcoin, the block now called the genesis block. It sits in a field that only the person who mines a block gets to fill, a few spare bytes at the front of the transaction that pays the miner, and it has been read as a timestamp, a manifesto and a joke ever since. It is also the first thing anyone wrote into Bitcoin that was not money.

Bitcoin was never meant to hold writing. Every byte in a block is supposed to be a coin moving from one owner to another. But a transaction is only a list of numbers, and a few of those numbers are loose enough that a person can put whatever they like in them, as long as they pay the fee. Bitquery indexes the complete Bitcoin chain, so we read every block, from Satoshi's headline to the first days of September 2026, and pulled out every embedding, every place where the numbers turn out to be words. There are four such places. The oldest, the miner's field where the headline lives, is the one people talk about, and it turns out to be the quietest. The busiest by far is a slot Bitcoin added in 2014 specifically so that people would stop doing damage elsewhere. The most surprising is the damage itself, a trick with fake addresses that has been used to write whole books into the chain, one line at a time, in a form no computer running Bitcoin can ever delete.

Three things came out of the reading. The tradition Satoshi started, of miners leaving notes in their blocks, peaked in 2015 and is gone. The real library on the chain is written in fake addresses, tens of thousands of them, holding a papal encyclical, a human-rights statement on Tiananmen, an epic in Sanskrit and a tribute to a murdered cryptographer. And since Bitcoin Core lifted its 80-byte limit on data outputs in October 2025, the chain has become a billboard, with one five-day campaign of more than 13,000 transactions aimed at a single developer. One limit on what follows has to be said up front. Our index is missing the miner's field for about a fifth of all blocks, all of them between 2016 and 2021, so for those years the count of miners' notes is a floor and not a measurement.

01 — The premise

Four places to hide a sentence

A Bitcoin transaction has inputs, which point at coins being spent, and outputs, which say who gets them. Each output carries a small program, usually one line long, that names the owner by a 20-byte fingerprint of their key. Each input carries the signature that satisfies the program on the coin it spends. Nothing in that design has room for a message, and yet every part of it leaks a little.

The first leak is the coinbase. The transaction that pays the miner has an input that spends nothing, so its signature field is free space, and the miner can put anything in it. That is where the headline lives, and where mining pools now stamp their names. Only the miner of a block can write there, and there are only about 144 blocks a day, so the field is scarce.

The second is a fake address. An output that pays a fingerprint pays whoever holds the matching key. If the fingerprint is not a fingerprint at all but 20 letters of text, nobody holds the key, the coins are gone for good, and the text is on the chain. This works in any year and anyone can do it. It is also the most expensive trick, though the fee does not show it. Every node on the network keeps a list of unspent outputs so it can check new spends, and a fake-address output sits in that list forever, because it can never be spent.

The third is a fake public key. Some older output types carry whole keys rather than fingerprints, and a key holds three times the text a fingerprint does. This was the trick of choice in Bitcoin's first years and it is how the WikiLeaks cables were pointed at from inside the chain.

The fourth is OP_RETURN. In 2014 Bitcoin's developers gave up fighting the fake-address trick and added an approved slot, an output type that announces itself as data, pays nobody, and is dropped from the unspent list the moment it arrives. In return they capped it, at 40 bytes and soon 80. The cap held for eleven years.

Figure 1The four places a transaction can hold text
01 · MINERS ONLYCoinbase inputSpare bytes in the input ofthe transaction that pays theminer.ONE TRANSACTIONinput → text goes hereoutputKept in the block965,135blocks read02 · ANYONE, SINCE 2014OP_RETURN outputAn output that declares itselfdata. Pays nobody.ONE TRANSACTIONinputoutput → text goes hereNodes may forget it4,412,782outputs that read as text03 · ANYONE, ANY YEARFake address20 bytes of text where anaddress hash should be.ONE TRANSACTIONinputoutput → text goes hereIn every node's unspentlist, for good96,231outputs spelling documents04 · ANYONE, 2011 TO 2014Fake public keyText inside a key that nowallet can sign for.ONE TRANSACTIONinputoutput → text goes hereIn every node's unspentlist, for good8,533transactions carrying text
Only miners can write to the coinbase. The other three are open to anyone who pays the fee. Counts are what we found across 965,135 blocks; the OP_RETURN figure is outputs whose data reads as text, out of 258,020,318 OP_RETURN outputs in total.

The place Satoshi used turned out to be a trickle of pool names with a few human years in the middle. The approved slot carries far more, but most of it is machine memos. The fake addresses are where the writing is.

What the four channels hold
ChannelWho can writeCarries textPeak years
Coinbase inputMiners only590,679 blocks, almost all pool tags2011 to 2015 for notes
OP_RETURN outputAnyone, since 20144,412,782 outputs, 2,925,116 distinct texts2015 to 2017, then 2025 on
Fake addressAnyone96,231 outputs in 3,286 transactions2014 to 2015
Fake public keyAnyone, older output types8,533 transactions, mostly token records2011 to 2014
02 — The coinbase

The years the miners talked

For the first two years nobody followed Satoshi's example. The coinbase carried the nonce, the number a miner changes while hunting for a valid block, and nothing else. Then, in the summer of 2011, a pool called Eligius, run by the developer Luke Dashjr, began writing lines of Latin into its blocks: Benedictum Nomen Iesu, Benedicta excelsa Mater Dei, a cycle of Catholic blessings that ran across fifteen blocks that June. The reply came two months later, in the fake-key channel rather than the coinbase, and it was an obscene attack on Dashjr by name that ended "Stop polluting the blockchain with your nonsense." Every argument Bitcoin has had since about writing on the chain was already there in August 2011, including the irony that the complaint was itself written on the chain.

The coinbase's human years belong to the pools that let their miners type. BTC Guild, Eligius and then the Chinese pools HaoBTC and BTCChina put a text box in front of their users, and the users used it. The 2015 crop is the largest, with aphorisms in capitals, birthday wishes, Matrix quotes, "Long live Ukraine!" in three blocks on a single September day. In June 2016 a HaoBTC miner named Sun Chun Yu proposed to Zhuang Yuan in a block. Her answer, "YES!", is in another one, two hours later. Every one of those blocks was worth 25 bitcoin to whoever mined it, and the proposal cost nothing extra.

Figure 2Blocks whose coinbase carries a personal note, by year
BLOCKS WHOSE COINBASE CARRIES A PERSONAL NOTE01252503755001231159128813173143231528168171819202122423232414252426hatched: index missing the coinbase script for 191,427 blocks2026 to 2 September. Pool tags, worker names and company branding excluded.
Notes, wishes, names and slogans, with pool tags and worker names removed. The hatched years are the ones where our index lacks the coinbase script for 191,427 blocks (heights 377,579 to 684,415), so the bars there are floors. In a sample of 315 of the missing blocks fetched from a public explorer we found no personal notes.

After 2016 the notes thin out to almost nothing. From 2017 the coinbase carries pool names, worker identifiers, and a few slogans that are politics of a different kind. Foundry's blocks say "#dropgold". Marathon's say "Made in USA", and for two weeks in May 2021 they said "OFAC Compliant Block", a tag that appears in two dozen blocks in our index and then stops. Antpool blocks still carry a customer's birthday wish now and then, which is why the bars do not quite reach zero. But the thing Satoshi did, a person leaving a line in a block they had won, belongs to the years when individuals still mined. The miners are companies now, and companies leave logos.

03 — The fake addresses

The library nobody can burn

Six weeks after the Eligius blessings, on 30 July 2011, the security researcher Dan Kaminsky built a transaction with dozens of fake addresses in it. Read in order, their fingerprints spell a tribute to Len Sassaman, a cryptographer and friend who had died that month, complete with a portrait drawn in text characters. The transaction paid a heavy fee and left most of a bitcoin sitting in outputs that can never be spent. It is the earliest document we found on the chain, and it set the pattern for everything that followed.

A document is cut into pieces the length of an address, each piece is dressed up as one, and a transaction pays a few hundred satoshis, hundred-millionths of a bitcoin, to each one. The reader collects the outputs and glues them back together. Nobody can spend the coins, so every piece stays in the unspent list on every node, permanently. The developers built OP_RETURN in 2014 as the alternative, a data output that nodes could forget. It did not stop the address trick, and 2014 and 2015 were the trick's biggest years.

Figure 3Unspendable outputs that spell text, by year
UNSPENDABLE OUTPUTS THAT SPELL TEXT, PER YEAR012,50025,00037,50050,00011122,7011327,1961444,695158,595163,0901718192021550221,093233,736242,236251,7622620 bytes of text where an address hash should be; each is a permanent entry in the UTXO set.
Fake-address outputs whose fingerprint reads as text, from 3,286 transactions. The 2014 and 2015 peak is mostly one uploading tool, Apertus, and the people who used it to archive news, poetry and whole books.

What people chose to make permanent is the interesting part. In September 2014 someone uploaded long passages of the Mahabharata, in Sanskrit, across more than a hundred transactions in a single evening. On the fourth day of the Umbrella protests that October, six transactions carried news coverage of Hong Kong's occupied streets. The week Pope Francis published his encyclical on climate, Laudato Si', in June 2015, someone spent two hours putting the whole English text into the chain, sixty transactions long. In March 2017 a single transaction carried a Human Rights Watch statement demanding that China acknowledge the Tiananmen killings. Alongside these are the things you would expect from an archive built by whoever showed up: biographies of Gandhi, Einstein and Michael Jackson, Valentine's messages, a birthday greeting from "The Fantastic Four Gang", and a long Italian obscenity.

Six documents in the fake-address channel
DocumentDateTxsText outputsFeesLocked foreverFirst tx
Len Sassaman tribute (ASCII portrait), by Dan Kaminsky2011-07-301760.15 BTC0.76 BTC930a2114…
WikiLeaks Cablegate backup (7z pointer)2013-04-08120.0482 BTCunder 0.001 BTC691dd277…
Mahabharata, Sanskrit epic (excerpts)2014-09-141255,1850.0371 BTC0.285 BTC4507cbd6…
Hong Kong Umbrella protest coverage2014-10-0163530.0041 BTC0.019 BTC004dcf6d…
Laudato Si', papal encyclical2015-06-186013,4360.0047 BTC0.074 BTC197f7651…
Human Rights Watch statement on Tiananmen2017-03-2013670.075 BTC0.002 BTC91b9b445…

The WikiLeaks entry is the odd one out, and it is the one people have heard of. On 8 April 2013 a transaction wrote "Wikileaks Cablegate Backup" and the name of a compressed archive into fake public keys, with a pointer to a second transaction holding a download tool named after Satoshi. The archive itself is in the chain too, spread over the outputs of the transactions around it. It cost 0.048 BTC in fees, and whether it was a backup, a stunt or a way of putting the leak beyond seizure, it left a government's cables somewhere no court can order deleted.

The text outputs hold about three bitcoin between them, locked for good, which is a small bill. Each one is also a row that every full node has carried since the day it was written and will carry until the network stops, and the uploaders of 2014 and 2015 added tens of thousands of them in two years. Our sibling piece on what inscriptions did to Bitcoin measured the same kind of permanent state from a different decade; the address trick was the original version of it.

04 — OP_RETURN

The sanctioned slot, and what actually goes in it

OP_RETURN was meant to be the compromise. Write your data here, pay for the bytes, and the network will forget it once the block is stored. People took the offer. There are a quarter of a billion of these outputs on the chain, and a few million of them decode as readable text. Almost none of that text was written for a person to read. Most of it is memos that a cross-chain swap service writes to itself, records from a name registry, hashes with a prefix, token mints and JSON. Filtered down to sentences of two or more words, the human part of OP_RETURN is about 15,000 distinct messages in twelve years.

Figure 4Distinct human-written OP_RETURN messages, by year first seen
DISTINCT HUMAN-WRITTEN OP_RETURN MESSAGES, BY YEAR FIRST SEEN01,2502,5003,7505,00015514941151,1731659917543181,02219585201,051211,1532281923695242,527253,87826Sentences of two or more words; protocol memos, tokens, hashes and JSON excluded. 2026 to 2 September.
A message is counted once, in the year it first appeared, however many times it was repeated. Around a thousand new sentences a year from 2015 to 2024, then 2,527 in 2025 and 3,878 in the first eight months of 2026.

The sentences themselves are what you would find on any wall. Love notes in German and Portuguese, birth announcements, "Carving my name into the blockchain", a good deal of Satoshi impersonation, the odd confession about faxing a seed phrase to customer support. A few are history. On the anniversary of the genesis block in 2022, someone wrote "dedicated to Hal Finney on the 3rd of January, 2009. I'll be next", in one transaction. The day after Alexei Navalny died in 2024, another carried "RIP Navalny. Someday Russia will be free" and, in Russian, "Stop the war with Ukraine".

The repeated messages tell a different story, about who pays to say the same thing thousands of times. The biggest single campaign before 2026 was a protest in the block-size fight of March 2016, "503: Bitcoin over capacity!", repeated across a hundred blocks. The next was a buyer's advertisement with a Protonmail address, then a wallet-recovery service, then a birthday message from the exchange Gemini for the pizza-day block.

The most repeated human messages in OP_RETURN
MessageOutputsFirst seenBlocks
"503: Bitcoin over capacity!"13,9022016-03-05401,266 to 401,365
"We'll buy your Bitcoins. sell.buy.bitcoin@protonmail.com"10,7902019-03-14567,044 to 568,360
"The Pizza Block by Gemini 🍕"7,2892025-05-22897,813
"WWW.BTCKEY.ORG Bitcoin wallet recovery and wallet decryption"5,5302020-03-08621,053 to 655,926
"endur.io 🌱 Brand awareness in everyday transactions."3,0062025-01-25880,296 to 949,376
"Carving my name into the blockchain"2112015-11-13383,762 to 444,091
05 — 2026

The cap comes off

In October 2025 Bitcoin Core shipped version 30, and with it the removal of the 80-byte limit that nodes had applied to OP_RETURN outputs before passing them on to other nodes. The rules every node enforces did not change, and a miner could always include a bigger output if someone handed it to them directly. The change was that ordinary nodes would now pass such transactions along. A rival version of the software, Bitcoin Knots, maintained by Luke Dashjr, kept the cap and tightened it, and the two camps spent the winter arguing in public about what a node should agree to carry.

The chain shows what the change did. Before v30, a text message over 80 bytes appeared a few dozen times in most months, and each one had to be handed straight to a miner. By February 2026 there were thousands. The big single payloads arrived too, the full text of the United States Constitution in one output that May, and Satoshi Nakamoto's original announcement email in June. The largest image we found, nearly a hundred kilobytes of it, is older than the change. Marathon mined it in May 2025, and at that size it could not have travelled through ordinary nodes, so someone handed it to the miner directly.

Figure 6Distinct text messages over 80 bytes, per month
DISTINCT TEXT MESSAGES OVER 80 BYTES, PER MONTH01,2502,5003,7505,000Jun 25JulAugSepOctNovDecJan 262,818FebMarApr783May687Jun1,263Jul1,622AugSepCore v30 lifts the 80-byte relay capCounted by the month a message first appeared. September 2026 is two days.
Messages longer than the old relay cap, counted in the month they first appeared. The dashed line is the release of Core v30. The February peak is two campaigns, described below; the summer of 2026 is a steady few hundred a month of long-form writing that the network would have refused to carry a year earlier.
The largest single payloads
WhatDateBlockSizeTx
PNG image, 97,446 bytes, in one OP_RETURN, mined by MARA before Core v30 lifted the relay cap2025-05-10896,08897,446 bytes95d12b36…
The United States Constitution, full text2026-05-29951,49244,930 bytes261f3d9a…
Satoshi Nakamoto's 11 Feb 2009 announcement email, full text2026-06-19954,462full text1fc3d183…
Largest text payload found: 99,888 bytes of letter-salad2026-06-05952,50299,888 bytes64abb471…

What the new room was used for first was a fight about the room itself. On 26 February 2026, between one in the morning and half past four in the afternoon, 4,446 transactions from some fifteen hundred addresses put thousands of distinct rants against inscriptions, the images and tokens written into blocks since 2023, and against the miners who accept them, into seventeen blocks. "Fee market manipulation 101", "spam protesting spam", "miners enabling spam for short-term fees are traitors": the phrasing has the cadence of text generated by a model and posted by a script, and the whole day cost a few hundredths of a bitcoin in fees, a few hundred satoshis a message. On every measure that the chain records, it was the thing it was complaining about.

Figure 5Anti-inscription messages per block, 26 February 2026
ANTI-INSCRIPTION MESSAGES PER BLOCK, 26 FEBRUARY 202605001,0001,5002,0001,020910908938,374938,400938,420938,440938,452Block height. 4,446 transactions from 1,536 addresses in one day, 0.0294 BTC in fees.
Each bar is one block. Three blocks carried more than 900 messages each. The senders were 1,536 addresses, most of them used once.

Three weeks later came something more pointed. Over five days in late March 2026, 13,062 transactions carried the same two sentences: "Luke Dash Jr went to the OP_NET House. He's on the OP_NET List". Each came from a separate address of the newest format, Taproot, one address per message, which is the signature of a script working through a list of freshly made keys. It cost its sender a tenth of a bitcoin in fees, a few hundred satoshis a message, about $7,000 at the price of the day, to have the maintainer of the client that wanted to limit OP_RETURN taunted by name in a place that cannot be edited. The chain records the message and the cost. It does not record who paid.

Two campaigns, March and February 2026
CampaignWhenTransactionsSending addressesBlocksFeesPer message
Anti-inscription rants2026-02-264,4461,536170.0294 BTC661 sats
The OP_NET taunt21 to 26 March 202613,06213,0625790.1014 BTC776 sats
06 — What it costs

Cheap to write, expensive to keep

Put the campaigns next to the documents and the economics of writing on Bitcoin come out backwards. Kaminsky's tribute to Sassaman cost close to a whole bitcoin in 2011, when a bitcoin was worth about $13, and it will occupy its rows in every node's unspent list for as long as there are nodes. The encyclical cost less than a tenth of one in 2015. The OP_NET taunt, thirteen thousand messages that every node was free to discard, also cost about a tenth of one, at 2026 prices. Counted in bitcoin per line, the taunt paid about one fifteen-hundredth of what the tribute paid. Counted in the dollars of the day, it paid about three times as much, because the coin had gone from about $13 to about $70,000 in between. The 80-byte cap had priced one kind of speech, the long kind, out of the approved slot and into the permanent one. Lifting it made long writing cheap and disposable at the same time.

Cost per message across four eras
ItemYearMessages or outputsFeesLocked for goodKept by every node?
Genesis headline20091nonenoneYes, in the block
Sassaman tribute (fake addresses)2011760.15 BTC0.76 BTCYes, in the unspent list
Laudato Si' (fake addresses)201513,4360.0047 BTC0.074 BTCYes, in the unspent list
503 over capacity (OP_RETURN)201613,902not measurednoneNo
Anti-inscription rants (OP_RETURN)20264,4460.0294 BTCnoneNo
OP_NET taunt (OP_RETURN)202613,0620.1014 BTCnoneNo

Satoshi's headline was possible because a block has a field nobody polices. Seventeen years on, the same chain holds an encyclical that no node can drop, a human-rights statement addressed to a government that bans it, and thirteen thousand copies of a taunt that any node may discard. Which of the four places gets used depends on what the software will carry that year. Who paid for the taunt, the chain does not say.

07 — The record

Blocks and transactions behind this piece

Notable entries, in order
WhatBlockDateWhere it is
Genesis headline, in the coinbase02009-01-034a5e1e4b…
Eligius Latin blessings begin, in the coinbase139,7922011-06-14coinbase of the block
Tribute to Len Sassaman, text hidden in fake addresses138,7252011-07-30930a2114…
Attack on Luke Dashjr, text hidden in a fake public key141,4602011-08-189740e7d6…
WikiLeaks Cablegate backup, text hidden in fake public keys230,2032013-04-08691dd277…
Mahabharata excerpts, text hidden in fake addresses320,7172014-09-144507cbd6…
Hong Kong protest coverage, text hidden in fake addresses323,2912014-10-01004dcf6d…
Laudato Si', text hidden in fake addresses361,5472015-06-18197f7651…
"503: Bitcoin over capacity!", in OP_RETURN401,2662016-03-0576a41a54…
Marriage proposal and answer, in the coinbase416,2362016-06-14coinbases of blocks 416,236 and 416,253
Human Rights Watch on Tiananmen, text hidden in fake addresses458,1062017-03-2091b9b445…
"OFAC Compliant Block" tag first seen, in the coinbase684,5092021-05-22coinbase of the block
Hal Finney anniversary note, in OP_RETURN717,0082022-01-03c69de2f0…
Navalny message, in OP_RETURN830,7822024-02-1738753254…
97-kilobyte PNG, in OP_RETURN, mined by Marathon896,0882025-05-1095d12b36…
Anti-inscription rant wave, in OP_RETURN938,4102026-02-264,446 transactions across 17 blocks
OP_NET taunt begins, in OP_RETURN941,5402026-03-2184c72d46…
US Constitution, in one OP_RETURN951,4922026-05-29261f3d9a…
Satoshi's 2009 announcement email, in OP_RETURN954,4622026-06-191fc3d183…

Method

How we read the chain

All 965,135 blocks to 2 September 2026, from Bitquery's Bitcoin index. Coinbase: the input script of every block's first transaction, decoded from hex, with the height push removed and runs of four or more printable characters kept; a note is "personal" if it has two or more real words, occurs in twenty or fewer blocks, and matches no pool, worker or company pattern. OP_RETURN: every data output whose pushed bytes are valid text of ten characters or more, grouped by exact text; "human" means two or more words in a row after removing swap memos, registry records, hashes, JSON and known protocol prefixes. Fake addresses: every pay-to-hash output whose 20-byte hash has at least 17 printable characters, or 12 with the rest blank, in transactions with at least two such outputs; documents were reassembled in output order. Fake keys: bare-multisig, pay-to-key and nonstandard outputs whose key bytes contain ten or more printable characters in a row, then filtered for words. Campaign totals come from joining the matching outputs to their transactions and inputs. Fees are the transactions' own; "locked" is the value paid to text outputs.

Known gaps. The index lacks the coinbase script for a block of heights in the middle of the chain, given under Figure 2, so coinbase counts for 2016 to 2021 are floors; a sample of those blocks fetched from a public explorer is reported there. Text in languages that do not use the Latin alphabet is undercounted in the fake-address channel because the printable test is ASCII. Inscriptions in witness data, which are a different medium with their own investigation, are not counted here. Distinct-message counts merge identical texts across years and date them by first appearance.

Questions people ask

What is the Bitcoin genesis block message? The text "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks", which Satoshi Nakamoto placed in the coinbase input of the first block, on the day of that headline. It is readable in the raw block and in any explorer.

Where can text be written into a Bitcoin transaction? In the coinbase input, if you mined the block; in an OP_RETURN output; in a fake address whose 20-byte hash is really text; or in a fake public key inside an older output type. The last two lock the coins paid to them forever.

What is the largest thing written into Bitcoin? By outputs, the encyclical Laudato Si', spread over more than thirteen thousand fake-address outputs in 2015. By a single payload, an OP_RETURN of almost a hundred kilobytes in 2026; the full US Constitution is the largest readable one.

Did Bitcoin Core v30 change what can be written? It removed the 80-byte OP_RETURN relay limit in October 2025. Text messages over that length went from a dozen a month to thousands within four months, and most of the chain's long-form writing dates from after the change.

Run these queries yourself

Every figure above is a query against the public chain. Ask the same questions of the live index through the Bitquery MCP server, start from the Bitcoin API examples, or read our audit of how much bitcoin Satoshi holds, built from the same blocks.