Are you a Rust newbie who found some code written in Rust and wants to dive right into the code? You're at the right place! This quick guide is supposed to help you in exactly this situation. It's not meant to be a full Rust tutorial - there are beter sources of those!
Two basic things you should know before you start:
| -----BEGIN PGP SIGNED MESSAGE----- | |
| Hash: SHA1 | |
| I hereby declare that I'm the owner of GPG key with fingerprint | |
| 3D9E81D3CA76CDCBE768C4B4DC6B4F8E60B8CF4C | |
| Which I use to sign beta-quality software. | |
| This software should be mostly usable, but was not WIDELY tested. | |
| It may contain bugs or even security vulnerabilities, as any other software. |
Bitcoin protocols using presigned transactions (e.g. Lightning Network, Firefish etc) face a problem with predicting fees of the presigned transactions. One possibility is to guess the future fee rate but that risks that the transaction will not be included in a block fast enough and it also risks wasting satoshis on fees. Another possibility is to use CPFP which may require adding more outputs - so called "anchor outputs". The drawbacks of anchor outputs are increased transaction size and potentially decreased privacy since the anchor outputs usually use "suspiciously low" amounts. Further, anchor outputs may pollute UTXO set if the presigned transaction confirms anyway (because it also had high enough fee) but the outputs are uneconomical to spend. This document proposes a new solution that could not only solve these issues but bring even more efficiency gains in the future.