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

Published

0 claims

None.

Held for the owner

Their text stays private until the owner approves it.

  • 34 claims on covenants

    contested topic; an argument; names Christian Decker, Anthony Towns; contested subject; contested status; names Anthony Towns; names James O'Beirne, Matt Corallo; names Antoine Poinsot, Greg Sanders; names Matt Corallo; names Antoine Poinsot; names ZmnSCPxj; names Steven Roose; names Olaoluwa Osuntokun; names Ethan Heilman, Armin Sabouri; names Brandon Black, Jeremy Rubin; names James O'Beirne; names moonsettler; a stance

Rejected

8 candidates

  • (covenants.open-demonstrated-demand: withheld, it touches a gated subject)

    verifier: The question as framed is partly answered by sources in this same run, so it is not an honest open question. Steven Roose's Delving post (cited by covenants.argument-roose-first-step) says "Very limited vaults have been built with CTV", linking a working implementation. A search also found an April 2026 mailing-list report of an LN-Symmetry-style state chain run on Inquisition signet (with APO and CTV, not CSFS), which I could not verify. "Critics say" generalizes one person, Antoine Poinsot, who also wrote that he is sympathetic to a CTV+CSFS soft fork. And whether a demonstration is "proper" is partly a judgment that "published implementations on signet" would not settle. A narrower question, for example whether LN-Symmetry built with CTV and CSFS has been implemented and published as of a date, would need fresh research.

  • (covenants.open-empirical-and-value: withheld, it touches a gated subject)

    verifier: This is Blocklore's own classification of the debate, not a claim any cited source makes. None of the sources says which questions are empirical and which are values that "data cannot settle". Towns, ZmnSCPxj and Poinsot/Sanders each argue a position. The ZmnSCPxj point about fungibility is partly empirical, so the value label is debatable. The claim is also not a question with stated resolution criteria, which the open-question kind requires (CLAIMS.md). Its one empirical example, CTV plus CSFS permitting a recursive covenant, is already shown by Towns' construction and covered by covenants.argument-ctv-csfs-recursion. Under EDITORIAL.md, empirical and value markings belong on debate-map nodes, not in a claim in the brain's voice.

  • Recursive covenants could create miner extractable value beyond simple transaction selection.

    research: Optech

  • The December 2024 wiki poll of developer opinions on covenant proposals.

    research: A poll is evidence only of itself; Optech reports no results, and I did not read the wiki page, so it would add little.

  • Shinobi's 2022 concern that recursive covenants threaten censorship resistance or fungibility.

    research: Only Optech's one-line summary was available; the primary message could not be fetched.

  • Bitcoin Core does not implement any of these opcodes as of commit a690300e.

    research: An absence cannot be expressed as a code.contains check and I did not search the tree.

  • Proponent-use claims for OP_CHECKCONTRACTVERIFY and OP_TXHASH comparable to the other proposals.

    research: Out of budget for this run; BIP 443 motivation and BIP 346 motivation should be read for attributed use claims (equal care gap).

  • The 2022 attempt to activate CTV through a Speedy Trial client.

    research: Not researched in this run; needs the 2022 mailing-list primaries.

Could not settle

  • Where Bitcoin Inquisition defines INQ_DEPLOYMENTS_SIGNET (the signet deployment parameters). Finding the header would let the signet claims carry code.contains checks instead of resting on release posts.
  • Whether any Bitcoin Inquisition release after 29.2 (7 February 2026) adds OP_CHECKCONTRACTVERIFY, OP_TXHASH or OP_PAIRCOMMIT on signet. A newer release post or the 29.x branch would settle it.
  • Whether the CTV + CSFS letter or later posts proposed specific activation parameters, and whether the August 2025 workshop series produced published outcomes.
  • Corallo's later replies (for example 01f49d64-838e-4311-bf79-8c4130b40c8e@mattcorallo.com) to O'Beirne's TXHASH response were not read; they would show how that exchange continued.

Injection attempts

No text in any source this run read tried to give the brain orders.

Read

35 sources