Right now with a lot of presigned protocols (like lightning commitment transactions), you include a separate output thats small so that if you need to fee-bump the transaction you can CPFP that output. One problem with this is you need to have some funds locked up in this anchor. Another is that for something like lightning, each side needs to have an anchor. And also anchors are sort of unique and ad hoc. Instagibbs has been working on ephemeral anchors which are like a standardized 0-value anyone can spend output. So you dont have funds locked up, you only need one anchor and either party can bump it, and its composable with other protocols. The actual output is an OP_TRUE and then a little two byte tag. This release of bitcoin standardizes that output so nodes will relay those transactions. They’ve been consensus valid, but until now you would have had to hand them to a miner
Login to reply
Replies (4)
STUDY BITCOIN. BE LESS RETARDED EVERYDAY.
Right now with a lot of presigned protocols (like lightning commitment transactions), you include a separate output thats small so that if you need to fee-bump the transaction you can CPFP that output. One problem with this is you need to have some funds locked up in this anchor. Another is that for something like lightning, each side needs to have an anchor. And also anchors are sort of unique and ad hoc. Instagibbs has been working on ephemeral anchors which are like a standardized 0-value anyone can spend output. So you dont have funds locked up, you only need one anchor and either party can bump it, and its composable with other protocols. The actual output is an OP_TRUE and then a little two byte tag. This release of bitcoin standardizes that output so nodes will relay those transactions. They’ve been consensus valid, but until now you would have had to hand them to a miner
View quoted note →
So this is a step toward ephemeral anchors or just an orthoganal improvement for anchors?
Why do folks think RBF default is a good thing? I always felt it had hidden dangers.
It's fine if you don't accept 0-conf. Not running it consumes significantly more bandwidth now because 95% of miners run it so your node is constantly having to reconstruct blocks after they are mined.

GitHub
policy: enable full-rbf by default by 1440000bytes · Pull Request #30493 · bitcoin/bitcoin
This pull request enables full rbf (mempool policy) by default. #28132 was closed recently with this comment.
Rationale:
Full RBF config option ...