What do the scripts look like? 👇

The proposals at a glance 👇

btcpayserver v2.4.1 (maintained by @NicolasDorier), is out with an exciting list of changes: Features: BIP329 label import added & invoices now include comments. Fixes: interrupted Boltcard payments & LNDHub not enabled by default Improvements: global search bar results

WHEW! It’s been a while but we’re excited to confirm that you’ll be hearing from us much more frequently as we have a slate of articles, features, & improvements ready to ship. We’ll leave you with a preview of an article ~coming~ soon. Any guesses on what it’s about??

Bitcoin’s P2P network has no central server. It’s a self-organizing gossip system where every node plays both student & teacher. Here’s how a node goes from zero → fully synced → keeping Bitcoin alive ⚡🌐

/9

P2A – Pay-to-Anchor Last but not least, P2A is the newest flavor & it’s quite unique. You create a special output, not to transfer value, but to *enforce structure.* It’s a “hook” which is a 0-sat ephemeral anchor that someone else can later spend in a small high-fee child tx to confirm your parent tx under v3/TRUC relay rules. But… what exactly is this? /6

CPFP - Child Pays for Parent Let’s say you receive a low-fee tx. You can spend its output in a child tx with a big fee. Miners see the combo & are incentivized to include both. Useful when the original tx isn’t RBF-enabled *&* when you’re one of the output recipients. What if you’re not though? /5

Full RBF This isn’t a new tx type, it’s a node policy. Bitcoin Core 24+ lets you enable mempoolfullrbf=1, treating every unconfirmed tx as replaceable even if it doesn’t signal opt-in RBF. /4

Opt-in RBF (BIP 125) - This is the original form. The sender sets nSequence < 0xfffffffe on inputs, marking the tx as replaceable. To be valid, the replacement tx must follow 5 rules: ✅ Higher total fee ✅ Higher fee rate ✅ Doesn’t evict >100 txs ✅ Doesn’t conflict w/ confirmed txs ✅ Shares at least 1 input /3