Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with child-pays-for-parent
Search options questions only
not deleted
user 73223
Child Pays For Parent (CPFP) is a technique for increasing the effective feerate of an unconfirmed transaction by spending one of its outputs in a high feerate transaction, encouraging miners to include both transactions in a block.
6
votes
1
answer
279
views
Why do Anchor Outputs need to enforce an nSequence of 1?
Quote from https://bitcoinops.org/en/topics/anchor-outputs:
As of this writing, the most recent versions of the design add two outputs to the commitment transaction—one for each LN party—and require …
- 713