On-chain analysis ties 1.1M BTC to Satoshi Nakamoto

Forensics links about 1.1 million BTC across 22,000 addresses to Satoshi Nakamoto; the coins have lain untouched since 2010, with researchers citing lost keys, death or deliberate restraint.

On-chain forensic analysis has linked roughly 1.1 million bitcoin to Satoshi Nakamoto across about 22,000 addresses. The cluster has not recorded an outbound transaction since around 2010, according to researchers who reconstructed the holdings from early block data.

The reconstruction relies on a pattern known as the Patoshi Pattern, identified by researcher Sergio Demian Lerner. Analysts examined values embedded in early coinbase transactions — notably the ExtraNonce field and the least-significant byte of the nonce — and found a consistent, non-random fingerprint across many early blocks. That fingerprint traces to Block 0, the Genesis Block mined on Jan. 3, 2009, and disappears near block 54,000 in late 2010.

Researchers interpret the pattern as evidence of a single, high-throughput mining setup running custom, multi-threaded software. The pattern’s slope in ExtraNonce values and constrained nonce byte ranges indicate coordinated parallel threads assigned to different sub-ranges of the nonce space. The configuration left a reproducible signature on the public ledger that analysts have used to group addresses into the Patoshi cluster.

The addresses attributed to the cluster each show the 50 BTC reward typical of Bitcoin’s earliest blocks and cumulatively hold an estimated 1.09–1.1 million BTC, about 5.47% of Bitcoin’s 21 million supply. At current prices the cache is worth tens of billions of dollars. The most widely recognized address in the group is the Genesis address, 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa; the original 50 BTC from the Genesis block is coded as unspendable, though that address has received later tribute transfers and held roughly 107.22210303 BTC as of mid-June 2026. Analysts report no outbound transfers from the Patoshi cluster in more than 15 years.

Two early transactions have clear links to Satoshi. On Jan. 12, 2009, 10 BTC went to cryptographer Hal Finney as a test. In April 2009, a transfer of 32.51 BTC was recorded in correspondence with developer Mike Hearn. In April 2011 Satoshi sent a final known message stating they had “moved on to other things.”

Researchers and long-term holders offer three main explanations for why the Patoshi coins remain idle. One is lost private keys: early Bitcoin users had limited tools for secure key storage and keys could have been deleted or lost with hardware failure. A second is death: if Satoshi was an individual who later died, the keys may not have been preserved. A third is that whoever controls the keys is choosing not to spend the coins.

Analysts note potential effects if any coins from the cluster were spent. Reintroducing roughly 5.5% of Bitcoin’s total supply into active circulation would change assumptions about permanently dormant supply and could affect market liquidity and prices. Any outbound transaction would generate a public ledger trail; if funds routed through known custodial services or exchanges that perform identity checks, on-chain analysis could produce investigatory leads linking those transactions to real-world entities.

For now, the Patoshi addresses remain visible on the blockchain but inactive: mapped and studied by forensic teams, and accessible only to whoever controls the corresponding private keys, if those keys still exist.

The material on GNcrypto is intended solely for informational use and must not be regarded as financial advice. We make every effort to keep the content accurate and current, but we cannot warrant its precision, completeness, or reliability. GNcrypto does not take responsibility for any mistakes, omissions, or financial losses resulting from reliance on this information. Any actions you take based on this content are done at your own risk. Always conduct independent research and seek guidance from a qualified specialist. For further details, please review our Terms, Privacy Policy and Disclaimers.

Articles by this author