Bitcoin Core 28.0 introduces **smarter transaction handling** to prevent stuck payments, reduce fees, and improve flexibility for wallets. Here’s a breakdown of the most important updates:

---

### 1. **One Parent One Child (1P1C) Transactions**

- **The problem**: If a transaction’s fee is too low for the current network conditions, it might never get confirmed.

- **The fix**: The new **1P1C relay** lets you attach a “child” transaction with higher fees to "push" the original "parent" transaction through. Think of it as giving the parent a boost by letting the child pay for both.

**Why it’s useful**: If your wallet creates a transaction with a low fee, you can now add another transaction to ensure it gets confirmed without waiting forever.

---

### 2. **TRUC Transactions (Version 3 Transactions)**

- **What they are**: TRUC stands for **Topologically Restricted Until Confirmation**. These transactions follow stricter rules that make them easier to replace (RBF) if needed.

- **Key features**:

- Always replaceable: TRUC transactions can always be fee-bumped or replaced, even without extra setup.

- Safe fee bumps: Even in complex setups like CoinJoins or Lightning Channels, you can adjust fees as needed.

**Why it’s useful**: Wallets using TRUC transactions can guarantee that you can always adjust fees to match changing network conditions.

---

### 3. **Pay to Anchor (P2A) Outputs**

- **What they are**: A tiny, specialized output added to transactions purely for fee adjustments. Think of it like a "placeholder" designed to let anyone pay for the transaction’s fees later.

- **How it works**: P2A outputs are super small and cheap to include, but they’re powerful because they let you boost transaction fees without needing access to private keys.

**Why it’s useful**: Helps ensure your transaction doesn’t get stuck, even if the person creating the transaction can’t afford higher fees upfront.

---

### 4. **Better Fee Replacement (Package RBF)**

- **The problem**: Previously, if you wanted to replace a stuck transaction, you had to calculate fees perfectly.

- **The fix**: With Package RBF, you can replace an entire group of transactions (parent and child) instead of just one, making it easier to adjust fees without mistakes.

**Why it’s useful**: Ensures transactions get through even in complex situations like Lightning or CoinJoins.

---

### 5. **What Does This Mean for Wallet Users?**

- **Simple Payments**: Wallets can make payments more predictable and reliable by using TRUC and P2A features.

- **Lightning Network**: Lightning transactions become more secure because stuck channel transactions can be easily bumped.

- **CoinJoins**: Privacy-focused transactions can now handle fee bumps without breaking the chain of anonymity.

---

### Summary

These updates give wallets and users more tools to handle tricky transaction scenarios, especially when network fees are unpredictable or when payments involve complex setups. Bitcoin Core 28.0 makes stuck payments a thing of the past and ensures smoother transaction processing.

Remember, these upgrades focus on **Bitcoin’s core principles: efficiency, reliability, and user empowerment**.

*READ the full OpTech info about it [here](https://bitcoinops.org/en/bitcoin-core-28-wallet-integration-guide/)*

Thanks for sharing this

Reply to this note

Please Login to reply.

Discussion

Thanks for taking the time to read! Definitely an interesting useful update.

Yea I just may update then. I’m always caution of upgrading as there is a lot of tech jargon that I don’t understand and I don’t want a Blackrock inspired upgrade

I always wait six months to upgrade to the previous last version 🙃 enough time to verify imo

Yea that’s a good idea

Can’t we just also uninstall newer and install older software (Bitcoin core)

Of course you can.

Just be careful:

- if you have a linked wallet to back it up

- older doesn’t mean it’s better so you gotta verify which compromise are you willing to take

- consensus rules evolve. Older outdated versions might cause your node to reject valid blocks or even stay in synch with the timechain

Older meaning the one I have at present but yea that’s sound advice still