2026-04-01

Mempool Window Wide Open — UTXO Housekeeping Time

BTC at $68,362, mempool fees at 1-2 sat/vbyte. Bitcoin Core 28.4 drops with Tor PoW defenses. BIP 360, 348, and 352 all progressing. Your quarterly consolidation reminder.

Threat Level: Yellow

No immediate panic. Conservative quantum attack timeline: 10-15 years minimum. Aggressive estimates: 7-8 years. The key insight: qubit quality matters as much as count, and error correction remains a brutal engineering problem.

The real exposure right now: P2PK outputs — Satoshi's coins, early miners — where the public key is already exposed on-chain. P2PKH (standard addresses) are only vulnerable if you reuse addresses, because the public key is revealed when you spend.

We have time. But the window to coordinate a Bitcoin-wide migration is years of social consensus, not months. The research happening NOW protects 2035 Bitcoin.

Block Beat

  • BTC: $68,362 (+2.4% / 24h)
  • Market cap: $1.37 trillion
  • Volume: ~$56.7B — healthy, not euphoric
  • Mempool: Near empty. 1-2 sat/vbyte to get in next block. This is a gift.

If you've been putting off consolidating UTXOs or moving dust, THIS is your window. Historically these sub-2 sat moments don't last.

Network Health

  • Lightning Network: 42,027 channels across 17,372 nodes
  • Total capacity: 5,704 BTC
  • Tor-only nodes: 9,216 — over half the network. Privacy win.
  • Bitcoin Core 28.4: Just released. Wallet migration fixes, removed unreliable DNS seed.
  • Core Lightning 26.04rc1: Big splicing updates — cross-channel splices, multi-channel splices, dynamic fee calculation.

BIP Watch

BIP 54 (Consensus Cleanup): Getting real implementation traction. Latest Core PRs adding kernel-level integration for coinbase nLockTime constraints. This is plumbing work. Boring plumbing that matters.

BIP 348 (OP_CHECKSIGFROMSTACK): Active discussion this week. CSFS deliberately doesn't bind signatures to specific inputs, enabling re-bindable signatures — the mechanism underlying LN-Symmetry (formerly eltoo). Penalty-free LN channels if activated.

BIP 360 (Quantum-Safe Addresses): Still the one everyone's watching. Original draft proposed SPHINCS+ hash-based signatures. Migration is complex but not impossible. The hard part isn't the crypto — it's social coordination.

BIP 352 (Silent Payments): Silent payment descriptors being drafted. Performance improvements to scanning ongoing. This is the privacy primitive Bitcoin has needed for a long time.

Bitcoin Core 28.4 — What's New

  • Tor PoW defenses (#33414): When Bitcoin Core creates onion services automatically, it now enables Tor's proof-of-work defenses against DoS attacks. If you're running a manual onion service, add HiddenServicePoWDefensesEnabled 1 to your torrc.
  • AssumeUTXO telemetry (#33259): Background validation state now visible in getblockchaininfo. If you're using assumeUTXO to bootstrap faster, you can now monitor background validation progress.

Today's Lesson: The Commit-Reveal Structure

Early Bitcoin (P2PK): You published your actual public key to receive. Anyone could see it. When quantum computers are powerful enough, they could derive your private key from that public key. Satoshi's coins in P2PK outputs are already quantum-exposed.

Then came P2PKH (Pay-to-Public-Key-Hash): Instead of publishing your public key, you publish a hash of your public key. SHA-256 and RIPEMD-160 are quantum-resistant (Grover's algorithm only gives a square-root speedup, not the exponential speedup Shor's gives against ECDSA). Your public key stays hidden until you spend.

The catch: Once you spend, your public key is revealed. This is why address reuse is catastrophic in a quantum world — every reuse after the first spend re-exposes your key. One address, one spend, one reveal, then move on.

Taproot takes this further: key path spends reveal only a single aggregated key. Script path spends reveal only the executed branch of the Tapscript tree — not all possible spending conditions.

The quantum migration problem: we need a path where users can voluntarily move coins to quantum-resistant outputs before Q-Day, with a soft fork that doesn't invalidate existing coins. BIP 360 is designing exactly this migration path.

What To Do Today

  1. Consolidate UTXOs NOW — Fees are at 1-2 sat/vbyte. Open your wallet, look at your UTXO set, and merge small UTXOs into larger ones. If you have any P2PKH (legacy) outputs, migrate them to native SegWit or Taproot while fees are cheap.

  2. Update your node — Bitcoin Core 28.4 is out. Run bitcoin-cli --version and update if you're behind. Add HiddenServicePoWDefensesEnabled 1 to your torrc if running a Tor onion service.

  3. Never reuse addresses — Every address should be used exactly once. Modern wallets handle this automatically.

The window to be calm and informed is open. It won't be forever.

Stack sats. Verify everything. Build the future. ⚡️🔐🟠

Comments

💬 Comments coming soon

We're setting up community comments via GitHub Discussions. Check back shortly.