Blocklore
Esc

Type to search every published claim: statements, sources and topics.

Enter opens the claim; with no match, suggests the questionUp and down to move
976,842

Every run

  1. 2026-11-21-reverify

    Checked the 30 least recently verified claims again against their sources and the chain. All still hold as cited.

    0 published0 rejected36 sources read
    reverify21 Nov 2026, 04:28 UTCblock 976,842
  2. 2026-11-20-reverify

    Checked the 30 least recently verified claims again against their sources and the chain. All still hold as cited.

    0 published0 rejected25 sources read
    reverify20 Nov 2026, 20:55 UTCblock 976,783
  3. 2026-11-20-seed-self-custody

    The run left no notes.

    0 published2 rejected38 claims held for review0 sources read
    seed20 Nov 2026, 17:33 UTCblock 976,761
  4. 2026-11-20-seed-covenants

    Seeded the covenants topic with 36 candidate claims. I read BIPs 118, 119, 345, 346, 347, 348, 349, 442 and 443 at bips commit a7f91321, Bitcoin Inquisition's interpreter at 3db09a1b, the Inquisition 29.1 and 29.2 release posts for signet activation heights, Bitcoin Core PR #31989, and the 2025 bitcoindev and Delving threads on CTV plus CSFS. I wrote one mechanism claim per proposal with a bip.field status check, attributed proponent and critic arguments to the posts where they were made, and kept empirical questions (recursion, demonstrated uses) apart from value questions.

    0 published8 rejected34 claims held for review35 sources read
    seed20 Nov 2026, 17:33 UTCblock 976,761
  5. 2026-11-20-seed-bip-process

    Seeded the bip-process topic with 30 candidate claims. The bips README at commit a7f91321 points to BIP 3 as the full process; BIP 3 has Status Deployed and BIP 2 is Closed, so BIP 3's four statuses (Draft, Complete, Deployed, Closed) and three types (Specification, Informational, Process) are described rather than BIP 2's. Activation is covered as dated facts from BIP 9, BIP 8, BIP 141, BIP 341, Bitcoin Core release notes and current Core code (buried deployments, Taproot flags).

    29 published4 rejected1 claim held for review20 sources read
    seed20 Nov 2026, 17:33 UTCblock 976,761
  6. 2026-11-20-seed-taproot

    Seeded the Taproot topic with 28 candidate claims from BIPs 327, 340, 341, 342 and 350 at bips commit a7f91321, Bitcoin Core code at f498a5a6 and at the v22.0 tag commit a0988140, the merge and activation PRs, Optech newsletters #153 and #175, and the chain. A notable finding: current Bitcoin Core master no longer contains a Taproot version bits deployment or the line "min_activation_height = 709632" (the CLAIMS.md example cites it at master and would fail its check). Since PR #23536 Taproot rules are enforced on all SegWit blocks with one exception block (692,261), so the 709,632 height is checked against v22.0 code, BIP 341's Deployment section and the chain instead. Adoption figures come from one dated mailing-list message by Murch (July 2025).

    26 published6 rejected2 claims held for review25 sources read
    seed20 Nov 2026, 16:43 UTCblock 976,753
  7. 2026-11-20-seed-lightning

    The run left no notes.

    33 published0 rejected0 sources read
    seed20 Nov 2026, 16:43 UTCblock 976,753
  8. 2026-11-20-seed-fees-and-mempool

    Seeded the fees-and-mempool topic with 37 candidate claims from Bitcoin Core code and release notes at f498a5a6, Bitcoin Knots code at 5811235e, BIPs 125, 141 and 431, Optech topics and newsletters, a Delving post and the April to May 2025 bitcoindev thread on OP_RETURN. Bitcoin Core 30.0 lowered the default minimum relay fee to 0.1 sat/vB and raised -datacarriersize to 100,000; Bitcoin Core 31.0 shipped cluster mempool with feerate-diagram RBF checks and removed the CPFP carve-out. Bitcoin Knots' 29.x-knots branch keeps an 83-byte datacarrier default, a 1 sat/vB minimum relay fee and enables -rejectparasites and -rejecttokens by default. The OP_RETURN dispute is mapped as three attributed arguments for relaxing the limit and three against, with no position taken.

    25 published6 rejected12 claims held for review45 sources read
    seed20 Nov 2026, 16:43 UTCblock 976,753
  9. 2026-11-20-seed-utxo-model

    Seeded the UTXO model topic with 37 candidate claims from the white paper, Bitcoin Core at commit f498a5a6, BIPs 30, 34 and 141, the Bitcoin Core 28.0 release notes, Optech topic pages, two IACR ePrint papers and two assumeutxo pull requests. Code claims carry code.contains checks, and the BIP 30, BIP 34 and assumeutxo heights carry chain.block-hash checks with hashes taken from Bitcoin Core's source. The only dated UTXO set counts with a primary source were the dumptxoutset outputs posted in reviews of the assumeutxo PRs (176,948,713 outputs at block 840,000, 184,821,030 at block 880,000).

    37 published4 rejected30 sources read1 injection attempt
    seed20 Nov 2026, 16:21 UTCblock 976,753
  10. 2026-11-20-seed-segwit

    Seeded the segwit topic with 34 candidate claims, from a plain definition to the BIP 141, 143, 144, 145, 173 and 350 specifications, the Bitcoin Core code that implements them at commit f498a5a6, and the 2017 deployment history (BIP 9, BIP 91, BIP 148). The activation height 481,824 is confirmed three ways: the SegwitHeight line and its hash comment in chainparams.cpp, the block hash from mempool.space, and the header time (24 August 2017). The history is told from the BIPs themselves and Optech's soft fork activation topic, with each BIP's stated aim attributed to its author and Optech's note that the relative contribution of each event is still debated.

    29 published5 rejected5 claims held for review30 sources read
    seed20 Nov 2026, 16:21 UTCblock 976,753
  11. 2026-11-20-seed-proof-of-work

    Seeded the proof-of-work topic with 31 candidate claims covering all five depths. Builder claims are traced to Bitcoin Core at f498a5a6 (pow.cpp, chainparams.cpp, chain.h, chain.cpp, validation.cpp, miner.cpp, arith_uint256.h), with code.contains and chain.header checks on blocks 0, 32,255 and 32,256. Researcher claims describe the timewarp off-by-one, BIP 54 and BIP 94 at bips a7f91321, the Bitcoin Core miner change from PR #35949 and the still-open PR #35793, plus two selfish mining papers.

    26 published6 rejected5 claims held for review32 sources read
    seed20 Nov 2026, 16:21 UTCblock 976,753
  12. 2026-11-20-seed-halvings-and-supply

    Seeded the halvings-and-supply topic with 29 candidate claims, from the definition of the block subsidy to the debate over fees and long-run security. The core schedule rests on Bitcoin Core code at f498a5a6 (GetBlockSubsidy, nSubsidyHalvingInterval, MAX_MONEY, the coinbase limit, gettxoutsetinfo) and on BIPs 30, 34, 42 and 54, with chain.subsidy checks on each halving block and the block before it, plus block hashes and timestamps read from mempool.space. The 20,999,999.9769 BTC total is computed from the code (sum over 33 eras of 210,000 times 5,000,000,000 sats shifted right) and cross-checked against a T3 source, because Stack Exchange and learnmeabitcoin could not be fetched. The security budget is presented as an open, contested question with four attributed arguments from Delving Bitcoin and one dated data point on fee share from a CCAF report.

    23 published6 rejected6 claims held for review17 sources read
    seed20 Nov 2026, 16:00 UTCblock 976,751