Lightning Network Anchor Outputs Explained: The Basics (Part 1)

Welcome back, and thank you for being here to learn with me.This is Part 2 of my ongoing series where I dive deeper into Lightning Network anchor outputs and share what I'm figuring out as I go Welcome Back In Part 1 , we covered the basic problem: pre-signed Lightning commitment transactions can have outdated fees by the time you need to broadcast them. Anchor outputs solve this by letting you boost fees later using CPFP (Child Pays For Parent). Today, we're going deeper. We're answering the "why" and "how" questions that make anchor outputs actually work. What we're covering in Part 2: How CPFP really works (the mechanics) Why 330 sats? (The magic number explained) The one-block delay (CSV) and why it's crucial What happens to your other outputs Real-world examples with actual numbers Let's dive in. CPFP Mechanics: How Does This Actually Work? In Part 1, we learned that CPFP means "Child Pays For Parent." But let's understand the mechanics of HOW this works at the Bitcoin protocol le