Pollock proposes vaults with time delays as the wrench attack antidote

Protocol (10)

• Thomas V's fraud proof scheme requires LSPs to commit UTXOs, clients to publish preimages on-chain before a deadline, and a Nostr network for clients to share commitment data.
• Gustavo notes Bitcoin Core PR #33796 adds BTCK_check_transaction endpoint. It runs context-free consensus checks on transaction structure.
• Gustavo explains PSBT v2 (BIP370) is now default in Bitcoin Core. It allows modular transaction construction, supporting adding inputs/outputs mid-process.
• BIP451 defines a DUST UTXO disposal protocol. It uses SIGHASH_ALL|ANYONECANPAY, letting anyone batch dust inputs into a single zero-value OP_RETURN output.
• Murch notes the protocol's OP_RETURN includes 'ASH'. A legacy input creates a ~65 byte transaction, while a SegWit input creates a transaction of exactly that size.
• Eclair PR #3144 updates simple taproot channels to use the official feature bit, aligning with LND's production implementation from Newsletter #401.
• Eclair PR #2887 adopts the official splicing protocol from Bolt specs. It maintains backward compatibility but upgrades wire messages, keysend, and RBF handling.
• LDK now checks for sufficient reserves before opening zero-fee commitment channels. It counts them as anchored channels to guard against simultaneous force-closes.
• LND adds a 'source_pub_key' field to route construction. This allows calculating routes from another node's perspective, not just your own.
• RustBitcoin adds a V1_message_header constructor. It lets developers build P2P message headers without requiring network transmission.

Lightning (3)

• The new 'extension bolt' Bolt 995 defines simple taproot channels. It uses MuSig2 and excludes gossip announcement specs, which will come in a follow-up.
• Zero-fee commitment channels (Bolts 1228) use a 240-sat ephemeral anchor output. The specification caps HTLCs at 114 due to the 10KB transaction size limit.
• Bolts 1327 updates RBF logic. It ensures fee bumps meet both Bolt's 25/24 multiplier and an absolute 25 sat/kwu minimum, aligning with BIP125 replacement rules.

Protocol (1)

• Pollack views quantum computing as a supply shock risk rather than an existential threat to Bitcoin, preferring a price crash over protocol changes that confiscate coins and break property rights.

Digital Sovereignty (5)

• Gerald Glickman argues the US digital identity model is fundamentally broken because it uses compromised public identifiers like Social Security numbers as secret authenticators, equivalent to using your home address as your front door key.
• Glickman advocates for a credential system where states issue verifiable credentials bound to a user's DIDs. This allows credential revocation (e.g., a driver's license) without destroying the user's foundational identity, giving control back to the individual.
• Marty Bent notes age verification laws, like the Senate Judiciary Committee's 22-0 vote on the GUARD Act, are a common Trojan horse for imposing centralized digital identity systems under the framing of protecting children.
• Glickman rejects Worldcoin's model of using biometrics as identifiers, though he approves of local device authentication like iPhone's Secure Enclave. The fight is for open systems against closed-garden solutions pushed by big tech lobbying.
• The call to action is to engage now: examine your state's mobile driver's license implementation, support open standards work at W3C or Trust over IP, and advocate for policies like Utah's SETI that embed privacy and individual control.

AI & Tech (3)

• The rise of AI and LLMs has drastically accelerated identity fraud, collapsing the half-life of new security controls. Glickman notes at least 3000 Americans become victims of identity theft every hour, a rate he calls unacceptable.
• Zero-knowledge proofs and selective disclosure enable privacy-preserving verification. A user can prove they are over 21 without revealing their birthdate, or prove they own a red hat without handing over the entire credential.
• The ideal credential flow involves an issuer crafting a signed credential bound to a public key, allowing the holder to generate a one-time, non-replayable ZK proof for a verifier. No personal information is stored or transmitted.

China (1)

• Glickman warns against using biometrics like face or fingerprints as identifiers, as they are irrevocable and will be compromised. He points to China's social credit system as a real-world example of authoritarian control enabled by such systems.

Coding (1)

• The proposed solution is using cryptography and open standards for decentralized identifiers (DIDs). This allows for cryptographic proof of authorship via digital signatures, shifting from probabilistic inference to mathematical certainty.

Protocol (2)

• Glickman believes the architectural choices made in the next 1-2 years will lock in the system for a generation. He cites accelerating state rollouts of digital driver's licenses and age verification laws as evidence of this narrow window.
• The current identity verification industry has misaligned incentives, as its business model depends on charging per verification. Glickman argues states and open standards bodies must lead, as seen with Utah's SETI legislation which includes a digital identity bill of rights.