Bump fee having an easier time with "preserve payment" than "decrease payment"
Open
Nobody has claimed this yet.
topic-wallet 👛
- Dominant language
- Python
- Stars
- 8.6k
- Forks
- 3.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 61
Description
This seems backward since to preserve the output you might need to add inputs.
The error message isn't clear what it's about. This was a made up CPFP from two unconfirmed output.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported CPFP case with two unconfirmed outputs and compare the "preserve payment" and "decrease payment" fee-bump paths. Trace the code that selects inputs and produces the error message; done means the behavior is consistent with the intended payment-preservation semantics and the error clearly explains the failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100