Add support for client controlled dust limit and spent filter (cut-through) to blockchain.block.tweaks request #1
Conversation
This file contains hidden or 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
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 makes it possible to send dust limit and spent filter parameters in blockchain.block.tweaks request.
I have been working on a tweak auditing service tool. Here is a gist of the output:
dust-limit is 0 in all cases, spent filter is "true" for *-spent cases
=== Audit Results for Block 258257 ===
Services: 6/6 successful
Tweak counts by service:
blindbit: 488 tweaks
bitcoin: 488 tweaks
esplora-cake: 488 tweaks
bitcoin-spent: 399 tweaks
blindbit-spent: 374 tweaks
esplora-spent: 374 tweaks