Mempool policy
summary
Claim: mempool policy functions as Bitcoin's administrative state, shifting rule-making out of consensus into node defaults. Examples: CPFP carve-outs and package-relay workarounds address pinning attacks and pre-signed Lightning fee bumps; cluster mempool reduces some failures. Timeline shows development gaps (most soft forks since 2011 come from Pieter Wuille; only two soft-fork activations proposed since 2016) and many policy tweaks that can silently break channels, favoring complexity as advantage for experts over plain rules.
AI-written summary · about
chapters (10)
- 0:00Mempool policy basics
- 1:49Ossification in Bitcoin
- 4:57Mempool vs administrative state
- 11:56Bitcoin must stay changeable
- 13:43Consensus vs mempool policy
- 15:28Layer 2 policy complexity
- 18:55Policy changes bypass debate
- 20:59BIP 9 transparency decline
- 22:24Anti-fragile decision-making
- 23:28Q&A
related talks
12mAccelerating Bitcoin
59mLightning Scaling Challenges
41mEverything I know about Routing Reliability and Liquidity on the Lightning Network
50mSecurity Aspects of Lightning Network Routing
14mPolicyCache: Intra-flow Learning in Congestion Control
07mSolver Infrastructure
17mUnlocking ECMP Programmability for Precise Traffic Control
01h 04mHashpools One Year Development Update
