Broadcast transaction packages #3859
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for your contribution to The Mempool Open Source Project. We require all contributors to agree to our Contributor License Agreement and don't seem to have one for you on file. Please see the instructions in CONTRIBUTING.md to proceed with this pull request. |
|
Looks cool! |
|
Wait. So this is not supported by the latest official Bitcoin Core 25.0? |
|
That's correct. The feature unfortunately didn't make the release. As long as |
|
Can this be used on mainnet now? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR demonstrates a possible implementation of package broadcasting. It facilitates the addition of transactions to the mempool even when their fee rate is below the minimum, as long as the total package fee rate suffices. An example of this could be a 1 sat/b lightning commitment transaction, which is time-sensitive (the parent tx), along with a high fee rate child transaction that covers the cost for the parent tx too.
According to the FAQ, mempool.space utilizes a virtually limitless mempool. In this scenario, transactions would still be accepted even if they were broadcasted individually. However, versions hosted in other locations might operate with more confined mempools. For these versions, package broadcasting might be the only technique to push a package similar to the one described above into their mempool.
To utilize this on the mainnet, it necessitates the application of this patch: bitcoin/bitcoin#27609. The discussions around the PR suggest its usage is safe.
broadcast-package.mov