Research status, 2026-10-09 (Part 1 of 2)

Bitcoin Research — Law, Regulation, Markets & Origins (2026)

Methodology

1

2026-10-09

Document text

Research, not advice. Part of the Bitcoin research archive (October 2026). Claims labelled unverified, contested or fringe are reported, not endorsed; statuses of bills and rules are as of the date checked. Government, court and patent records are public domain; the research notes are CC BY 4.0.

Research status, 2026-10-09

This is the completeness and sourcing check of ~/Projects/bitcoin, run on 2026-10-09 after the research agents listed in NEXT.md had finished. It records what is in the repo, how many sources are saved, what was checked and fixed, everything the Spark runs rejected, the known gaps, and every claim the notes mark as unverified, contested, fringe or Spark-rejected. It is research, not advice.

Contents: 1 At a glance · 2 What is in the repo · 3 Saved sources · 4 Checks and results · 5 Fixes made by this check · 6 What the Spark runs rejected · 7 Known gaps · 8 Appendix: every flagged claim

1. At a glance

  • All 17 research jobs in NEXT.md delivered. The origins 2007–2011 job stopped on a scope question in the first pass and was rerun the same evening (update, 2026-10-09): notes/2026-10-09-origins-timeline.md and sources/primary/ (34 files: Satoshi's cryptography-list, bitcoin-list and p2p-research emails, all 539 BitcoinTalk posts, his emails to Wei Dai, Hearn and Andresen, block records for blocks 0, 9 and 170, the first-commit main.cpp, and the bitcoin.org whois). The timeline's § 9 checks every Spark origins claim against primary records, so § 6.2 below is now background only.
  • Every state and DC has a legislation note: 51 of 51 legislation/us-state-XX.md files, each with a sources/states/XX/ folder and INDEX.md. Every legislation file records the date its status was checked.
  • Saved sources: 845 files in 13 topic folders. That is 813 unique by content and about 750 distinct documents, counting a PDF and its text extract once and counting copies saved in two or three folders once. There are 64 INDEX.md files (12 topic, 51 state, 1 nationwide for the states).
  • No secrets found. Text and PDF scans found no private keys, seed phrases, passwords, API keys, passcodes or .onion addresses. The exception is the BIP specifications' published test vectors, which are public examples, not anyone's keys; they are now labelled (§ 4.4).
  • Copyright. Every full copy is a government or court document, a patent, the whitepaper, Satoshi's own writing, or a freely licensed text (BIPs, the Unlicense physical-attacks list). Articles, books and videos appear only as summaries with links. A few non-US government items are full copies for private use only; see § 4.3.
  • Citations. Detailed sections cite inline. Summary tables and "short version" bullets usually restate facts that are cited further down, or cite in a "Sources:" block under the table. An automatic pass found 1,591 of 4,818 substantive paragraphs and table rows with no inline citation marker. Spot checks found the source nearby in every case sampled, but a claim-by-claim audit was not done (§ 4.2).
  • Flagged claims: 540 paragraphs are marked. 423 are unverified, 109 contested or disputed, 42 fringe and 4 Spark-rejected; some carry more than one label. All are listed in § 8.
  • Spark runs: all nine finished. Their rejected material is in § 6: 16 sub-answers labelled CONTESTED or UNDOCUMENTED, 8 claims their verifier rejected, 105 claims it found only partly supported, 15 facts dropped, 23 refused pages, 67 pages skipped as irrelevant, 49 failed fallbacks and 392 search results passed over. Only the books, wallets and banking notes have folded any of this in. The other five notes now point to § 6.
  • This check fixed 12 things in place (§ 5). It settled the Coinme 34-agency participation question from the consent order itself, the CLARITY Act's Senate status from the Senate's own vote record, the withdrawal of the 2020 unhosted-wallet rule, the 2025 repeal of the DeFi broker rule, and which three states ban kiosks.
  • Size: about 570 MB on disk. 181 MB is already committed in .git, and about 390 MB is the working tree. The largest single file is 18 MB (the NYAG–KuCoin stipulation), so nothing approaches GitHub's 100 MB per-file limit. Uncommitted at the time of this check:
  • the six researchers' new files: sources/fincen/ (142 files), sources/states/ (214 plus 52 indexes), sources/satoshi/ (28), sources/wallets/ (21), 54 legislation notes, the books, Satoshi and wallets notes, and this file;
  • this check's edits to files already committed: the banking, walk-in shops and KYC/AML notes, and the bips index.

NEXT.md also had uncommitted changes, which this check did not make.

2. What is in the repo, by folder

Folder What is there Files
notes/ 2026-10-09-who-is-satoshi.md (candidates, evidence for and against, court record, fringe claims), -books.md (books, reviews, reliability), -technology.md (how Bitcoin works, BIPs, forks, mining), -patents.md (patents, COPA, nChain), -hacks-causes-defenses.md (major thefts, causes, defences) 5 notes + README
market/ 2026-10-09-wallets.md (Ballet, Ledger, Trezor, Coinbase, Kraken), -exchanges.md (KYC, P2P, ATMs), -payment-processors.md, -merchants-accepting-bitcoin.md (including dating sites, and dark-web markets from public record), -walk-in-bitcoin-shops.md, -banking.md (debanking, the 2025–26 changes, who serves crypto firms), -link-map.md 7 notes + README
legislation/ us-federal-fincen.md (FinCEN and virtual currency, 1999–2026), us-federal-fincen-wallet-registration.md (the 2020 unhosted-wallet rule and its 2026 withdrawal), us-kyc-aml-selling-bitcoin.md, 51 state and DC notes, and the two summaries us-states-A-M-summary.md and us-states-N-Z-summary.md 56 notes + README
data/ 2026-10-09-link-map.csv (outbound links and the sites that mention them) 1
sources/ 13 topic folders of saved copies, each with an INDEX.md (§ 3) 845 + 64 indexes + README
root README.md, CLAUDE.md, NEXT.md, and this file 4

Not yet in the repo: any market data research (price history, volume, supply, ETFs, institutional holdings), which the README names as the main purpose of market/; and any non-US legislation, which the README names for legislation/ (§ 4.5).

3. Saved sources, by topic

Folder Files Distinct documents Size What they are Rights
sources/banking/ 117 117 36 MB Fed, FDIC and OCC letters, orders, charters and releases; Federal Register rules; House and Senate reports; Custodia court opinions; the Fed master-account database (2 CSV) US government and courts
sources/bips/ 43 43 1 MB 42 BIPs plus the BIP 39 English wordlist Each BIP's own free licence (PD, BSD, MIT, CC0)
sources/darkweb-public-record/ 34 29 4 MB DOJ and Treasury releases and court filings (Silk Road, AlphaBay, Hydra and others); 8 Europol releases US government; Europol is © Europol, private use only
sources/exchanges/ 35 35 52 MB Pleas, consent orders and complaints (Binance, Paxful, KuCoin, BitMEX); state AG and regulator actions on kiosks US federal and state government; courts
sources/fincen/ 142 142 53 MB Every FinCEN guidance, ruling, advisory, alert, enforcement action and Federal Register rule on CVC, 1999–2026; statutes and regulations; speeches; court opinions US government and courts
sources/fincen-wallet-rule/ 41 34 16 MB The 2020 unhosted-wallet NPRM, comment reopenings, the 2026 withdrawals, Unified Agenda entries, the CLARITY Act texts and the Senate cloture vote, 10 public comments, EO 14178, Pub. L. 119-5 US government; the public comments are copyright of their authors, kept as part of the federal record
sources/hacks/ 27 26 13 MB Court records (Bitfinex/Lichtenstein, FTX, Baton v Ledger, Terpin v AT&T, the Coinbase breach MDL), FBI, CISA and FCC documents, Mt. Gox trustee reports, the OSC QuadrigaCX review, the bitcoin.org Android alert, Lopp's list of physical attacks US government and courts; Mt. Gox trustee and Ontario OSC: not public domain, no licence; bitcoin.org MIT; Lopp list under the Unlicense (licence confirmed on GitHub by this check)
sources/kyc-aml/ 93 48 21 MB eCFR sections, U.S. Code, FinCEN forms and notices, Nevada NRS/NAC 671 and FID orders, NY BitLicense rule text, ICE and DOJ pleas, appeals opinions US government and courts (text extracts beside most files)
sources/patents/ 42 42 112 MB 41 US patents and publications (nChain, Coinbase, BofA, IBM, Block, NSA SHA-2 and others); an IETF IPR statement US patents (public record)
sources/payment-processors/ 8 6 1 MB OFAC–BitPay, CFPB and states–Block, NYDFS–Block, FINTRAC penalty notices US government; FINTRAC is Canadian Crown copyright
sources/satoshi/ 28 28 22 MB COPA v Wright judgments and orders, Wright v McCormack, Wright v BTC Core, Kleiman v Wright, Murphy v DHS (FOIA), Kilgore v Nakamoto; the whitepaper; Satoshi's emails and posts; the Satoshi–Malmi archive Courts and US government; whitepaper; Satoshi's own writing. The Malmi archive also contains Malmi's side, as he published it; 8 old passwords in it were redacted
sources/states/ 214 214 45 MB Session laws, enrolled bills, codes, regulator guidance and orders, AG suits, for all 50 states and DC; includes the Coinme multistate consent order added by this check State government and courts
sources/wallets/ 21 21 11 MB FinCEN guidance; SEC v Coinbase and v Kraken; IRS John Doe summonses; Harper v Werfel; Celsius; Baton v Ledger; OFAC–Kraken; FDIC; California AG breach notices; CLARITY texts US government and courts

Duplicates: 28 documents are saved in two or three folders, giving 32 extra copies. Examples are FIN-2019-G001, the 2020 NPRM, the Tennessee kiosk ban, the Custodia opinions and the CLARITY texts. Each folder keeps its own copy so its index is self-contained. Deduplicating is optional.

4. Checks and results

4.1 Every state plus DC

All 51 notes exist. Every one has a sources/states/XX/ folder whose INDEX.md lists each file, and each listed file exists. The nationwide sources/states/INDEX.md that the A–M researcher left for later has been added. Every legislation/ file has a "Date checked" or equivalent field, as CLAUDE.md requires.

4.2 Citations

  • Method. A script split each note into paragraphs, bullets and table rows over about 90 characters, then looked for any citation marker: a link, a numbered or keyed reference ([S12], [N2], [gucci]), a sources/ path, a statute or CFR section, a Federal Register cite, a case name, or an "unverified" label.
  • Result. 1,591 of 4,818 units had no marker. Files with the most: market/2026-10-09-banking.md (127 of 180), legislation/us-kyc-aml-selling-bitcoin.md (76 of 133), notes/2026-10-09-hacks-causes-defenses.md (65 of 278), notes/2026-10-09-technology.md (57), market/2026-10-09-wallets.md (57), market/2026-10-09-payment-processors.md (56), notes/2026-10-09-who-is-satoshi.md (51), legislation/us-states-N-Z-summary.md (51) and market/2026-10-09-link-map.md (50). State notes have 4 to 30 each.
  • What the uncited units are. Spot checks in banking, hacks, Louisiana, KYC/AML and wallets found the same three patterns every time:
  • opening "short version" bullets and summary tables that restate facts cited in the detail sections;
  • timeline tables cited in a "Sources:" block directly underneath (banking § 1.1);
  • regulation rows cited by bare section number, such as "1022.380(c)".

No fabricated or orphan claim turned up in the samples. A full claim-by-claim audit was not done.

4.3 Copyright

  • No copyrighted article, book chapter or transcript is stored as a full copy. A scan for long quotations in the notes found only statute and regulator text, which is public domain, and short attributed quotes from articles.
  • Full copies that are not US public domain, all marked in their indexes and kept because NEXT.md's ground rules allow government and court documents:
  • 8 Europol press releases (sources/darkweb-public-record/). Europol's notice allows private use only, and the index says not to publish or push them.
  • 5 Mt. Gox trustee notices and reports (sources/hacks/).
  • The Ontario Securities Commission's QuadrigaCX review (sources/hacks/).
  • A FINTRAC notices page (sources/payment-processors/).
  • 10 public comments on the 2020 rule (sources/fincen-wallet-rule/comments-2020-docket/).
  • Martti Malmi's side of the Satoshi–Malmi emails (sources/satoshi/).

If the repo ever gets a remote or is shared, these are the files to review first.

4.4 Secrets and privacy

  • Scanned: all text files (md, html, txt, csv, xml, mediawiki) and the extracted text of all 453 PDFs.
  • Searched for: WIF and xprv private keys, PEM keys, cloud and GitHub tokens, "password" or "passcode" with a value, Social Security number patterns, .onion addresses, and the editor's name, email and phone. Nothing found beyond:
  • the BIP specifications' published test vectors. bip-0032.mediawiki, bip-0084.mediawiki and bip-0086.mediawiki contain example extended private keys, and the last two the standard "abandon … about" test mnemonic. These are public examples, not anyone's keys. sources/bips/INDEX.md now says so and says how to remove them if the "no private keys" rule is read strictly.
  • BIP author email addresses, which are public.
  • The Murphy v DHS filing that prints a teleconference passcode was deliberately not saved. The Malmi archive's old passwords are redacted (8 occurrences; checked, none left).
  • The FBI notices list attacker wallet addresses as published by the FBI. These are public addresses, not secrets.

4.5 Layout against the README

  • notes/YYYY-MM-DD-topic.md and market/YYYY-MM-DD-topic.md: followed.
  • legislation/: the README asks for one file per bill, law or rule, named like us-federal-hr-1234.md or wy-sf-0001.md. This research used one file per state (us-state-XX.md) and one per federal topic, as NEXT.md specified. Each state file has a per-bill table with number, status and the date checked. If the README layout is wanted, the bill tables can be split out later.
  • data/ is not described in the README. It holds the link-map CSV.
  • sources/: every topic folder has an INDEX.md with title, issuer, date, URL, retrieval date and file name. sources/primary/ holds the origins primary sources (added in the rerun; see § 1).
  • Not covered at all yet, though the README names them:
  • market data: price history, volume, supply, mining economics, ETFs and institutional holdings. The technology note covers the supply schedule and mining mechanics only.
  • legislation outside the US.

4.6 Repo size and commit

  • About 570 MB on disk: 181 MB already committed in .git and about 390 MB in the working tree.
  • The patents folder is the largest at 112 MB. The largest single file is 18 MB.
  • sources/fincen/ alone is 53 MB, as its researcher noted.
  • The bulk is government PDFs that compress poorly.

5. Fixes made by this check

Each fix rests on a primary document already in the repo or saved by this check, and each is marked in the text as "completeness check".

  1. Coinme multistate settlement: who took part. Saved the order itself: sources/states/ga/GA-DBF-2026-10-07-Coinme-multistate-settlement-agreement-and-consent-order.pdf (Georgia DBF, 26 pp.; robots.txt allows it), indexed in sources/states/ga/INDEX.md. - What the order shows: Appendix A lists 34 agencies: 32 states, DC and Puerto Rico. The money is a $2.2M penalty (per-state shares in Appendix B) plus $0.3M in costs to the seven lead states (Appendix C); a further $4M is due if kiosks are not closed by 2027-01-01 (Appendix D). - Participants: AL, AK, AZ, AR, CO, CT, DE, DC, FL, GA, ID, IL, IA, KS, KY, MD, MN, MS, NE, NM, NV, NC, ND, OH, OK, OR, PA, PR, RI, SC, SD, TN, WA and WV. - Not in the order: CA, HI, IN, LA, ME, MA, MI, MO, MT, NH, NJ, NY, TX, UT, VT, VA, WI and WY. - Files corrected, replacing "unverified" with the fact and its share: the AL, AZ, CA, CO, CT, FL, HI, ID, KY, LA, MD, ME, MN, MS, MT, NE, OK, OR, PA and WA notes, both state summaries, legislation/us-kyc-aml-selling-bitcoin.md and market/2026-10-09-walk-in-bitcoin-shops.md (Nevada's participation). The WA note had said "Washington plus 34 others", and the OR note "35 regulators"; both were wrong.
  2. CLARITY Act (H.R. 3633), Senate status. The Senate rejected cloture on the motion to proceed, 49–50, on 2026-09-15 (Roll Call Vote 234; saved XML and HTML in sources/fincen-wallet-rule/). Updated in market/2026-10-09-wallets.md (2 places) and legislation/us-federal-fincen.md (2 places). Both had said "news only" or "not checked".
  3. 2020 unhosted-wallet NPRM. It was withdrawn as of 2026-10-06 and never finalised (91 FR 63514; saved in sources/fincen/). Fixed in market/2026-10-09-wallets.md (2 places), which had said "unverified".
  4. IRS DeFi broker rule repeal. Public Law 119-5 (H.J. Res. 25, approved 2025-04-10) disapproved 89 FR 106928 (saved in sources/fincen-wallet-rule/). Fixed in legislation/us-federal-fincen.md (2 places), which had said "unverified here".
  5. Which states ban kiosks. The three outright bans, from the enacted texts in the repo, are Indiana (2026-03-09), Tennessee (2026-07-01) and Minnesota (2026-08-01). Connecticut has no ban, and Vermont had a moratorium, not a ban. Resolved the conflict in legislation/us-state-mn.md and added the Tennessee cross-reference to the A–M summary.
  6. KYC/AML note. Indiana HB 1116's effective date (on passage, 2026-03-09) and Hawaii's act number (Act 224, HB 1642 CD1) are now cited to the saved texts. Its gap list was corrected: both texts are saved.
  7. Books note. Its Spark run had been described as unfinished. It has finished, and its contested and rejected items are now summarised in the note's § 5.
  8. Banking note. Its Spark run had been described as queued. It has finished, and its status and two summary points (on Mercury and Chase, and an unverified WSJ survey) are recorded. They are not adopted.
  9. Walk-in shops note. Coinme: Nevada participated. The order defines a kiosk as a "machine", so Coinme Cash checkout counters look outside it. That is our reading, marked unverified.
  10. sources/states/INDEX.md created: the nationwide index of the 51 state folders, with counts and sizes.
  11. sources/bips/INDEX.md: a note that three BIPs contain published test-vector keys (§ 4.4).
  12. Spark pointers. A short closing section was added to the five notes whose Spark runs are not merged: who is Satoshi, patents, hacks, FinCEN wallet rule, and KYC/AML. Each points to § 6 here and names that run's main rejected or wrong items.

6. What the Spark runs rejected

The editor asked on 2026-10-09 for the material that the Spark rejects or labels UNDOCUMENTED to be included and flagged, not dropped. This section holds all of it for the nine bitcoin runs. It comes from each run's report (research report <id>) and from the fleet audit log (research logs). It is Spark output, not checked fact: the Spark's readers are small local models, and several items below are wrong. Bracketed numbers such as [12] point to the source table in that run's own report.

Run Overall Pages read OK / refused / thin / error / never read Sub-answers not CONFIDENT Claims rejected by its verifier Partly supported Facts dropped
Origins 2007–2011 CONFIDENT 46 / 1 / 8 / 2 / 38 0 1 11 2
Who is Satoshi CONFIDENT 48 / 2 / 4 / 2 / 31 6 CONTESTED 0 16 1
Books MIXED 47 / 3 / 11 / 9 / 28 3 CONTESTED 3 15 1
Wallets MIXED 53 / 4 / 18 / 9 / 49 2 UNDOCUMENTED 2 14 3
Patents MIXED 49 / 3 / 9 / 3 / 6 3 UNDOCUMENTED, 1 CONTESTED 1 10 3
Hacks CONFIDENT 54 / 0 / 9 / 5 / 29 1 UNDOCUMENTED 1 14 4
FinCEN wallet rule CONFIDENT 45 / 5 / 4 / 7 / 22 0 0 12 0
KYC/AML for sellers CONFIDENT 42 / 2 / 2 / 1 / 34 0 0 9 0
Banking CONFIDENT 45 / 3 / 2 / 1 / 61 0 0 4 1

6.1 Spark errors this check spotted, checked against the repo

  • Origins.
  • "Martti Malmi … not referenced in any of the provided sources": wrong. The repo holds 144 Satoshi emails to Malmi, 2009–2011 (sources/satoshi/Satoshi-Malmi-emails-2009-2011-archive-mmalmi-github.html; notes/2026-10-09-who-is-satoshi.md [S24]).
  • "Satoshi's message on November 10, 2008, announced the release of Bitcoin v0.1": rejected by its own verifier. The report's own timeline gives v0.1 as 2009-01-08 (unverified here).
  • Who is Satoshi.
  • "COPA (Cryptocurrency Open Platform Association)" is wrong: COPA is the Crypto Open Patent Alliance (see notes/2026-10-09-patents.md).
  • "Liya Gudman" is Leah McGrath Goodman, the Newsweek reporter (Satoshi note [S53]).
  • Le Roux's arrest is given as both "April 2011" and "September 2012" in the same answer. The run flagged this conflict itself.
  • Books. It confused The Bitcoin Standard's reviews with Digital Gold and The Book of Satoshi, and gave Kings of Crypto to Ben Mezrich (it is Jeff John Roberts) and The Blocksize War to Vigna and Casey (it is Jonathan Bier). See notes/2026-10-09-books.md.
  • Wallets.
  • "Coinbase is licensed as a money transmitter in 48 U.S. states, including … Montana" was rejected by its own verifier. Montana does not license money transmitters at all (legislation/us-state-mt.md).
  • Its two UNDOCUMENTED answers are covered in the wallets note:
    • US regulatory status of hardware wallets: under FinCEN FIN-2019-G001 § 4.5.1(b), hardware and software suppliers are "engaged in trade and not money transmission";
    • Ballet: covered, with its own gaps (§ 7.3).
  • Hacks. It labels the cause of Ledger's 2020 data breach UNDOCUMENTED. The hacks note documents it: an e-commerce and marketing database reached through an API key, plus insiders at a Shopify contractor (notes/2026-10-09-hacks-causes-defenses.md, incident table and § 3.1).
  • Patents.
  • It attributed US20160292672A1 / US11200564B2 to Block and to Bank of America. Its own evidence shows the assignee as Nasdaq Inc.
  • Its UNDOCUMENTED answers for nChain, Coinbase and Bank of America are wrong. The repo holds granted patents for all three in sources/patents/: nChain/Wright US10652014B2, US10659223B2, US11120437B2 and US12032677B2; Coinbase US9735958B2, US10510053B2, US10755241B2, US10903991B1 and US12063291B2; Bank of America US10255600B2, US10275772B2 and the application US20150262173A1.
  • The "53 Bank of America blockchain patents" figure is unverified.
  • Ledger's patents remain undocumented here too (notes/2026-10-09-patents.md § 4.3).
  • FinCEN wallet rule. Its "judgement" list doubts whether the withdrawal was in 2026. It was: 91 FR 63514, 2026-10-06, saved.

6.2 Origins: the Spark findings (now checked line by line in notes/2026-10-09-origins-timeline.md § 9)

The run's summary claims, each with its status against this repo:

Claim Status here
Whitepaper posted 2008-10-31 to the Cryptography (metzdowd) mailing list Confirmed: COPA judgment ¶23.4 via the Satoshi note
Genesis block 2009-01-03 18:15:05 UTC, with "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks" Confirmed: technology note [S6]; Satoshi note [S1 ¶23.6]
v0.1 released 2009-01-08 Unverified here
First transaction, 10 BTC to Hal Finney in block 170, 2009-01-12 Confirmed: COPA judgment ¶23.8 via the Satoshi note
Martti Malmi's 2009-10-12 sale of 5,050 BTC for $5.02, the "first documented price" Unverified here; Spark sources are CoinMarketCap, bitcoin.com and gamblineers.com
Laszlo Hanyecz's pizza purchase, 10,000 BTC, 2010-05-22 Unverified here
Parity with the US dollar, 2011-02-09 Unverified here
Last BitcoinTalk post 2010-12-12 (denial-of-service protections) Unverified here; Spark source is Grokipedia
Andresen announced a more active role 2010-12-19 Unverified here
Emails to Mike Hearn (2011-04-23: "I've moved on to other things") and to Gavin Andresen (2011-04-26) Partly: the Satoshi note has the Hearn email as Reported via Wikipedia and a WSJ review; the dates are unverified here
Andresen named lead maintainer in 2010 and founded the Bitcoin Foundation in 2012 Unverified here; the Foundation date was a fact the Spark itself dropped

The run's per-run detail is below.

6.3 Per-run detail

Origins 2007–2011: 20261009-143628--what-is-documented-about-the-origins-of-bitcoin-from-2007-to

Finished 2026-10-09T22:26:09Z. Overall confidence CONFIDENT. Topic note: none: the origins researcher was blocked, so this report is the only origins material in the repo. Full report: research report 20261009-143628--what-is-documented-about-the-origins-of-bitcoin-from-2007-to.

Claims its own verifier rejected ("not supported by the cited evidence"):

  • ✗ Satoshi's message on November 10, 2008, announced the release of Bitcoin v0.1 — The evidence does not contain a message from Satoshi on November 10, 2008, announcing the release of Bitcoin v0.1.

Claims its verifier found only partly supported (11; text cut off by the report at about 160 characters):

  • ~ The whitepaper, titled "Bitcoin: A Peer-to-Peer Electronic Cash System," was posted on a cryptography mailing list by Satoshi Nakamoto
  • ~ One source [3] claims the publication date as January 3, 2009, which is the date Bitcoin software was released, not the whitepaper
  • ~ The whitepaper's publication date is consistently cited as October 31, 2008, though the specific mailing list or platform is not identified in the evidence
  • ~ Primary sources for Satoshi Nakamoto's early communications before the whitepaper include emails with Adam Back, Wei Dai, and Hal Finney, as well as messages on
  • ~ The GitHub repository lists emails between Satoshi and Adam Back (3 emails), Satoshi and Wei Dai (2 emails), and Satoshi and Hal Finney (18 emails)
  • ~ The Cryptography Mailing List archives contain Satoshi's messages dated from 2008-11-01 to 2009-01-25, including discussions on Bitcoin's development and POW to
  • ~ The final public communication on the Bitcointalk forum occurred on December 12, 2010, regarding denial-of-service protections
  • ~ Nakamoto's last verified email to Gavin Andresen was sent on April 26, 2011, confirming the handover and cessation of involvement
  • ~ Gavin Andresen announced taking a more active role on December 19, 2010, with Satoshi's blessing
  • ~ Gavin Andresen's GitHub commits are documented as primary evidence of his contributions
  • ~ Craig Steven Wright has claimed to be Satoshi Nakamoto, registering US copyright for the whitepaper and code in April 2019

Facts dropped before the report was written (audit log, facts_dropped_detail):

  • "Emails between Satoshi and Hal Finney are available." (page: https://github.com/lugaxker/nakamoto-archive; dropped because its supporting quote was not found word-for-word on the page)
  • "Gavin Andresen founded the Bitcoin Foundation in 2012." (page: https://notablepeopleproject.org/gavin_andresen; dropped because its supporting quote was not found word-for-word on the page)

Pages refused, failed or skipped:

  • Refused (robots.txt or DNS failure) (1): https://motherboard.vice.com/en_us/article/7xx9gb/former-bitcoin-developer-shares-early-satoshi-nakamoto-emails (dns failure for 'motherboard.vice.com': [Errno -2] Name or service not known)
  • Skipped as low relevance (8): https://github.com/cryptoanarchywiki/mailing-list-archive (score 0.11); https://finance.yahoo.com/quote/BTC-USD?fr=sycsrp_catchall (score 0.11); https://finance.yahoo.com/quote/BTC-USD (score 0.11); https://satoshi.nakamotoinstitute.org/emails/cryptography (score 0.0); https://satoshi.nakamotoinstitute.org/emails/threads (score 0.0); https://www.bitperia.cz/clanek/the-bitcoin-whitepaper-cz-cesky-preklad (score 0.25); https://www.coinbase.com/learn/crypto-basics/bitcoin-whitepaper-simplified-for-everyone (score 0.25); https://cryptosvet.cz/bitcoin-whitepaper-tentokrat-sa-o-copyright-snazi-zena-z-ciny (score 0.12)

  • Fallback browser failed (2): https://mailing-list-archive.cryptoanarchy.wiki/archive (browser: rendered, but only 387 characters of text); https://www.forbes.com/sites/digital-assets/2026/03/26/who-is-satoshi-nakamoto-coinbase-ceo-reveals-he-now-thinks-he-knows-the-answer-to-the-massive-bitcoin-mystery (browser: rendered, but only 0 characters of text)

  • Search stage: 128 candidate results came back across 8 searches. Those not taken were passed over because of per-domain caps or the page budget. Passed-over results named in the log: https://coinguides.org/satoshi; https://coinmarketcap.com/academy/article/bitcoin-whitepaper-simplified-for-everyone; https://coinmarketcap.com/currencies/bitcoin; https://cryptonews.com/academy/who-is-satoshi-nakamoto; https://en.bitcoin.it/wiki/Category:History; https://en.wikibooks.org/wiki/Information_Technology_and_Ethics/Cryptocurrency_Overview; https://en.wikibooks.org/wiki/Intellectual_Property_and_the_Internet/Print_version; https://en.wikibooks.org/wiki/Perspectives_in_Digital_Culture/Web_as_Public_and_Private_Space; https://en.wikibooks.org/wiki/Technical_Analysis/Psychology_And_Markets; https://en.wikipedia.org/wiki/Bitcoin; https://en.wikipedia.org/wiki/Craig%20Steven%20Wright; https://en.wikipedia.org/wiki/Hal%20Finney%20%28computer%20scientist%29; https://en.wikipedia.org/wiki/History%20of%20bitcoin; https://en.wikipedia.org/wiki/Money%20Electric%3A%20The%20Bitcoin%20Mystery; https://en.wikipedia.org/wiki/Proof%20of%20work; https://en.wikipedia.org/wiki/Satoshi%20Nakamoto; https://finance.yahoo.com/quote/BTC-USD; https://finance.yahoo.com/quote/BTC-USD?fr=sycsrp_catchall; https://www.bestbrokers.com/bitcoin-trading/bitcoin-price-history; https://www.cointracker.com/blog/bitcoin-price-history; https://www.forbes.com/sites/digital-assets/2026/03/26/who-is-satoshi-nakamoto-coinbase-ceo-reveals-he-now-thinks-he-knows-the-answer-to-the-massive-bitcoin-mystery; https://www.kraken.com/learn/bitcoin-halving-history

Its "What still needs judgement" list:

  1. Verify if the Cryptography Mailing List was a direct successor to the Cypherpunks mailing list
  2. Confirm Martti Malmi's role in Bitcoin's initial development
  3. Verify the exact mailing list where the whitepaper was first published
  4. Confirm the content of Satoshi's emails with Adam Back, Wei Dai, and Hal Finney beyond the counts provided
  5. Verify the initial reception of the Bitcoin whitepaper beyond publication context and speculation about authorship
  • 5 further pages were read but yielded no cited evidence.

Who is Satoshi: 20261009-143633--who-is-satoshi-nakamoto-survey-every-serious-candidate-hal-f

Finished 2026-10-09T22:50:59Z. Overall confidence CONFIDENT. Topic note: notes/2026-10-09-who-is-satoshi.md (Spark material not yet merged). Full report: research report 20261009-143633--who-is-satoshi-nakamoto-survey-every-serious-candidate-hal-f.

Sub-answers labelled CONTESTED or UNDOCUMENTED, with what the run said (Spark output, not checked line by line; see the topic note for the checked version):

  • CONTESTED · certainty 6/10: What evidence supports Hal Finney as Satoshi Nakamoto?

    Hal Finney received the first recorded Bitcoin transaction from Satoshi Nakamoto on January 12, 2009, when Satoshi sent him 10 bitcoins [18, 3, 14, 7, 35, 25]. Finney was a respected cryptographer and early Bitcoin collaborator who downloaded the software the day it was released [18, 7]. He assisted with debugging Bitcoin's initial code releases [35] and launched the first Bitcoin home node one week after the network launch [7]. Finney's prior work on reusable proof-of-work systems in 2004 [35] and his proximity to Bitcoin's launch fueled speculation about his potential role as Satoshi [35]. However, Finney explicitly denied being Satoshi before his death in 2014 [7, 35]. Multiple sources confirm he was not considered Satoshi, including a statement from Grokipedia noting 'Hal Finney was not considered to be Satoshi Nakamoto' [35]. Finney lived near Dorian Nakamoto, which fueled theories of collaboration or pseudonym use [35], but these remain speculative. The evidence does not confirm Finney's authorship of Bitcoin's whitepaper or his role in creating the core protocol beyond the initial transaction and debugging [35]. Gaps it named: whether Finney's prior work on reusable proof-of-work systems directly influenced Bitcoin's design; if Finney's denial of being Satoshi was definitive or if he was being discreet; whether Finney's collaboration with Nick Szabo (per Jaime Núñez) was factual or speculative

  • CONTESTED · certainty 6/10: What evidence supports Adam Back as Satoshi Nakamoto?

    The evidence suggests Adam Back may be Satoshi Nakamoto based on several points. John Carreyrou, a Pulitzer Prize-winning investigative reporter for the New York Times, suspects Back after watching the 2024 HBO documentary Money Electric, noting Back's discomfort when mentioned as a suspect [23]. Back invented Hashcash, a proof-of-work system later used in Bitcoin mining, which Satoshi referenced in the Bitcoin whitepaper [23, 10]. Back also outlined Bitcoin's core features in 1997 and 1999 posts, including a distributed e-cash system with inflation control [23]. Linguistic analysis by Carreyrou found Back matched Satoshi's writing quirks, such as double spaces, mixed British/American spellings, and idiosyncratic hyphenation [23]. The New York Times investigation and HBO documentary Money Electric identified Back as the principal suspect [28]. However, Back denies the claim, stating the evidence is "a combination of coincidence and similar phrases from people with similar experience and interests" [11]. The Wikipedia entry confirms Back was the only person named in the Bitcoin whitepaper's body and his writing style resembles Nakamoto's [28]. The evidence does not confirm Back is Satoshi, as he denies it and the analysis relies on circumstantial evidence. The claim that Back was "the best match" in Carreyrou's AI analysis [11] is presented, but the analysis itself is not independently verified. Gaps it named: Whether Back's linguistic matches are statistically significant; Whether the Hashcash reference in the whitepaper is sufficient to prove authorship; Whether Back's 1997-1999 posts were widely known at the time of Bitcoin's launch

  • CONTESTED · certainty 6/10: What evidence supports Dorian Nakamoto as Satoshi Nakamoto?

    The evidence supporting Dorian Nakamoto as Satoshi Nakamoto includes several claims from various sources. According to Forbes [31], Dorian Nakamoto's response to a Newsweek journalist stated, "I am no longer involved in that and I cannot discuss it. It's been turned over to other people. They are in charge of it now. I no longer have any connection," which was confirmed by Captain Michael Parker of the Temple Sheriff's Station [31]. The Bitcoin Wiki [5] notes that Newsweek journalist Liya Gudman published an investigation in March 2014 suggesting Dorian Prentis Satoshi Nakamoto was the creator of Bitcoin, though Dorian denied being the creator and stated he had only heard about Bitcoin three weeks prior to the article's publication [5]. The CoinMarketCap article [8] mentions that Dorian Nakamoto's name is similar to Satoshi Nakamoto, noting that "Dorian Nakamoto was born Satoshi Nakamoto and then added 'Dorian Prentice' to his name in his twenties" [8]. It also claims Dorian's writing style matches Satoshi's, as he used both English and American spellings [8], and his career timeline aligns with Bitcoin's creation, as his career "took a dive in the early 2000’s, so he would have had the bandwidth necessary to work on Bitcoin during the appropriate time" [8]. However, the Wikipedia entry [24] states that Andreas Antonopoulos organized a fundraising campaign for Dorian Nakamoto after the Newsweek article identified him as Satoshi, and the Grokipedia [35] notes that Dorian was "speculated to be Satoshi Nakamoto" but not confirmed. Patrick Juola's analysis [26] suggested Neal J. King was a more likely candidate than Dorian Nakamoto. The evidence does not confirm Dorian Nakamoto's identity as Satoshi Nakamoto, as he denied being the creator [5], and the claims are largely speculative or based on circumstantial similarities. The evidence includes a quote from Dorian that was interpreted as an admission but was actually a denial of involvement [31, 8]. Gaps it named: Dorian Nakamoto's actual identity as Satoshi Nakamoto is not confirmed; The claim that Dorian Nakamoto was born Satoshi Nakamoto is not verified; The analysis suggesting Neal J. King was a more likely candidate contradicts the Dorian Nakamoto theory

  • CONTESTED · certainty 6/10: What evidence supports Craig Wright as Satoshi Nakamoto?

    The evidence indicates that Craig Wright has repeatedly claimed to be Satoshi Nakamoto, supported by several specific assertions. Wright allegedly used the email address [email protected] in January 2014, which he claimed was the same as Satoshi's early Bitcoin development email [19]. He reportedly attempted to contact an Australian senator using this email address [19], and stated he had been 'running bitcoin since 2009' [19]. Wright also claimed to have asked Dave Kleiman to edit a Bitcoin paper months before the whitepaper's November 2008 publication [19], and his January 10, 2009, blog post mentioned Bitcoin before its launch [19]. However, multiple sources challenge these claims. COPA (Cryptocurrency Open Platform Association) presented evidence showing Wright's documentation was largely inauthentic or forged [15], including metadata analysis revealing Wright's Bitcoin White Paper was written in OpenOffice, not LaTeX as claimed [20]. Experts found the 'time capsule' file was edited in September 2023 [20], and a deleted file suggested Chat GPT was used to fabricate evidence [20]. Wikipedia confirms Wright has claimed since 2015 to be Satoshi Nakamoto [27], and he led the creation of Bitcoin Satoshi Vision in 2018 [27]. Despite Wright's claims, the evidence primarily demonstrates his assertions rather than supporting proof of his identity as Satoshi Nakamoto. Gaps it named: Whether Wright's claims were made in a legally binding context; Whether the email address [email protected] was definitively used by Satoshi Nakamoto; Whether the metadata analysis conclusively proves the whitepaper was not written by Satoshi Nakamoto

  • CONTESTED · certainty 6/10: What evidence supports Peter Todd as Satoshi Nakamoto?

    The evidence supporting Peter Todd as Satoshi Nakamoto primarily comes from the 2024 HBO documentary Money Electric: The Bitcoin Mystery by Cullen Hoback. According to the documentary, Todd was named as a candidate for Satoshi Nakamoto [32], with Hoback presenting circumstantial evidence including Todd's early involvement in Bitcoin development [32][38]. The documentary notes that Todd corrected a technicality in one of Satoshi's last posts shortly after joining the Bitcoin forum in 2010, then disappeared online alongside Satoshi [34]. Hoback also highlights Todd's alleged use of an alternate persona for a 'Replace by Fee' patch, suggesting a pattern of behavior consistent with Satoshi's anonymity [34]. The documentary claims Todd made statements like 'Jsem Satoshi, stejně jako všichni ostatní' ('I am Satoshi, just like everyone else') [38], though Todd publicly denied being Satoshi, calling the theory 'ludicrous' [32][34][36] and criticizing Hoback's approach as 'QAnon style coincidence-based conspiracy thinking' [32]. Despite these claims, the evidence states that 'no concrete evidence has been presented to support the claim, and the theory remains entirely speculative' [32]. Todd also denied being Satoshi in a CNN statement [36] and in the documentary [32]. The documentary's main evidence includes a forum thread from December 2010 where Todd appears to 'finish Satoshi's sentences' [12]. Gaps it named: Whether Todd's forum interaction in December 2010 is evidence of Satoshi's identity; Whether Todd's alleged alternate persona for the 'Replace by Fee' patch is verified; Whether Todd's statement 'Jsem Satoshi' was made in a context supporting the theory

  • CONTESTED · certainty 6/10: What evidence supports Paul Le Roux as Satoshi Nakamoto?

    The evidence presents both claims supporting and refuting Paul Le Roux as Satoshi Nakamoto. Proponents cite Le Roux's arrest timeline: "Le Roux was arrested less than a year after Satoshi disappeared, in April 2011" [16], though this conflicts with [22] stating Satoshi's last message was in April 2011 and Le Roux was arrested in September 2012. Le Roux's technical background is noted: "Le Roux has extensive programming experience as well as work experience in cryptography – possibly for GCHQ" [16], and his E4M encryption software launch mirrored Bitcoin's approach: "The way he announced and then launched it was remarkably similar to the way Satoshi launched Bitcoin" [16]. He also developed gambling software during Bitcoin's early period [16] and mentioned interest in Bitcoin mining hardware [16]. However, counter-evidence from [22] states Le Roux was "fully occupied running RX Limited, his illegal pharmacy network" during Bitcoin's development (2008-2011), contradicting the timeline. His character is contrasted: Satoshi is described as "humble, idealistic, focused on decentralization" while Le Roux is "violent criminal, profit-driven, centralized control" [22]. Le Roux's letter to Judge Abrams showed "limited technical understanding of Bitcoin" [22], and he denied involvement with TrueCrypt despite E4M's connection to it [33]. The Wikipedia entry notes he "denied developing TrueCrypt in a court hearing" [33], though E4M's release in 1998 [33] aligns with the claim that his software launch method resembled Bitcoin's [16]. Gaps it named: The exact timeline of Le Roux's arrest relative to Satoshi's disappearance; Whether Le Roux's E4M software was directly connected to Bitcoin's development; The validity of the claim that Le Roux was developing gambling software during Bitcoin's critical period; Whether Le Roux's technical understanding of Bitcoin was sufficient to develop it

Claims its verifier found only partly supported (16; text cut off by the report at about 160 characters):

  • ~ Nick Szabo is cited as a leading candidate due to stylistic similarities between his writing and Satoshi's whitepaper
  • ~ Nick Szabo's Bit Gold project anticipated Bitcoin's core concepts
  • ~ Finney downloaded the software the day it was released
  • ~ Nick Szabo's 1998 'bit gold' proposal for a decentralized digital currency mimicked the security and trust characteristics of gold without a central authority
  • ~ The Bitcoin whitepaper references 'bit gold' as an influence
  • ~ Szabo's academic background in computer science and cryptography aligns with Satoshi's presumed expertise
  • ~ Writing style analysis shows an 'excellent match' between Szabo's blog posts and the whitepaper, including unusual phrases like 'of course' without isolating co
  • ~ John Carreyrou, a Pulitzer Prize-winning investigative reporter for the New York Times, suspects Back after watching the 2024 HBO documentary Money Electric,
  • ~ Captain Michael Parker of the Temple Sheriff's Station confirmed Dorian Nakamoto's response
  • ~ Newsweek journalist Liya Gudman published an investigation in March 2014 suggesting Dorian Prentis Satoshi Nakamoto was the creator of Bitcoin
  • ~ Dorian denied being the creator and stated he had only heard about Bitcoin three weeks prior to the article's publication
  • ~ Craig Wright used the email address [email protected] in January 2014
  • ~ Wright claimed the email address [email protected] was Satoshi's early Bitcoin development email
  • ~ The evidence supporting Peter Todd as Satoshi Nakamoto primarily comes from the 2024 HBO documentary Money Electric: The Bitcoin Mystery by Cullen Hoback
  • ~ Todd disappeared online alongside Satoshi
  • ~ Le Roux was arrested less than a year after Satoshi disappeared, in April 2011

Facts dropped before the report was written (audit log, facts_dropped_detail):

  • "The judgment discusses evidence against Wright's claim to be Satoshi Nakamoto." (page: https://www.judiciary.uk/wp-content/uploads/2024/05/COPA-v-Wright-Judgment.pdf; dropped because its supporting quote was not found word-for-word on the page)

Pages refused, failed or skipped:

  • Refused (robots.txt or DNS failure) (2): https://finwaveanalytics.com/Others/961.html (robots.txt unreachable (5xx/network) -- RFC 9309 says disallow); https://www.investinblockchain.com/new-evidence-suggests-satoshi-nakamoto-is-paul-solotshi-the-creator-of-encryption-software-e4m-and-truecrypt (robots.txt unreachable (5xx/network) -- RFC 9309 says disallow)
  • Skipped as low relevance (4): https://cryptosvet.cz/satoshi-nakamoto-je-mozno-kriminalnik-paul-le-roux (score 0.25); https://play.google.com/store/info/name/Craig_Wright?id=11vhy89t86 (score 0.14); https://www.kryptonovinky.cz/adam-back-peter-todd-neni-satoshi-nakamoto (score 0.14); https://www.kryptonovinky.cz/peter-todd-kvuli-dokumentu-o-bitcoinu-se-musim-skryvat (score 0.14)
  • Fallback browser failed (4): http://www.forbes.com/sites/kashmirhill/2014/03/07/more-details-on-newsweek-journalists-interview-with-alleged-bitcoin-creator (browser: rendered, but only 0 characters of text); https://drbitcoinpod.com/2024/02/04/copa-vs-craig-wright-part-5 (browser: rendered, but only 301 characters of text); http://www.economist.com/news/briefings/21698066-onus-on-craig-wright-provide-better-evidence-satoshi-nakamoto (browser: rendered, but only 0 characters of text); https://www.alza.cz/satoshi-nakamoto (browser: Refused: still a bot check after 15s (first answer 403, title 'Just a moment...'))

  • Wayback fallback failed (1): http://www.economist.com/news/briefings/21698066-onus-on-craig-wright-provide-better-evidence-satoshi-nakamoto (wayback: the captured copy has too little text)

  • Search stage: 111 candidate results came back across 8 searches. Those not taken were passed over because of per-domain caps or the page budget. Passed-over results named in the log: https://cryptonews.com/academy/who-is-satoshi-nakamoto; https://en.wikipedia.org/wiki/Adam%20Back; https://en.wikipedia.org/wiki/Craig%20Steven%20Wright; https://en.wikipedia.org/wiki/Cryptocurrency; https://en.wikipedia.org/wiki/Europeans%20in%20China%20during%20the%20Middle%20Ages; https://en.wikipedia.org/wiki/Evan%20Ratliff; https://en.wikipedia.org/wiki/History%20of%20bitcoin; https://en.wikipedia.org/wiki/Leah%20McGrath%20Goodman; https://en.wikipedia.org/wiki/Money%20Electric%3A%20The%20Bitcoin%20Mystery; https://en.wikipedia.org/wiki/Satoshi%20Nakamoto; https://en.wikipedia.org/wiki/Timeline%20of%20historic%20inventions; https://en.wikipedia.org/wiki/Yuezhi; https://grokipedia.com/page/Satoshi_Nakamoto; https://www.judiciary.uk/wp-content/uploads/2024/05/COPA-v-Wright-Judgment.pdf; https://www.opencrypto.org/2024-03-14-Justice-Mellor-Rules-That-Craig-Wright-Is-Not-Satoshi-Nakamoto-in-COPA-v-Wright-Trial; https://www.opencrypto.org/2024-05-20-update-written; https://www.opencrypto.org/page2

Its "What still needs judgement" list:

  1. Verify the 2024 UK High Court judgment's ruling on Craig Wright's claim
  2. Confirm whether Nick Szabo's 2005 'bit gold' proposal aligns with his 1998 work
  3. Check if Peter Todd's 'Jsem Satoshi' statement was made in a context supporting the theory
  4. Validate the timeline of Paul Le Roux's arrest relative to Satoshi's disappearance
  5. Confirm the accuracy of the Patoshi mining pattern's connection to Satoshi
  • 9 further pages were read but yielded no cited evidence.

Books: 20261009-143638--what-are-the-best-regarded-books-about-bitcoin-s-history-and

Finished 2026-10-09T23:13:20Z. Overall confidence MIXED. Topic note: notes/2026-10-09-books.md (merged in its § 5). Full report: research report 20261009-143638--what-are-the-best-regarded-books-about-bitcoin-s-history-and.

Sub-answers labelled CONTESTED or UNDOCUMENTED, with what the run said (Spark output, not checked line by line; see the topic note for the checked version):

  • CONTESTED · certainty 4/10: How do reviewers rate Digital Gold's reliability as a historical account?

    Reviewers rate Digital Gold's reliability as a historical account as unreliable. One reviewer, Tim, criticizes the book's historical account, stating that "Particularly the middle, the idea of the gold standard's elimination killing art, literature, innovation, etc, etc was laughable" and questions the claim that "no great (unique) technological innovations happened after 1913" [9]. The book has an overall rating of 4.6 stars based on 22 reviews on Google Play [13], but this rating does not address the reliability of its historical account. The evidence does not provide a comprehensive assessment of the book's reliability as a historical account beyond Tim's criticism. Gaps it named: The overall reliability of Digital Gold as a historical account is not fully established by the evidence.; The evidence does not provide a consensus among reviewers on the book's historical reliability.

  • CONTESTED · certainty 4/10: How do reviewers rate The Book of Satoshi's reliability as a historical account?

    Reviewers on Goodreads rate The Book of Satoshi (though the evidence references The Bitcoin Standard by Saifedean Ammous) as a polemic favoring Austrian economics over Keynesianism, with some noting its enthusiasm for Bitcoin leads to repetition and loss of nuance [9]. The book is recommended for readers interested in the historical function and origins of money, despite not offering a technical explanation of Bitcoin [9]. However, critics argue it devotes only about 25% of its content to Bitcoin itself, focusing instead on economic theory [9]. The evidence does not clarify whether these reviews are from academic historians or general readers, nor does it specify if the book's historical accuracy regarding Satoshi Nakamoto is assessed. The evidence also does not address how reviewers rate the book's reliability as a historical account of Satoshi's work or Bitcoin's origins, as the focus is on economic framing rather than historical fidelity. [9] The book is seen as a polemic in favor of the Austrian School of Economics and against Keynesianism. [9] The book is criticized for being repetitive and losing nuance due to its enthusiasm for Bitcoin. [9] The book is recommended for those interested in the function and origins of money, despite not being a technical explanation of Bitcoin. [9] The book is criticized for focusing more on Austrian economics and critiques of Keynesianism than on Bitcoin itself. Gaps it named: whether reviewers rate the book's reliability as a historical account; if the book's historical accuracy regarding Satoshi Nakamoto is assessed; the distinction between The Book of Satoshi and The Bitcoin Standard

  • CONTESTED · certainty 6/10: How do reviewers rate The Bitcoin Standard's reliability as a historical account?

    Reviewers have mixed opinions on The Bitcoin Standard's reliability as a historical account. Some criticize it for ideological bias, lack of objectivity, and excessive focus on Austrian economics over Keynesianism [9]. For instance, one reviewer notes the author 'uses partial data to make a point' and 'applies his own opinion on what is valuable to society' [9], while another calls it a 'polemic' that 'discredits ideas by trying to discredit the people behind it' [9]. Critics also argue the book exaggerates the impact of monetary systems on society, stating 'Surely, there were many other factors at play beyond just the monetary standards of the time' [9], and lacks technical depth on Bitcoin, with one reviewer noting the author 'could show how bitcoin addresses the critical issues of money' [9]. However, some praise its historical account of money, with one reviewer calling the first part 'fantástica' [9] and another stating it 'covers gold, history of money, economics, central banking' [9]. A few reviewers appreciate its clarity of thought and historical context, though one acknowledges it is 'repetitive' and 'loses nuance in its enthusiasm for Bitcoin' [9]. Overall, the book is seen as a polemic favoring the Austrian School, with mixed reception on its historical reliability. Gaps it named: The extent to which the book's historical account is considered reliable by academic historians; The specific historical claims that are disputed or supported; The proportion of reviewers who find it reliable versus unreliable

Claims its own verifier rejected ("not supported by the cited evidence"):

  • ✗ Reviewers rate Digital Gold's reliability as a historical account as unreliable. — None of the evidence lines address the reliability of Digital Gold as a historical account.
  • ✗ This rating does not address the reliability of its historical account. — None of the evidence lines address the reliability of the historical account.
  • ✗ The book is recommended for readers interested in the historical function and origins of money — The evidence does not mention the historical function and origins of money.

Claims its verifier found only partly supported (15; text cut off by the report at about 160 characters):

  • ~ Digital Gold by Nathaniel Popper is a book published in May 2016 by HarperCollins
  • ~ The book explains the blockchain technology, describing how it distributes ledgers across thousands of nodes to enable transactions without intermediaries
  • ~ The book highlights Bitcoin's potential to serve the 2.5 billion unbanked individuals worldwide, including case studies like Parisa Ahmadi, an Afghan woman with
  • ~ Kings of Crypto by Ben Mezrich chronicles the rise of cryptocurrency exchange Coinbase from its origins as a Y Combinator startup to becoming a 'pillar of the l
  • ~ The book presents cryptocurrency's origins and its transformative impact on money, described as 'the surprising story of the origins of cryptocurrency and how i
  • ~ Proposed solutions included Bitcoin XT, SegWit, and Bitcoin Cash
  • ~ The debate ultimately led to the adoption of SegWit, which raised the block limit without a hard fork, and the creation of Bitcoin Cash
  • ~ The Bitcoin Standard by Saifedean Ammous is a 2018 book published by John Wiley & Sons (though later editions by Braiins Publishing)
  • ~ The book explores the history of money from primitive systems like seashells, cattle, salt, and beads to modern government debt
  • ~ The book explains what constitutes 'sound money' and argues that Bitcoin represents a decentralized, digital solution to money's historical problems, accessible
  • ~ The book has an overall rating of 4.6 stars based on 22 reviews on Google Play
  • ~ Reviewers on Goodreads rate The Book of Satoshi as a polemic favoring Austrian economics over Keynesianism
  • ~ Reviewers on Goodreads note its enthusiasm for Bitcoin leads to repetition and loss of nuance
  • ~ Reviewers have mixed opinions on The Bitcoin Standard's reliability as a historical account.
  • ~ Some criticize it for ideological bias, lack of objectivity, and excessive focus on Austrian economics over Keynesianism.

Facts dropped before the report was written (audit log, facts_dropped_detail):

  • "The book is praised for its historical account of money and its evolution." (page: https://www.goodreads.com/book/show/36448501-the-bitcoin-standard; dropped because its supporting quote was not found word-for-word on the page)

  • A second-look pass proposed UNDOCUMENTED (certainty 2) for one sub-answer. That was rejected and the first answer kept (CONFIDENT, certainty 6).

  • One sub-question was replanned to: What is the scope and content of The Age of Cryptocurrency by Paul Vigna and Michael Casey?

Pages refused, failed or skipped:

  • Skipped as low relevance (11): https://play.google.com/store/books/details?id=mYgWEQAAQBAJ (score 0.25); https://en.wikibooks.org/wiki/Mirad_Lexicon/Mirad-English-B (score 0.25); https://finance.yahoo.com/quote/BTC-USD?fr=sycsrp_catchall (score 0.17); https://finance.yahoo.com/quote/BTC-USD (score 0.17); https://play.google.com/store/audiobooks/series?id=G1NVHAAAABhPRM (score 0.12); https://www.cnbc.com/2021/06/07/bitcoin-2021-elon-musk-jack-dorsey-winklevoss-twins-key-highlights.html (score 0.17); https://www.ctu.to/kniha/digitalni-zlato (score 0.12); https://www.ledger.com/academy/topics/crypto/when-was-bitcoin-invented (score 0.12); https://en.bitcoin.it/wiki/Main_Page (score 0.17); https://en.wikipedia.org/wiki/Bitcoin%20Satoshi%20Vision (score 0.25); https://www.cointracker.com/blog/who-created-bitcoin (score 0.25)
  • Refused (robots.txt or DNS failure) (3): https://www.linkedin.com/top-content/finance/bitcoin-and-financial-systems/evaluating-bitcoin-value-amid-economic-debt-cycles (robots.txt disallows this path); https://www.linkedin.com/in/bitcoinliquidity (robots.txt disallows this path); https://us.macmillan.com/books/9781250081551/theageofcryptocurrency (robots.txt disallows this path)
  • Fallback browser failed (9): https://allegro.cz/produkt/digital-gold-nathaniel-popper-cf6d7b6f-1a02-46a0-b2c3-4a9488792aa0 (browser: rendered, but only 0 characters of text); https://www.alza.cz/media/bitcoinovy-standard-d7483568.htm (browser: Refused: still a bot check after 15s (first answer 403, title 'Just a moment...')); https://www.nejlevnejsi-knihy.cz/kniha/digital-gold-2881125.html (browser: Refused: still a bot check after 15s (first answer 403, title 'Just a moment...')); https://cizojazycne-knihy.heureka.cz/digital-gold-nathaniel-popper (browser: Refused: still a bot check after 15s (first answer 403, title 'Just a moment...')); https://www.nejlevnejsi-knihy.cz/kniha/bitcoin-standard.html (browser: Refused: still a bot check after 15s (first answer 403, title 'Just a moment...')); https://www.megaknihy.cz/podnikani/20220361-the-bitcoin-standard.html (browser: rendered, but only 284 characters of text); https://www.megaknihy.cz/sport/1162037-standard-bitcoina.html (browser: rendered, but only 284 characters of text); https://cizojazycne-knihy.heureka.cz/cryptocurrency-paul-vigna (browser: Refused: still a bot check after 15s (first answer 403, title 'Just a moment...')); https://www.nejlevnejsi-knihy.cz/kniha/digital-currencies-unlocking-the-secret.html (browser: Refused: still a bot check after 15s (first answer 403, title 'Just a moment...'))

  • Wayback fallback failed (5): https://allegro.cz/produkt/digital-gold-nathaniel-popper-cf6d7b6f-1a02-46a0-b2c3-4a9488792aa0 (wayback: no captured copy of this page); https://www.nejlevnejsi-knihy.cz/kniha/digital-gold-2881125.html (wayback: no captured copy of this page); https://cizojazycne-knihy.heureka.cz/digital-gold-nathaniel-popper (wayback: no captured copy of this page); https://cizojazycne-knihy.heureka.cz/cryptocurrency-paul-vigna (wayback: no captured copy of this page); https://www.nejlevnejsi-knihy.cz/kniha/digital-currencies-unlocking-the-secret.html (wayback: no captured copy of this page)

  • Search stage: 151 candidate results came back across 9 searches. Those not taken were passed over because of per-domain caps or the page budget. Passed-over results named in the log: https://99bitcoins.com/cryptocurrency/bitcoin/historical-price; https://allegro.cz/produkt/digital-gold-nathaniel-popper-cf6d7b6f-1a02-46a0-b2c3-4a9488792aa0; https://archive.org/details/the-age-of-cryptocurrency-how-bitcoin-and-digital-money-are-challenging-the-global-economic-order; https://cdn.bookey.app/files/pdf/book/en/the-age-cryptocurrency.pdf; https://en.wikibooks.org/wiki/Cultural_Anthropology/Print_version; https://en.wikibooks.org/wiki/Cultural_Anthropology/Production%2C_Inequality_and_Development; https://en.wikibooks.org/wiki/Information_Technology_and_Ethics/Cryptocurrency_Overview; https://en.wikibooks.org/wiki/Intellectual_Property_and_the_Internet/Print_version; https://en.wikibooks.org/wiki/Introduction_to_Computer_Information_Systems/Print_version; https://en.wikibooks.org/wiki/Mirad_Grammar/print_version; https://en.wikipedia.org/wiki/Craig%20Steven%20Wright; https://en.wikipedia.org/wiki/History%20of%20bitcoin; https://en.wikipedia.org/wiki/Non-fungible%20token; https://ig.ft.com/sites/business-book-award/books/2015/shortlist/digital-gold-by-nathaniel-popper; https://knihobot.cz/g/524686; https://play.google.com/store/books/details/Digital_Gold_Bitcoin_and_the_Inside_Story_of_the_M?id=rafFCwAAQBAJ&hl=cs; https://saifedean.com/tbs; https://sobrief.com/books/the-age-of-cryptocurrency; https://www.alza.cz/media/bitcoinovy-standard-d7483568.htm; https://www.amazon.com/Age-Cryptocurrency-Bitcoin-Challenging-Economic-ebook/dp/B00L73JQ18; https://www.anintegratedworld.com/digital-gold-nathaniel-popper; https://www.databazeknih.cz/prehled-knihy/bitcoinovy-standard-496093; https://www.knihydobrovsky.cz/kniha/bitcoin-billionaires-157106953; https://www.knihydobrovsky.cz/kniha/recenze/675862; https://www.knihydobrovsky.cz/kniha/the-bitcoin-standard-738965647; https://zaujaloma.ai/produkt/kniha-bitcoinovy-standard-saifedean-ammous-cz

Its "What still needs judgement" list:

  1. Verify the reliability of Digital Gold's historical account beyond the single critic's claim
  2. Confirm whether The Book of Satoshi and The Bitcoin Standard were confused in the evidence
  3. Determine if The Blocksize War is a standalone book or part of The Age of Cryptocurrency (both by Vigna and Casey)
  4. Assess the proportion of reviewers who find The Bitcoin Standard reliable versus unreliable
  5. Clarify the publication date and page count for Kings of Crypto
  • 27 further pages were read but yielded no cited evidence.

Wallets: 20261009-143643--how-do-bitcoin-wallets-compare-hardware-wallets-ledger-trezo

Finished 2026-10-09T22:45:22Z. Overall confidence MIXED. Topic note: market/2026-10-09-wallets.md (merged in its § 12, labelled SPARK-REJECTED). Full report: research report 20261009-143643--how-do-bitcoin-wallets-compare-hardware-wallets-ledger-trezo.

Sub-answers labelled CONTESTED or UNDOCUMENTED, with what the run said (Spark output, not checked line by line; see the topic note for the checked version):

  • UNDOCUMENTED · certainty 2/10 that the evidence is silent: What is the US regulatory status of hardware wallets like Ledger and Trezor?

    The evidence indicates that Coinbase allows users to withdraw cryptocurrency to hardware wallets like Ledger and Trezor, as stated in their support documentation: "Yes. You can freely withdraw to self-custody wallets such as Ledger, Trezor, or Coinbase Wallet, though network fees apply." [5] However, the evidence does not provide any information about the specific regulatory status of Ledger and Trezor in the United States. The only mention of regulatory status in the evidence is a statement that Trezor and Ledger are "the top companies dominating the hardware wallet market" without any regulatory context [8]. There is no information about whether these devices are approved, licensed, or regulated by any US government agency, nor is there any mention of specific regulations they must comply with in the US market. The evidence only confirms that these hardware wallets are compatible with Coinbase's platform, not their regulatory standing in the US. Gaps it named: Specific US regulatory status of Ledger and Trezor; Approval or licensing by US regulatory agencies; Compliance requirements for hardware wallets in the US

  • UNDOCUMENTED · certainty 1/10 that the evidence is silent: How does Ballet physical cold-storage wallet security compare to hardware wallets like Ledger and Trezor?

    Ballet physical cold-storage wallet security is not addressed in the evidence provided. The evidence discusses Ledger and Trezor wallets, noting that Ledger offers stronger security features compared to Trezor [8], though Ledger's firmware is closed-source while Trezor uses an open-source framework [8]. Trezor supports over 9,000 crypto assets, whereas Ledger supports over 15,000 [8]. Trezor prioritizes transparency and simplicity, while Ledger focuses on advanced features for security [8]. Trezor Model T and Safe 3 have secure element chips, but not all Trezor models do [8], and Ledger supports Bluetooth connectivity [8]. However, no information about Ballet physical cold-storage wallets is present in the evidence. [8] https://nftevening.com/trezor-vs-ledger Gaps it named: Ballet physical cold-storage wallet security details; Comparison of Ballet to Ledger and Trezor

Claims its own verifier rejected ("not supported by the cited evidence"):

  • ✗ users control fee settings directly — None of the evidence lines state that users control fee settings directly.
  • ✗ Coinbase is licensed as a money transmitter in 48 U.S. states, including New York's BitLicense and Montana licenses — None of the evidence lines mention Coinbase being licensed as a money transmitter in 48 U.S. states, including New York's BitLicense and Montana licenses.

Claims its verifier found only partly supported (14; text cut off by the report at about 160 characters):

  • ~ Ledger employs a Secure Element (SE) chip certified under Common Criteria (EAL5+/EAL6+) for transaction signing and display
  • ~ Ledger uses Clear Signing for secure display rendering within the SE chip
  • ~ Ledger suffered a data breach through its e-commerce partner Shopify in 2020
  • ~ The 2020 data breach exposed personal information of approximately 270,000 customers, including names, addresses, and email addresses
  • ~ Coinbase experienced a data breach in May 2023 involving bribery of customer service agents at an outsourcing firm in India, specifically TaskUs
  • ~ The breach exposed names, addresses, government-ID imagery, transaction history, account balances, phone numbers, and emails
  • ~ Hackers used the stolen data to impersonate Coinbase security employees in social engineering attacks, tricking customers into transferring cryptocurrency to fr
  • ~ Hardware wallets like Ledger Nano S (1099–1442 CZK, ~$45–$60) and Trezor Model T ($170 or €160) have upfront purchase costs but no ongoing transaction fees
  • ~ custodial exchanges like Coinbase and Kraken charge trading fees
  • ~ Kraken's standard spot trading uses tiered maker-taker fees
  • ~ Kraken maintains money transmitter licenses in required jurisdictions and is registered as a Money Services Business (MSB) with FinCEN
  • ~ Kraken is subject to oversight from state financial regulators and the SEC for securities-related activities
  • ~ Coinbase is registered with the CFTC for futures trading
  • ~ Custodial wallets offer convenience through password recovery, simplified tax reporting, and user-friendly interfaces

Facts dropped before the report was written (audit log, facts_dropped_detail):

  • "The price for Trezor One and Trezor Model T is 69 EUR and 149 EUR respectively." (page: https://www.cryptowisser.com/wallet/trezor-wallet; dropped because its supporting quote was not found word-for-word on the page)
  • "The price for Trezor One is 69 EUR." (page: https://www.cryptowisser.com/wallet/trezor-wallet; dropped because its supporting quote was not found word-for-word on the page)
  • "The price for Trezor Model T is 149 EUR." (page: https://www.cryptowisser.com/wallet/trezor-wallet; dropped because its supporting quote was not found word-for-word on the page)

Pages refused, failed or skipped:

  • Skipped as low relevance (18): https://help.coinbase.com/en/coinbase/privacy-and-security/other/coinbase-regulatory-compliance (score 0.25); https://cointelegraph.com/news/bitcoin-whale-transfer-hack-possibility-coinbase-exec-speculates (score 0.18); https://pro.kraken.com/ (score 0.25); http://arxiv.org/abs/0803.2365v1 (score 0.18); https://www.ballet.com/verify (score 0.09); https://www.ncbi.nlm.nih.gov/pubmed/40235856 (score 0.18); https://nypost.com/sports/who-is-jessica-campbell-the-kraken-coach-who-made-nhl-history (score 0.09); https://www.coinbase.com/plp/nar3 (score 0.25); https://www.ballet.com/2FKG (score 0.27); https://finance.yahoo.com/news/coinbase-exploit-hacker-swaps-5m-113956664.html?fr=sycsrp_catchall (score 0.27); https://www.coinbase.com/ (score 0.25); https://www.degruyterbrill.com/database/hrdo/entry/hrdo.HRD-2156_0153/html (score 0.09); http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=11189670 (score 0.0); https://www.bbc.com/sport/football/videos/cm4gd19v09kqo (score 0.0); https://www.law360.com/articles/2344214/coinbase-investor-sues-over-hack-fallout-uk-fine (score 0.18); https://www.benzinga.com/content/45738898/coinbase-knew-customer-data-was-at-risk-in-vendor-hack-months-before-disclosure-report (score 0.18); https://www.pymnts.com/cryptocurrency/2025/binance-and-kraken-reportedly-fend-off-social-engineering-hack (score 0.27); https://www.bloomberg.com/news/articles/2025-05-16/binance-kraken-said-to-have-been-targets-of-coinbase-like-hacks (score 0.0)
  • Refused (robots.txt or DNS failure) (4): https://books.google.com/books?hl=en&lr=lang_en&id=-mIdyTLcUE8C&oi=fnd&pg=PT8&dq=Ballet+cold+storage+security&ots=BKzOa_FEMy&sig=33HPRMxiSexFMI_3OhQcWJxetCI (robots.txt disallows this path); https://books.google.com/books?hl=en&lr=lang_en&id=z96aCwAAQBAJ&oi=fnd&pg=PA1&dq=Ballet+cold+storage+security&ots=bK8fc9-LZA&sig=9lE9EM9tfks57ZPhGq0DmSp_ERk (robots.txt disallows this path); https://monero.forex/ideal-security-how-to-create-a-cold-storage-wallet-for-monero-xmr (dns failure for 'monero.forex': [Errno -2] Name or service not known); https://dl.ucsc.cmb.ac.lk/jspui/handle/123456789/4462 (robots.txt unreachable (5xx/network) -- RFC 9309 says disallow)
  • Fallback browser failed (7): https://www.bscom.cz/hw-penezenky-a-trezory-c16856/ledger (browser: Refused: still a bot check after 15s (first answer 403, title 'Just a moment...')); https://www.kraken.com/sign-in?rfr=consumer-web&preferTheme=light (browser: no free slot within 120s); https://dl.acm.org/doi/10.1145/3843848 (browser: no free slot within 120s); https://ieeexplore.ieee.org/abstract/document/11327832 (browser: no free slot within 120s); https://www.ssrn.com/abstract=5357834 (browser: Refused: still a bot check after 15s (first answer 403, title 'Just a moment...')); https://academic.oup.com/book/10891/chapter/159125334 (browser: Refused: still a bot check after 15s (first answer 403, title 'Just a moment...')); https://www.techmeme.com/250516/p25 (browser: Refused: still a bot check after 15s (first answer 403, title 'Just a moment...'))

  • Wayback fallback failed (5): https://www.bscom.cz/hw-penezenky-a-trezory-c16856/ledger (wayback: no captured copy of this page); https://ieeexplore.ieee.org/abstract/document/11327832 (wayback: no captured copy of this page); https://dl.acm.org/doi/10.1145/3843848 (wayback: no captured copy of this page); https://www.ssrn.com/abstract=5357834 (wayback: no captured copy of this page); https://academic.oup.com/book/10891/chapter/159125334 (wayback: no captured copy of this page)

  • Search stage: 219 candidate results came back across 8 searches. Those not taken were passed over because of per-domain caps or the page budget. Passed-over results named in the log: http://didaktorika.gr/eadd/handle/10442/55828; https://books.google.com/books?hl=en&lr=lang_en&id=2COs6yh_LS0C&oi=fnd&pg=PR9&dq=Ballet+cold+storage+security&ots=7AClpWm7lc&sig=Ees-lmrhoyvu4PcncSGwh6uo1xI; https://books.google.com/books?hl=en&lr=lang_en&id=CFoqAAAAYAAJ&oi=fnd&pg=PA1&dq=Ballet+vs+Ledger+Trezor+security&ots=Zx6_RRjiXf&sig=ZoZQ2Lhehn_2CAeb_AptweF33-o; https://books.google.com/books?hl=en&lr=lang_en&id=i_lkfAD0oYUC&oi=fnd&pg=PR7&dq=Ballet+cold+storage+security&ots=MPPA2uZfqo&sig=W54N3cxS6mOopVIpc9dfAbDDPD4; https://books.google.com/books?hl=en&lr=lang_en&id=pnGsBwAAQBAJ&oi=fnd&pg=PA356&dq=Ballet+cold+storage+security&ots=bXjhmNEIaJ&sig=t3Amwq699b_eJzZ7EQQWFKZyvS4; https://books.google.com/books?hl=en&lr=lang_en&id=sEBZAwAAQBAJ&oi=fnd&pg=PA1908&dq=Ballet+cold+storage+security&ots=iFEj177zdc&sig=4MII3iV9XGzNbrMfXpMo6ZX054Y; https://coinbureau.com/analysis/trezor-vs-ledger; https://cryovaultsolutions.com/blog/ledger-data-breach-switch-2026; https://en.wikibooks.org/wiki/An_Internet_of_Everything%3F/Surveillance_and_Sousveillance; https://en.wikibooks.org/wiki/History_of_video_games/Platforms/Hasbro_P-O-X; https://en.wikibooks.org/wiki/History_of_video_games/Platforms/Wii; https://en.wikipedia.org/wiki/Binance; https://en.wikipedia.org/wiki/Bitcoin; https://en.wikipedia.org/wiki/Blockchain.com; https://en.wikipedia.org/wiki/Cardano%20%28blockchain%20platform%29; https://en.wikipedia.org/wiki/Circle%20Internet%20Group; https://en.wikipedia.org/wiki/Cryptocurrency; https://en.wikipedia.org/wiki/Decentralized%20autonomous%20organization; https://en.wikipedia.org/wiki/History%20of%20bitcoin; https://en.wikipedia.org/wiki/Kraken%20%28cryptocurrency%20exchange%29; https://en.wikipedia.org/wiki/Kraken%20botnet; https://en.wikipedia.org/wiki/TaskUs; https://finance.yahoo.com/news/bybit-coinbase-2025s-biggest-crypto-200102196.html; https://finance.yahoo.com/news/hack-could-cost-coinbase-400m-122053627.html?fr=sycsrp_catchall; https://finance.yahoo.com/video/crypto-wallet-exposed-nearly-14-120000499.html; https://icobench.com/wallets/trezor-vs-ledger; https://koinly.io/blog/trezor-vs-ledger; https://nftevening.com/trezor-vs-ledger; https://play.google.com/store/apps/details?id=com.coinbase.android&hl=en-US; https://play.google.com/store/apps/details?id=com.kraken.trade&hl=cs; https://search.proquest.com/openview/b67ce7199728f3f98d4c9d30c6639456/1?pq-origsite=gscholar&cbl=18750&diss=y; https://shop.ledger.com/pages/ledger-wallet; https://support.ledger.com/article/4404389606417-zd; https://trezor.io/trezor-safe-3; https://www.coinbase.com/signup; https://www.degruyter.com/document/doi/10.1515/9783110629613-005/html; https://www.kraken.com/learn/kraken-vs-coinbase; https://www.ledger.com/LEDGER%20LIVE%20; https://www.ledger.com/academy/topics/ledgersolutions/ledger-vs-trezor-2026-which-hardware-wallet-is-safer-ultimate-comparison; https://www.techrxiv.org/articles/preprint/Ledger_of_Trust_Investigating_Blockchain_s_Impact_on_Credit_Business_Efficiency_and_Security/24191520; https://www.techrxiv.org/doi/full/10.36227/techrxiv.24191520.v1; https://www.webpronews.com/bud-light-eyes-sydney-sweeney-for-10m-deal-to-rebuild-conservative-appeal; https://www.yahoo.com/news/articles/ledger-hit-another-data-breach-121307470.html?fr=sycsrp_catchall; https://www.yahoo.com/news/articles/ledger-reveals-payments-partner-leaked-141833587.html?fr=sycsrp_catchall; https://www.yahoo.com/news/hackers-bribed-overseas-coinbase-agents-161416364.html?fr=sycsrp_catchall; https://www.yahoo.com/news/three-steps-coinbase-users-hack-143000229.html?fr=sycsrp_catchall; https://www.yahoo.com/news/us/articles/over-53-000-crypto-owners-170926537.html; https://www.yahoo.com/news/us/articles/trezor-customer-data-exposed-shipping-131043576.html?fr=sycsrp_catchall

Its "What still needs judgement" list:

  1. Verify exact security certification levels for Trezor's chips
  2. Confirm if Ledger's 2023 Recover controversy directly contradicted their marketing claim
  3. Clarify whether Coinbase's 2023 breach cost was $180M-$400M or if this includes other damages
  4. Confirm if Ledger's 2023 Connect Kit exploit was separate from the $500,000 drain
  5. Verify US regulatory status of Ledger and Trezor beyond Coinbase compatibility
  6. Confirm exact standard trading fee percentages for Coinbase and Kraken
  • 21 further pages were read but yielded no cited evidence.

Patents: 20261009-143847--what-patents-have-been-granted-or-filed-on-bitcoin-and-block

Finished 2026-10-09T23:10:26Z. Overall confidence MIXED. Topic note: notes/2026-10-09-patents.md (Spark material not yet merged). Full report: research report 20261009-143847--what-patents-have-been-granted-or-filed-on-bitcoin-and-block.

Sub-answers labelled CONTESTED or UNDOCUMENTED, with what the run said (Spark output, not checked line by line; see the topic note for the checked version):

  • UNDOCUMENTED · certainty 2/10 that the evidence is silent: What patents have been granted to nChain related to Bitcoin and blockchain technology?

    The evidence indicates that patent US11170366B2, granted on November 9, 2021, relates to private blockchain services [9]. It was filed on May 18, 2018 [9], and is assigned to Inveniam Capital Partners Inc [9], not nChain [9]. The evidence does not provide any patents directly granted to nChain related to Bitcoin or blockchain technology. The only patent referenced is not assigned to nChain, and no other patents held by nChain are mentioned in the evidence. [9] https://patents.google.com/patent/US11170366B2/en Gaps it named: nChain's patents related to Bitcoin and blockchain technology; confirmation of nChain's ownership of any patent

  • UNDOCUMENTED · certainty 9/10 that the evidence is silent: What patents have been filed by Coinbase related to blockchain technology?

    The evidence does not provide any patents filed by Coinbase related to blockchain technology. Source [9] explicitly states that the patent 'Private blockchain services' is not filed by Coinbase. Source [10] mentions a patent related to 'Systems and methods of blockchain transaction recordation' but does not attribute it to Coinbase. Source [6] discusses Coinbase's Chief Legal Officer supporting a partnership to protect blockchain technologies from patent trolls, but this does not indicate any patents filed by Coinbase itself. The evidence does not list any patents filed by Coinbase, only references to other patents and a statement about patent trolls. Therefore, the evidence does not confirm any patents filed by Coinbase related to blockchain technology. Gaps it named: Coinbase's specific blockchain-related patents; Confirmation of Coinbase's patent filings

  • UNDOCUMENTED: What patents have been granted to Ledger related to cryptocurrency hardware wallets?

    No usable evidence was gathered for this sub-question. Search returned nothing readable, or every page was refused or empty.

  • CONTESTED · certainty 6/10: What patents have been granted to Bank of America related to blockchain technology?

    Bank of America has been granted patents related to blockchain technology, as evidenced by the patent US11200564B2 (granted December 14, 2021), which was filed as US20160292672A1 on March 31, 2016, and is related to blockchain transaction recordation [10]. However, the patent is assigned to Nasdaq Inc., not Bank of America [10]. Another patent, US11170366B2, covers private blockchain services for documenting digital asset usage and was granted to Inveniam Capital Partners Inc., not Bank of America [9]. A claim that Bank of America has 53 blockchain and cryptocurrency patents [11] appears to be a misattribution, as the evidence does not confirm Bank of America as the assignee for these patents. The evidence does not provide any patents directly granted to Bank of America, only patents assigned to other entities or misattributed in the source [11]. Gaps it named: The evidence does not confirm any patents directly granted to Bank of America; The source [11] claiming 53 patents is not verified against Bank of America's actual patent portfolio

Claims its own verifier rejected ("not supported by the cited evidence"):

  • ✗ Block has filed a patent related to blockchain transaction recordation, as referenced in the Google Patents entry for US20160292672A1. — None of the evidence lines state or imply that Block has filed a patent related to blockchain transaction recordation as referenced in the Google Patents entry for US20160292672A1.

Claims its verifier found only partly supported (10; text cut off by the report at about 160 characters):

  • ~ IBM has filed multiple patents related to blockchain technology.
  • ~ In 2020, IBM secured a patent for a 'gaming consensus protocol for blockchain' that enables players' systems to validate transactions on a blockchain ledger whi
  • ~ This patent, originally filed in 2018 and approved in November 2020, allows gaming peers to perform consensus on transaction ordering while keeping smart contra
  • ~ IBM filed a patent addressing blockchain implementation on IoT devices, which solves challenges like limited computing power by limiting numbers in proof-of-wor
  • ~ Bank of America has been granted patents related to blockchain technology
  • ~ patent US11200564B2 was filed as US20160292672A1 on March 31, 2016
  • ~ Block (formerly Square) has filed at least two patents related to cryptocurrency.
  • ~ COPA partners with Unified Patents to protect blockchain technologies from patent trolls
  • ~ Unified Patents' Blockchain Zone aims to challenge patents owned by non-practicing entities (NPEs)
  • ~ NPEs account for 58% of all US patent litigation

Facts dropped before the report was written (audit log, facts_dropped_detail):

  • "COPA is the Crypto Open Patent Alliance." (page: https://www.opencrypto.org/page3; dropped because its supporting quote was not found word-for-word on the page)
  • "The patent was filed by Nasdaq Inc, not Coinbase." (page: https://patents.google.com/patent/US20160292672A1/en; dropped because its supporting quote was not found word-for-word on the page)

  • "Bank of America has not been mentioned in relation to specific blockchain patents in the provided document." (page: https://patentpc.com/industries/blockchain-and-fintech; dropped because its supporting quote was not found word-for-word on the page)

  • One sub-question was replanned to: What patents have been granted to Ledger related to cryptocurrency hardware wallets?

Pages refused, failed or skipped:

  • Refused (robots.txt or DNS failure) (3): https://www.linkedin.com/pulse/blockchain-applications-intellectual-property-yes-s%C3%A9bastien-ragot (robots.txt disallows this path); https://www.academia.edu/64979608/Application_of_blockchain_technology (robots.txt disallows this path); https://twitter.com/jack/status/1304099079211810817 (robots.txt disallows this path)
  • Skipped as low relevance (9): https://www.tomshardware.com/tech-industry/artificial-intelligence/openai-and-microsofts-alliance-fractures-as-cloud-exclusivity-deal-ends-azures-single-provider-monopoly-for-chatgpt-is-officially-over (score 0.2); https://www.bankofamerica.com/online-banking/sign-in (score 0.22); https://secure.bankofamerica.com/auth/signon (score 0.22); https://kryptomagazin.cz/pocet-blockchainovych-patentu-ibm-vzrostl-za-posledni-rok-o-300 (score 0.25); https://kryptohodler.cz/ibm-navysila-sve-blockchainove-patenty-o-300 (score 0.25); https://www.edureka.co/blog/blockchain-applications (score 0.22); https://coinmate.io/cz/blockchain (score 0.11); https://shop.ledger.com/pages/ledger-wallet-download (score 0.22); https://www.ledger.com/start/my-ledger (score 0.11)
  • Fallback browser failed (3): https://allegro.cz/produkt/penezenka-na-kryptomeny-ledger-nano-s-plus-kompatibilni-s-windows-mac-linux-4f052542-74fa-4cc7-8d0c-be69bc19b64a (browser: TimeoutError: Page.goto: Timeout 30000ms exceeded.); https://www.alza.cz/ledger-bitcoin-wallet-nano-s-d5003297.htm (browser: Refused: still a bot check after 15s (first answer 403, title 'Just a moment...')); https://coinmate.io/cz/blockchain (browser: Refused: still a bot check after 15s (first answer 403, title 'Just a moment...'))

  • Wayback fallback failed (1): https://allegro.cz/produkt/penezenka-na-kryptomeny-ledger-nano-s-plus-kompatibilni-s-windows-mac-linux-4f052542-74fa-4cc7-8d0c-be69bc19b64a (wayback: no captured copy of this page)

  • Search stage: 109 candidate results came back across 9 searches. Those not taken were passed over because of per-domain caps or the page budget. Passed-over results named in the log: https://allegro.cz/produkt/penezenka-na-kryptomeny-ledger-nano-s-plus-kompatibilni-s-windows-mac-linux-4f052542-74fa-4cc7-8d0c-be69bc19b64a; https://en.wikibooks.org/wiki/Cultural_Anthropology/Print_version; https://en.wikibooks.org/wiki/Information_Technology_and_Ethics/Social_Media_Data_Collection; https://en.wikibooks.org/wiki/Intellectual_Property_and_the_Internet/Print_version; https://en.wikibooks.org/wiki/Introduction_to_Computer_Information_Systems/Print_version; https://en.wikibooks.org/wiki/The_World_of_Peer-to-Peer_%28P2P%29/All_Chapters; https://en.wikibooks.org/wiki/The_World_of_Peer-to-Peer_%28P2P%29/Print_version; https://en.wikipedia.org/wiki/Blockchain; https://en.wikipedia.org/wiki/Ethereum; https://en.wikipedia.org/wiki/IBM%20Research; https://en.wikipedia.org/wiki/MARA%20Holdings; https://en.wikipedia.org/wiki/Software%20patent; https://patentpc.com/industries/blockchain-and-fintech; https://shop.ledger.com/pages/hardware-wallet; https://shop.ledger.com/pages/ledger-wallet-download; https://www.bitlaw.com/blockchain/blockchain-patents.html; https://www.dashop.cz/bitcoin/ledger-nano-gen5; https://www.express-servis.cz/p/ledger-flex-crypto-wallet-bezpecnost-a-prenosnost; https://www.ibm.com/think/topics/blockchain-security; https://www.opencrypto.org/about; https://www.opencrypto.org/joining; https://www.zbozi.cz/vyrobek/ledger-nano-s-hardware-wallet; https://www.zdnet.com/finance/blockchain/executives-guide-to-blockchain

Its "What still needs judgement" list:

  1. Verify if Block's patent US20160292672A1 is actually filed by Block (not misattributed to Coinbase as in source [10])
  2. Confirm whether Bank of America's patent US11200564B2 is correctly attributed to Nasdaq Inc. and not Bank of America
  3. Determine if nChain has any patents related to Bitcoin that were not mentioned in the evidence
  4. Check if Ledger has any patents related to cryptocurrency hardware wallets (evidence was not found)
  5. Verify if COPA holds any patents directly or if it only facilitates access to members' patents
  • 37 further pages were read but yielded no cited evidence.

Hacks: 20261009-143852--what-were-the-major-bitcoin-exchange-hacks-and-thefts-mt-gox

Finished 2026-10-09T23:00:25Z. Overall confidence CONFIDENT. Topic note: notes/2026-10-09-hacks-causes-defenses.md (Spark material not yet merged). Full report: research report 20261009-143852--what-were-the-major-bitcoin-exchange-hacks-and-thefts-mt-gox.

Sub-answers labelled CONTESTED or UNDOCUMENTED, with what the run said (Spark output, not checked line by line; see the topic note for the checked version):

  • UNDOCUMENTED · certainty 1/10 that the evidence is silent: What caused the Ledger data breach according to official reports?

    According to the evidence, the Ledger data breach in June 2020 exposed over 1 million email addresses, along with names, physical addresses, and phone numbers [30]. The data was initially sold before being publicly dumped in December 2020 [30]. The data was provided to Have I Been Pwned (HIBP) by Alon Gal, CTO of Hudson Rock, a cybercrime intelligence firm [30]. However, the evidence does not specify the cause of the breach (e.g., phishing, malware, or system vulnerability) or identify the attackers. The evidence also includes unrelated data breaches (e.g., the UK Ministry of Defence leak [22] and Deloitte breach [34]), which do not pertain to Ledger. The official reports referenced in the evidence do not explain what caused the Ledger breach, only describing the breach's scope and timeline. The evidence does not address the cause of the Ledger data breach, as it only describes the breach's exposure of data, its timeline, and the source of the data for HIBP. No official report cited in the evidence states what caused the breach (e.g., technical flaw, human error, or external attack). The evidence includes a separate Ministry of Defence leak [22] and Deloitte breach [34], but these are unrelated to Ledger and do not explain Ledger's breach cause. The evidence does not provide information on the cause of the Ledger data breach, only the breach's details and timeline. The cause remains undocumented in the provided sources. Gaps it named: cause of the Ledger data breach; identity of attackers; technical or human cause of the breach

Claims its own verifier rejected ("not supported by the cited evidence"):

  • ✗ The evidence does not specify the exact technical vulnerability or method used to collect the login codes — The evidence does not specify the exact technical vulnerability or method used to collect the login codes.

Claims its verifier found only partly supported (14; text cut off by the report at about 160 characters):

  • ~ The Mt. Gox hack was caused by a combination of security vulnerabilities and insider access
  • ~ The hack was characterized by weak security measures, including a weak admin password that could be brute-forced within days
  • ~ The incident led to the theft of 744,000 bitcoins, prompting Mt. Gox to file for bankruptcy protection in Japan
  • ~ Lichtenstein stole approximately 120,000 Bitcoin (valued at $4.5 billion at the time) by fraudulently authorizing over 2,000 transactions to transfer 119,754 Bi
  • ~ The Binance 2019 hack was caused by hackers who collected login codes of various users over several months
  • ~ The Coincheck hack was caused by a security breach in their NEM address and hot wallet system
  • ~ 523 million NEMs were stolen from their NEM address
  • ~ Cold wallets hold 5–15% of assets for daily liquidity, while the majority remains offline
  • ~ River uses 100% cold storage for client deposits
  • ~ API security includes encrypted communication (TLS 1.3+), certificate pinning, rate limiting, and DDoS protection
  • ~ Cold storage secures the majority of reserves offline, keeping private keys disconnected from the internet to prevent online theft
  • ~ This involves storing keys on air-gapped computers or hardware wallets, which sign transactions offline without ever exposing private keys online
  • ~ Exchanges often use hardware wallets—specialized devices that maintain offline security—and paper wallets, where private keys are printed and stored physically
  • ~ Cold storage requires regular firmware updates and backup verifications

Facts dropped before the report was written (audit log, facts_dropped_detail):

  • "The 2019 Binance hack is not discussed in the document." (page: https://finance.yahoo.com/news/inside-binance-accounts-internal-investigators-171443134.html; dropped because its supporting quote was not found word-for-word on the page)
  • "The document does not provide information on what caused the Bitfinex hack." (page: https://www.law360.com/articles/1890526/bitfinex-hacker-deserves-5-years-for-crypto-heist-feds-say; dropped because it is a statement about the document, not a fact)
  • "The document does not provide specific details about the Binance 2019 hack." (page: https://en.wikipedia.org/wiki/Cryptocurrency%20and%20crime; dropped because it is a statement about the document, not a fact)
  • "The Ledger data breach is not mentioned in the document." (page: https://finance.yahoo.com/news/inside-binance-accounts-internal-investigators-171443134.html; dropped because its supporting quote was not found word-for-word on the page)

Pages refused, failed or skipped:

  • Skipped as low relevance (9): https://www.businessinsider.com/personal-finance/investing/best-crypto-bitcoin-exchanges (score 0.0); https://www.insurancejournal.com/news/east/2025/06/11/827295.htm (score 0.29); https://finance.yahoo.com/news/senator-opens-inquiry-binance-over-120629103.html (score 0.14); https://cryptobriefing.com/bitget-hacker-withdraws-binance-transfers (score 0.29); https://www.crowdfundinsider.com/2019/08/150394-chipmixer-bitcoin-tumbler-used-to-launder-funds-stolen-in-80-million-usd-hack-on-binance (score 0.29); https://support.binance.us/en/articles/9842963-about-binance-us (score 0.29); http://roberts.pm/buttfinesse (score 0.0); https://www.beckershospitalreview.com/supply-chain/80-of-healthcare-data-breaches-from-hacks-report-finds.html (score 0.14); https://altcoinss.com/coincheck-investigates-another-hack-but-funds-appear-safu (score 0.17)

  • Fallback browser failed (4): https://www.msn.com/en-gb/money/other/mt-gox-former-ceo-among-victims-in-revolut-breach-after-hackers-used-real-government-email/ar-AA2cex8S?ocid=BingNewsVerp (browser: rendered, but only 61 characters of text); https://www.msn.com/en-us/money/general/exclusive-binance-fires-top-investigators-who-claim-to-have-uncovered-evidence-of-iranian-sanctions-violations/ar-AA1Wj0Y6 (browser: rendered, but only 61 characters of text); https://www.msn.com/en-gb/money/other/mt-gox-former-ceo-among-victims-in-revolut-breach-after-hackers-used-real-government-email/ar-AA2cex8S (browser: rendered, but only 61 characters of text); https://www.msn.com/en-us/money/general/exclusive-binance-fires-top-investigators-who-claim-to-have-uncovered-evidence-of-iranian-sanctions-violations/ar-AA1Wj0Y6?ocid=BingNewsVerp (browser: rendered, but only 61 characters of text)

  • Search stage: 122 candidate results came back across 8 searches. Those not taken were passed over because of per-domain caps or the page budget. Passed-over results named in the log: https://en.wikibooks.org/wiki/Information_Technology_and_Ethics/Cryptocurrency_Overview; https://en.wikibooks.org/wiki/Information_Technology_and_Ethics/Types_of_Security; https://en.wikibooks.org/wiki/Introduction_to_Computer_Information_Systems/E-Commerce; https://en.wikibooks.org/wiki/Introduction_to_Computer_Information_Systems/Print_version; https://en.wikibooks.org/wiki/Perspectives_in_Digital_Culture/Web_as_Public_and_Private_Space; https://en.wikibooks.org/wiki/Professionalism/BitTorrent_and_BitCoin; https://en.wikipedia.org/wiki/Bitcoin; https://en.wikipedia.org/wiki/Cryptocurrency%20and%20crime; https://en.wikipedia.org/wiki/United%20States%20government%20group%20chat%20leaks; https://thedatascientist.com/cryptocurrency-security-threats-from-mt-gox-to-bitstamp; https://www.cnet.com/news/privacy/record-number-of-data-breaches-reported-in-2021-new-report-says; https://www.cnn.com/2026/04/07/politics/iran-linked-hackers-disrupt-us-industrial-sites; https://www.hallattorneys.com/ledger-data-breach; https://www.msn.com/en-us/money/financial-regulation/doj-warns-prosecutors-of-weaker-binance-help-rattling-global-crypto-enforcement/ar-AA27wEDs?ocid=BingNewsVerp; https://www.riskledger.com/data-insights-reports

Its "What still needs judgement" list:

  1. How specific security practices were applied in post-hack analyses of major breaches
  2. Effectiveness of recommended practices in preventing future hacks
  3. Connection between Mt. Gox's failures and recommended security measures
  4. How Bitfinex's cloud storage vulnerability relates to the absence of specific security measures
  5. How cold storage specifically prevents breaches from vulnerabilities like key exposure during transfers
  6. Whether exchanges use specific protocols for key management during transfers between offline and online systems
  7. The effectiveness of these practices in preventing actual breaches (e.g., case studies of successful prevention)
  • 23 further pages were read but yielded no cited evidence.

FinCEN wallet rule: 20261009-144031--in-2026-did-fincen-or-the-us-treasury-propose-a-rule-requiri

Finished 2026-10-09T22:47:59Z. Overall confidence CONFIDENT. Topic note: legislation/us-federal-fincen-wallet-registration.md (Spark material not yet merged). Full report: research report 20261009-144031--in-2026-did-fincen-or-the-us-treasury-propose-a-rule-requiri.

Claims its verifier found only partly supported (12; text cut off by the report at about 160 characters):

  • ~ The 2020 FinCEN rule proposal required banks and money services businesses (MSBs) to verify identities and file reports for transactions involving unhosted cryp
  • ~ An 'unhosted wallet' was defined as one where no financial institution processes transactions, contrasting with 'otherwise covered wallets' held at foreign inst
  • ~ FinCEN withdrew the rule in 2024, easing compliance burdens for self-custody
  • ~ FinCEN withdrew it on October 5, 2026
  • ~ The 2020 unhosted wallet rule proposal was withdrawn by FinCEN in 2026
  • ~ FinCEN formally withdrew the rule in 2026, stating it would take no further action on the proposed rulemaking (NPRM)
  • ~ The 2020 unhosted wallet rule proposal was withdrawn by FinCEN in October 2026
  • ~ The withdrawal was formalized with a notice signed by FinCEN Deputy Director Jimmy L. Kirby
  • ~ The US Treasury withdrew the 2026 crypto wallet registration proposal in 2026
  • ~ The rule, initially proposed in 2020, would have required banks and money services businesses to report transactions involving unhosted wallets exceeding $3,000
  • ~ The withdrawal followed nearly six years of public comment and consideration
  • ~ The withdrawal was framed as advancing the Trump administration's deregulatory agenda and keeping digital asset rules 'fit-for-purpose,' citing a July 2025 Whit

Pages refused, failed or skipped:

  • Refused (robots.txt or DNS failure) (5): https://www.fincen.gov/news/news-releases/fincen-announces-withdrawals-proposed-digital-asset-related-rules (robots.txt unreachable (5xx/network) -- RFC 9309 says disallow); https://www.fincen.gov/system/files/2019-05/FinCEN%20Guidance%20CVC%20FINAL%20508.pdf (robots.txt unreachable (5xx/network) -- RFC 9309 says disallow); https://www.fincen.gov/ (robots.txt unreachable (5xx/network) -- RFC 9309 says disallow); https://home.treasury.gov/news/press-releases/sm1216 (robots.txt unreachable (5xx/network) -- RFC 9309 says disallow); https://stg2.fincen.gov/ (robots.txt unreachable (5xx/network) -- RFC 9309 says disallow)
  • Skipped as low relevance (4): https://www.federalregister.gov/public-inspection/2026-20430/requirements-for-certain-transactions-involving-convertible-virtual-currency-or-digital-assets (score 0.0); https://bankingjournal.aba.com/2026/10/fincen-withdraws-proposals-on-crypto-recordkeeping (score 0.12); https://www.newsbtc.com/regulation/fincen-withdraws-crypto-rules-targeting-mixers-and-unhosted-wallets (score 0.14); https://fincenid.fincen.gov/ (score 0.0)

  • Fallback browser failed (6): https://www.msn.com/en-us/news/other/fincen-scraps-proposed-crypto-mixer-and-wallet-rules/ar-AA2dEqdP (browser: rendered, but only 61 characters of text); https://www.msn.com/en-us/money/financial-regulation/fincen-scraps-proposed-crypto-mixer-and-wallet-rules/ar-AA2dEqdP (browser: rendered, but only 42 characters of text); https://www.msn.com/en-us/money/financial-regulation/bitcoin-holds-above-85-000-as-treasury-drops-wallet-reporting-plan-cftc-proposes-crypto-rules/ar-AA2dCyc6?ocid=BingNewsVerp (browser: rendered, but only 61 characters of text); https://www.msn.com/en-us/money/financial-regulation/bitcoin-holds-above-85-000-as-treasury-drops-wallet-reporting-plan-cftc-proposes-crypto-rules/ar-AA2dCyc6 (browser: rendered, but only 61 characters of text); https://www.msn.com/en-us/money/general/bitcoin-holds-above-85-000-as-treasury-drops-wallet-reporting-plan-cftc-proposes-crypto-rules/ar-AA2dCyc6 (browser: rendered, but only 61 characters of text); https://www.msn.com/en-us/money/financial-regulation/fincen-scraps-proposed-crypto-mixer-and-wallet-rules/ar-AA2dEqdP?ocid=BingNewsVerp (browser: rendered, but only 42 characters of text)

  • Search stage: 212 candidate results came back across 8 searches. Those not taken were passed over because of per-domain caps or the page budget. Passed-over results named in the log: https://blockonomi.com/fincen-withdraws-proposed-crypto-mixer-and-unhosted-wallet-rules; https://boiefiling.fincen.gov/; https://cointelegraph.com/news/fincen-crypto-mixing-rule-legitimate-activity; https://cryptobriefing.com/us-treasury-withdraws-proposed-crypto-rules-on-unhosted-wallets-mixers; https://decrypt.co/380120/treasury-kills-crypto-unhosted-wallet-mixer-surveillance-rules; https://decrypt.co/380260/prosecutors-cite-bitcoin-fog-ruling-against-roman-storms-venue-challenge; https://finance.yahoo.com/markets/crypto/articles/fincen-withdraws-proposed-crypto-mixer-143759934.html; https://finance.yahoo.com/markets/crypto/articles/fincen-withdraws-proposed-crypto-mixer-143759934.html?fr=sycsrp_catchall; https://finance.yahoo.com/markets/crypto/articles/treasury-kills-crypto-unhosted-wallet-201938517.html; https://finance.yahoo.com/markets/crypto/articles/treasury-kills-crypto-unhosted-wallet-201938517.html?fr=sycsrp_catchall; https://fincenid.fincen.gov/; https://insidecrypto.net/us-treasury-withdraws-crypto-wallet; https://note.com/noble_chives458/n/nd3032c47f15a?hl=en; https://stg2.fincen.gov/; https://thecurrencyanalytics.com/crypto-exchanges/u-s-treasury-kills-10000-unhosted-wallet-reporting-rule-after-six-years-of-pushback-300545; https://thecurrencyanalytics.com/digital-wallet/treasury-kills-crypto-wallet-and-mixer-rules-freeing-4500-self-custody-users-from-reporting-burden-300427; https://usethebitcoin.com/news/fincen-withdraws-proposed-crypto-rules-treasury-money-laundering-risks; https://www.ainvest.com/news/unhosted-wallet-rule-fincen-killed-settles-stands-keys-2610; https://www.cryptacount.com/en/news/fincen-withdraws-10000-unhosted-wallet-mixer-reporting-rules-2026; https://www.cryptotimes.io/2026/10/05/u-s-treasury-withdraws-two-crypto-surveillance-proposals; https://www.federalregister.gov/public-inspection/2026-20430/requirements-for-certain-transactions-involving-convertible-virtual-currency-or-digital-assets; https://www.fincen.gov/; https://www.livebitcoinnews.com/u-s-scraps-proposed-3000-crypto-wallet-recordkeeping-rule-after-nearly-six-years; https://www.msn.com/en-us/money/financial-regulation/bitcoin-holds-above-85-000-as-treasury-drops-wallet-reporting-plan-cftc-proposes-crypto-rules/ar-AA2dCyc6; https://www.msn.com/en-us/money/financial-regulation/bitcoin-holds-above-85-000-as-treasury-drops-wallet-reporting-plan-cftc-proposes-crypto-rules/ar-AA2dCyc6?ocid=BingNewsVerp; https://www.msn.com/en-us/money/financial-regulation/fincen-scraps-proposed-crypto-mixer-and-wallet-rules/ar-AA2dEqdP; https://www.thecoinrepublic.com/2026/10/06/u-s-treasury-news-fincen-withdraws-crypto-wallet-mixer-rules

Its "What still needs judgement" list:

  1. Verify the exact threshold amounts for transaction reporting ($3,000 vs. $10,000) across all sources
  2. Confirm whether the withdrawal date was October 5, 2026, or if there was a typo in the year (2023 vs. 2026)
  3. Check if the White House's July 2025 digital asset report was actually published and referenced in the withdrawal notice
  4. Verify if the 2023 mixer proposal was withdrawn alongside the 2020 wallet proposal in 2026
  5. Confirm if the 7,500+ public comments figure is accurate and from the 2020 proposal period
  • 2 further pages were read but yielded no cited evidence.

KYC/AML for sellers: 20261009-144154--what-kyc-and-aml-rules-apply-in-the-us-to-a-business-selling

Finished 2026-10-09T23:06:52Z. Overall confidence CONFIDENT. Topic note: legislation/us-kyc-aml-selling-bitcoin.md (Spark material not yet merged). Full report: research report 20261009-144154--what-kyc-and-aml-rules-apply-in-the-us-to-a-business-selling.

Claims its verifier found only partly supported (9; text cut off by the report at about 160 characters):

  • ~ Bitcoin sellers must register with FinCEN as a Money Service Business (MSB) within 180 days of beginning operations
  • ~ The registration is mandatory for virtual asset service providers operating in the United States
  • ~ Nevada specifically requires confirmation of FinCEN MSB registration
  • ~ Customer identification procedures for Bitcoin sales to the public are required under Anti-Money Laundering (AML) and Know Your Customer (KYC) regulations
  • ~ Crypto businesses, including exchanges and wallet providers classified as Money Services Businesses (MSBs), must file Suspicious Activity Reports (SARs) with Fi
  • ~ The Travel Rule applies to Bitcoin transactions in the US when they constitute a 'transmittal of funds' and involve a Money Services Business (MSB) acting as a
  • ~ Covered institutions, including crypto exchanges and custodial wallet providers, must collect and transmit specific information for transactions above a $3,000
  • ~ Bitcoin sellers in Nevada are required to obtain a money transmitter license under Nevada Revised Statutes (NRS) Chapter 671
  • ~ This includes cryptocurrency operators, Bitcoin sellers, and Bitcoin ATM operators

Pages refused, failed or skipped:

  • Skipped as low relevance (2): https://www.cnn.com/business (score 0.0); https://www.leg.state.nv.us/NAC/NAC-671.html (score 0.29)

  • Refused (robots.txt or DNS failure) (2): https://www.fincen.gov/resources/msb-state-selector (robots.txt unreachable (5xx/network) -- RFC 9309 says disallow); https://www.fincen.gov/resources/statutes-regulations/guidance/funds-travel-regulations-questions-answers (robots.txt unreachable (5xx/network) -- RFC 9309 says disallow)

  • Search stage: 93 candidate results came back across 8 searches. Those not taken were passed over because of per-domain caps or the page budget. Passed-over results named in the log: https://en.wikibooks.org/wiki/Cultural_Anthropology/Print_version; https://en.wikibooks.org/wiki/Information_Technology_and_Ethics/Cryptocurrency_Legal_%26_Ethical_Perspectives; https://en.wikibooks.org/wiki/Information_Technology_and_Ethics/Introduction_to_cryptocurrency; https://en.wikibooks.org/wiki/Introduction_to_Computer_Information_Systems/Print_version; https://en.wikibooks.org/wiki/Lentis/Cryptocurrency; https://en.wikibooks.org/wiki/Lentis/Internet_Anonymity; https://en.wikipedia.org/wiki/Cryptocurrency%20exchange; https://en.wikipedia.org/wiki/Financial%20Crimes%20Enforcement%20Network; https://en.wikipedia.org/wiki/Security%20token%20offering

Its "What still needs judgement" list:

  1. Whether the 180-day deadline applies specifically to Bitcoin sellers or is a general MSB requirement
  2. Whether the MSB registration requirement applies to all Bitcoin sellers or only those meeting the 'exchanger' or 'administrator' definitions
  3. Exact identification methods required for customer identification procedures
  4. Whether Bitcoin transactions directly trigger CTRs or SARs without a business intermediary
  5. The exact implementation timeline for the $250 threshold proposal
  6. Whether all MSBs are uniformly classified under the same regulatory framework
  7. The specific consequences for non-compliance beyond transaction delays or cancellations
  8. Specific differences in state AML program requirements beyond New York's standards
  • 11 further pages were read but yielded no cited evidence.

Banking: 20261009-144200--how-hard-is-it-for-bitcoin-and-crypto-businesses-to-get-us-b

Finished 2026-10-09T23:13:24Z. Overall confidence CONFIDENT. Topic note: market/2026-10-09-banking.md (status pointer only). Full report: research report 20261009-144200--how-hard-is-it-for-bitcoin-and-crypto-businesses-to-get-us-b.

Claims its verifier found only partly supported (4; text cut off by the report at about 160 characters):

  • ~ Crypto businesses face significant challenges in obtaining US bank accounts in 2025-2026 due to Operation Choke Point 2.0
  • ~ Chase Business Complete Banking® allows sending/receiving funds to crypto exchanges
  • ~ Banks face liquidity risks from unpredictable deposit flows tied to crypto-asset entities
  • ~ Crypto-friendly banks like Chase and Bank of America allow users to fund regulated exchanges without excessive holds or fraud flags

Facts dropped before the report was written (audit log, facts_dropped_detail):

  • "The document discusses banking engagement with digital assets." (page: https://www.whitehouse.gov/wp-content/uploads/2025/07/Digital-Assets-Report-EO14178.pdf; dropped because its supporting quote was not found word-for-word on the page)

Pages refused, failed or skipped:

  • Refused (robots.txt or DNS failure) (3): https://www.linkedin.com/top-content/finance/banking-regulations-update/cryptocurrency-regulations-in-banking (robots.txt disallows this path); https://www.linkedin.com/top-content/technology/blockchain-legal-frameworks/regulatory-challenges-in-blockchain (robots.txt disallows this path); https://www.nasdaq.com/articles/how-failures-at-silvergate-svb-and-signature-bank-impact-bitcoin-investment (robots.txt unreachable (5xx/network) -- RFC 9309 says disallow)
  • Skipped as low relevance (2): https://businessanywhere.io/crypto-friendly-banks (score 0.17); https://www.federalregister.gov/documents/2025/01/31/2025-02123/strengthening-american-leadership-in-digital-financial-technology (score 0.0)
  • Fallback browser failed (1): https://memeblock.com/2025/12/02/crypto-regulations-adoption/operation-choke-point-2-0-explained-report-crypto-debanking (browser: rendered, but only 127 characters of text)

  • Wayback fallback failed (1): https://memeblock.com/2025/12/02/crypto-regulations-adoption/operation-choke-point-2-0-explained-report-crypto-debanking (wayback: no captured copy of this page)

  • Search stage: 137 candidate results came back across 8 searches. Those not taken were passed over because of per-domain caps or the page budget. Passed-over results named in the log: https://corbettreport.com/operation-choke-point-2-0; https://crypto.news/erebor-bank-crypto-banking-valuation-silvergate; https://en.wikibooks.org/wiki/Information_Technology_and_Ethics/Security_Breach; https://en.wikibooks.org/wiki/LPI_Linux_Certification/Print_Version_A; https://en.wikibooks.org/wiki/US_History/Print_version; https://en.wikipedia.org/wiki/Bitcoin; https://en.wikipedia.org/wiki/Crypto.com; https://en.wikipedia.org/wiki/Cryptocurrency; https://en.wikipedia.org/wiki/List%20of%20bank%20failures%20in%20the%20United%20States%20%282008%E2%80%93present%29; https://en.wikipedia.org/wiki/Silvergate%20Bank; https://en.wikipedia.org/wiki/SoFi; https://en.wikipedia.org/wiki/U.S.%20Strategic%20Bitcoin%20Reserve; https://silvergate.com/; https://www.block3finance.com/the-legal-challenges-of-offshore-crypto-banking; https://www.cnbc.com/2023/03/02/silvergate-capital-shares-crater-after-the-crypto-bank-delays-annual-report.html; https://www.cnbc.com/2023/03/08/silvergate-shutting-down-operations-and-liquidating-bank.html?msockid=18e7c5c808a8604016ccd22509026185; https://www.cnbc.com/2023/03/10/crypto-bank-signature-slides-on-friday-amid-troubles-at-silicon-valley-bank-silvergate.html; https://www.linkedin.com/top-content/finance/regulatory-compliance-in-finance/crypto-regulations-for-mainland-financial-institutions

Its "What still needs judgement" list:

  1. The exact difficulty level for specific types of crypto businesses (e.g., exchanges vs. wallet providers)
  2. The current status of the CLARITY Act in the Senate
  3. The extent to which offshore banking is now a common alternative for crypto businesses
  4. The specific regulatory approvals required for crypto-friendly banks beyond federal charters or state licenses
  5. The exact percentage of banks classified as crypto-friendly versus crypto-hostile
  6. The full list of banks that have been explicitly labeled as crypto-hostile beyond Discover, Capital One, and Citi
  7. The exact percentage of crypto businesses affected by banking restrictions
  8. Specific examples of successful banking relationships with crypto firms
  • 4 further pages were read but yielded no cited evidence.

7. Known gaps

These are gathered from each researcher's report and each note's gaps section, minus the items fixed in § 5, plus what this check found. The topic notes carry more detail.

7.1 Whole topics missing

  • Origins 2007–2011: done in the rerun. Still not saved: Satoshi's Aug 2008 emails with Adam Back and Jan 2009 emails with Hal Finney (released in COPA v Wright), New Liberty Standard's 2009 pages, Finney's "Running bitcoin" tweet and The Times of 3 Jan 2009. Details in the timeline's § 11.
  • Market data (the README's main purpose for market/): price history, volume, supply, ETFs, institutional holdings and mining economics.
  • Non-US legislation, for example the EU's MiCA, the UK, El Salvador and others. The merchants note touches El Salvador only in passing.
  • Spark material not merged into the Satoshi, patents, hacks, wallet-rule and KYC/AML notes. It is listed in § 6; NEXT.md item 2 covers folding it in.

7.2 Blocked or paywalled sources, common to most topics

WebSearch was exhausted for the session, so the researchers used the Spark research search CLI and direct fetches. The following sites blocked automated reads, and anything taken from them is marked "news", "reported" or "unverified":

  • Federal: justice.gov HTML (press releases), sec.gov (which needs a contact email that was deliberately not sent), congress.gov, cftc.gov (robots.txt), msb.fincen.gov (robots.txt disallows all, so no FinCEN MSB registration was checked for any company), CourtListener dockets.
  • State: dfs.ny.gov, leginfo.legislature.ca.gov, DFPI, mass.gov, capitol.hawaii.gov, legis.iowa.gov, commerce.alaska.gov, difi.az.gov, rules.sos.ga.gov.
  • Law and news: Justia, FindLaw and LegiScan; NYT, Wired, Forbes, Bloomberg, FT, The Economist, Law360, CNBC and MSN. The Guardian was not used because its terms forbid LLM use.

These are the URLs for NEXT.md item 3 (open in Chrome).

7.3 By topic

Who is Satoshi (notes/2026-10-09-who-is-satoshi.md) - Not read in the original: NYT/Carreyrou on Adam Back (2026-04-08), Wired 2011/2015/2019, Forbes 2014, New Yorker 2011, Fast Company 2011, Business Insider 2013, Bloomberg 2017/2020, FT 2016, the Aston stylometry study, and the Snopes and AFP fact-checks. These come from secondary coverage. - Results not retrieved: Adebayo and Yampolskiy (IEEE BigData 2024). - Outcomes unknown: no charging decision on the 2024 CPS referral of Wright and Matthews; no outcome of the March 2025 Attorney General referral. - Not saved: Granath v Wright (Oslo, 2022); the Kleiman v Wright final judgment and sanctions orders. The Kleiman verdict PDF has no text layer. - Murphy v DHS: what ICE released is not public; ECF 19, 20 and 22 are not on RECAP. - Chain Bulletin's 2020 timestamp article and Stefan Thomas's original chart were not found. - Unresolved: Sassaman's widow's position in Finding Satoshi conflicts with her 2024 DL News interview. - Own analysis: the email time-zone tally is not peer-reviewed. - Bitquery's 2026 Patoshi figure is unverified.

Books (notes/2026-10-09-books.md) - The Book of Satoshi: no independent check of its transcriptions. - Only one or two reviews found for Kings of Crypto and The Blocksize War. - Bitcoin Billionaires: front matter not seen. - The Mysterious Mr. Nakamoto: its thesis is unreconciled (a team, per Kirkus, against James A. Donald, per the New York excerpt) and its subtitle is unconfirmed. - Reviews in the NYT, Economist, LRB, FT and BBC were not read. - Date conflicts: Mastering Bitcoin's first edition; the Cato Journal reviewer's name. - Reviews in WSJ, Washington Post and similar outlets may exist and were not found.

Wallets (market/2026-10-09-wallets.md) - Ballet: no audit, no patent number (its pages say both "patented" and "patent-pending"), no fee schedule, no regulatory filings. - Ledger: - Ledger Recover's price and launch date unverified. - Baton v Ledger after the 2022 remand: the hacks folder has 2025 orders, but the wallets note has not been linked to them. - Ledger's 2018 Saleem Rashid research unverified. - CryptoBilis losses still developing. - Ledger IPO status contradictory. - The alleged September 2026 sale of 471,000 Ledger records unverified. - Trezor: sources conflict on the ShipMonk breach (time window and how many affected). - Coinbase: Advanced fees, crime insurance, licences page and the NYDFS 2023 consent order PDF not obtained. - Kraken: no primary source for the 2024 CertiK incident; its master account rests on its own blog (the banking note cites the Fed database); Wyoming SPDI charter not located. - Not saved: CFTC orders (robots.txt) and SEC releases. Court copies of the same documents are saved instead.

FinCEN (legislation/us-federal-fincen.md) - 1995 Travel Rule texts not retrieved (the current CFR text is saved). - The Travel Rule $250 NPRM withdrawal has only a Unified Agenda entry. - No FBAR virtual-currency proposal was found. - Huione amendment comment deadline not captured. - Unverified: - Harmon, Vinnik and Samourai outcomes; - the CZ pardon; - the Tornado Cash delisting; - IRS Form 1099-DA; - FATF R.16; - the effect of Loper Bright. - US v Storm and the Samourai charging documents not saved. - 12 passing-mention FinCEN items are listed, not saved. - No count of crypto MSB registrants.

FinCEN wallet rule (legislation/us-federal-fincen-wallet-registration.md) - A full keyword search of the 8,274 comments was not run (rate-limited), so supporting comments may be missed. - Mixer-rule comments not retrieved. - The reason for the Spring 2024 "withdrawn" agenda entry is unknown. - The PWG quotation was not found verbatim. - The House vote count and Tillis's motion come from news. - No congressional letters retrieved. - Other state "Bitcoin rights" laws unverified.

KYC/AML for sellers and walk-in shops - NYDFS, California and CoinATMRadar blocked. - California § 3902 and NY Banking Law § 641 not saved. - Status of the federal Crypto ATM Fraud Prevention Act unknown. - No FinCEN or NMLS registry check for Bitcoin Central, Coinhub or DigitalMint. - BDCheckout after Bitcoin Depot's bankruptcy unknown. - Whether Coinme Cash counters fall under the Coinme order (our reading: no, unverified). - No Chinese-language OTC shops found in Las Vegas.

Banking (market/2026-10-09-banking.md) - The Custodia 2024 district opinion and Custodia's Supreme Court docket not found. - Kraken master-account date conflict: the Fed database says 2026-01-28, news says March 2026. - NYDFS Signature review blocked. - FDIC 790-page correspondence not saved (157 MB). - Customers Bancorp figures come from a tool reading SEC filings, not the filings themselves. - No primary source for Axos, Metropolitan's exit, Cross River's 2026 status, the Silvergate SEN closing date or Bank of America's adviser policy. - Debanking bills not checked. - The ICBA v OCC suit is news only. - Wyoming SPDI holders are inferred.

Exchanges, payment processors, merchants and the link map - Strike, Voltage, OpenNode, Binance Pay, CoinGate, Blink and IBEX Pay details missing. - Coinbase, BVNK and Mastercard pages blocked. - Licensing unconfirmed for Bitrefill, Travala, Propy and Crypto.com Pay. - El Salvador 2025 decree and IMF report not obtained. - Ashley Madison and Badoo billing pages unreadable. - Darknet revenue series beyond 2023 not obtained. - Link map: 32 home pages gave no links (blocked or JavaScript-only); "mentioned by" is a search sample, not a backlink count.

Patents (notes/2026-10-09-patents.md) - Ledger SAS patents not listed (sites blocked; the USPTO API rejected the request). - nChain: no grant/application split; Wright-named count and portfolio transfer unknown. - Malikie–MARA case number and the US 8,522,286 discrepancy. - Outcomes unknown: the US 12,032,677 re-examination, Digital Shovel, Anuwave v Coinbase, BearBox's appeal. - Mastercard's widely reported patent not identified.

Hacks (notes/2026-10-09-hacks-causes-defenses.md) - justice.gov releases blocked: Mt. Gox/Bilyuchenko, Vinnik, Bitfinex, Twitter, O'Connor, SBF, FTX SIM-swap. - Also blocked: the FBI DMM statement, the NYDFS Twitter report, Binance's 2019 notice, Coinbase's 2025 blog and 8-K. - Not located: Japan FSA and NPA documents. - Not obtained: Kaspersky CryptoShuffler and the Bitstamp report.

Technology (notes/2026-10-09-technology.md) - No gaps section. 101 BIPs without a licence line are linked, not saved.

States (detail in each us-state-XX.md and the two summaries) - Tax: state revenue-department guidance is missing for almost every state. Exceptions: AZ statutes, MO HB 594, the NJ and NY bulletins, the WA DOR statement. - Bill statuses: many final 2026 statuses rest on NCSL's tracker (last updated 2026-03-25) and are marked "final status unverified": RI, OK, NE, SC, UT, WV, NH, HI, IN and others. - Pending enforcement outcomes: - DC v Athena Bitcoin; - Washington DFI v Bitcoin Depot and CoinFlip; - Custodia's cert petition; - the Tennessee kiosk-ban suit (court and case number not found); - Oregon v Coinbase; - NJ v Coinbase (staking); - Iowa AG v Bitcoin Depot and CoinFlip; - Missouri AG v CoinFlip. - New York: later BitLicense amendments missing (only the 2015 text is saved); 2025–26 NYDFS guidance in summary only; Paxos and Genesis amounts unverified. - State-specific gaps are listed in each note: - AK, AZ, CA, GA, HI, IA and MA regulator sites were blocked; - FL: State v Espinoza not saved; - MT: SB 178 (2023) text not saved; - NM: NMSA 58-32 text not read; - VA: chapter numbers unconfirmed; - WY: kiosk rules not out yet, and two of the four SPDIs not named; - TX: reserve size and custodian not found; - the Coinme order's Puerto Rico participation is noted but not researched (PR is outside this repo's 51). - ULC trackers (URVCBA, UMSA) need JavaScript, so lineage claims for RI, LA, NM and TX are the researchers' own readings.

7.4 Checks this completeness pass did not finish

  • A claim-by-claim citation audit (§ 4.2 used sampling).
  • Re-checking the Spark's "partly supported" claims against the notes. They are listed in § 6.3, not adjudicated.
  • Splitting legislation/ into one file per bill, as the README describes (§ 4.5).