OPENSATS RECEIVES DONATION FROM @BITWISE BITCOIN ETF OpenSats is grateful for recurring support from Bitwise as part of their pledge to donate 10% of profit. These funds will be sent to open source contributors globally using bitcoin. We take no cut. opensats.org/blog/opensats-…

I’ve been running a Taproot script-path scanner over mainnet blocks, and one interesting pattern stood out: script-path event load changed dramatically over time. Roughly three phases appear in the data: • pre-780k: almost no script-path activity • 780k–820k: large spike •

Taproot is deployed, but the developer stack around it is still missing. Taproot is complete as a protocol, but incomplete as a developer ecosystem. Three layers are still underdeveloped: • debugging & measurement tools • script engineering knowledge • playground

OP_CAT is running on-chain (Signet). Built a split-preimage Taproot contract using Bitcoin Inquisition and btcaaron. The experiment walks through: • commit → reveal lifecycle • witness stack execution • Taproot address reconstruction Full write-up: medium.com/@aaron.recompi…

OP_CHECKTEMPLATEVERIFY running on-chain (Signet). Built a minimal CTV Taproot contract using Bitcoin Inquisition and btcaaron. The experiment demonstrates: • lock outputs at UTXO creation time • empty witness — the tx proves itself • no RBF, CPFP is the only fee path Series

What I cannot execute, I do not understand.

He doesn’t invent new rules. He finds where existing rules accidentally overlap.

I’ve been exploring a simple question: 👉 what exactly does a Bitcoin signature verify? Ran a small experiment comparing: - CSFS - IK + CSFS - CHECKSIG Observation: Same opcode family, different binding surface. Full discussion (Delving Bitcoin):

Nice to see the CTV+CSFS thread included in this week’s Bitcoin Dev Project TLDR. What matters most to me is that experiment-driven discussion is making it into the conversation. Bitcoin Dev Project

OP_CAT + OP_CHECKSIGFROMSTACK on Signet — Dynamic Message, Oracle Authorization Previous experiment: IK + CSFS asks: did the owner sign this? This one asks: did the oracle sign what the stack assembled? New write-up here: medium.com/@aaron.recompi… #BTC

Sign once. Spend twice. Same witness, different UTXO — both confirmed on-chain. BIP 118 (SIGHASH_ANYPREVOUT) on Bitcoin Signet: the preimage diff, the 0x01 prefix, and why this is the foundation of Eltoo. 👉 medium.com/@aaron.recompi…

Two Delving posts this week on APO + signet: Independent Python BIP 118 sighash — rebinding proof: one signature spent two different UTXOs, same witness, both confirmed in block 298,280 Three-round Eltoo state chain: APO updates + CTV settlement, six txids on Inquisition signet

Quick question: In tapscript, 0xB3 shows up as OP_NOP4. Anyone knows what this is actually reserved for? 👀