-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support RBF #284
Comments
I had an interesting idea where instead of supporting RBF, we create an anyone-can-spend output on each transaction. If it lags, anyone could use child-pays-for-parent to bump its priority. Unfortunately, this doesn't work as a malicious actor could spend the output without RBF enabled. If they don't increase the fee rate, this wouldn't be an instance of CPFP, yet an honest volunteer wouldn't be able to perform CPFP due to the occupation of the output. |
mempoolfullrbf solves the above concern. If it's truly enabled by default now, it'd be the solution here. |
Resolved in above commit on the processor-smash branch. |
https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-28.0.md notes how mempoolfullrbf was enabled by default. |
Beyond needing a dedicated secondary signing loop, for re-signing a TX which has taken too long, we need to update the scheduler.
serai/processor/src/main.rs
Lines 221 to 227 in 0c9c1ae
This is the problematic block.
The text was updated successfully, but these errors were encountered: