Skip to content

Newsletters: add 281 (2023-12-13) #1428

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.

Sign up for GitHub

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

Merged
bitschmidty merged 4 commits into from
Dec 13, 2023
Merged

Newsletters: add 281 (2023-12-13) #1428

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
5d536b1
Newsletters: add 281 (2023-12-13)
harding Dec 10, 2023
d125efd
News281: add services and client software section
bitschmidty Dec 11, 2023
82072ea
News281: add stack exchange
bitschmidty Dec 11, 2023
c35249e
News281: Add more BSE topics
murchandamus Dec 11, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
News281: add stack exchange
  • Loading branch information
@bitschmidty
bitschmidty committed Dec 13, 2023
commit 82072eaa3c3271109f36ba1da594e756f505cd4c
23 changes: 22 additions & 1 deletion _posts/en/newsletters/2023-12-13-newsletter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,7 +96,25 @@ answers posted since our last update.*
nswer -->{% endcomment %}
{% assign bse = "https://bitcoin.stackexchange.com/a/" %}

FIXME:bitschmidty
- [What are all the rules related to CPFP fee bumping?]({{bse}}120853)
Pieter Wuille points out that contrary to the [RBF][topic rbf] fee bumping
technique that has a list of associated policy rules, the [CPFP][topic cpfp]
fee bumping technique has no additional policy rules.
Copy link
Collaborator

@LarryRuane LarryRuane Dec 12, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't a comment on the PR here, but mention of "policy" reminds me that recently I saw a useful distinction that I wasn't aware of, it may have been in a Murch tweet (sorry, post on X). Transaction "standardness" relates to properties of a single transaction considered in isolation; "policy" involves multiple transactions (ancestor and descendant counts, for example). Previously, I had thought of these two words as somewhat interchangeable. Just thought I'd pass that along in case others here weren't aware of those definitions!

Copy link
Collaborator Author

@harding harding Dec 13, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think that's quite right. I agree that standardness relates to the properties of a single transaction (inclusive of its prevouts), but I consider policy to be a superset of standardness rules that also includes all other rules related to whether a node will accept a transaction into its mempool and relay it. I think this is evidenced by IsStandard() and IsStandardTx being defined in policy.*.


- [How is the total number of RBF replaced transactions calculated?]({{bse}}120823)
Murch and Pieter Wuille walk through some examples of RBF replacements in the
context of [BIP125][]’s rule 5: “The number of original transactions to be
replaced and their descendant transactions which will be evicted from the
mempool must not exceed a total of 100 transactions”. Readers may also be
interested in the [Add BIP-125 rule 5 testcase with default
mempool][review club 25228] PR Review Club meeting.

- [What types of RBF exist and which one does Bitcoin Core support and use by default?]({{bse}}120749)
Murch provides some of Bitcoin Core’s transaction replacement history and in a
[related question]({{bse}}120773), a summary of RBF replacement rules and
links to Bitcoin Core’s [Mempool Replacements][bitcoin core mempool
replacements] documentation and one developer's ideas for [RBF
improvements][glozow rbf improvements].

## Releases and release candidates

Expand Down Expand Up @@ -171,3 +189,6 @@ newsletter. Regular publication will resume on Wednesday, January 3rd.
[envoy v1.4.0]: https://github.com/Foundation-Devices/envoy/releases/tag/v1.4.0
[bbqr github]: https://github.com/coinkite/BBQr
[zeus v0.8.0]: https://github.com/ZeusLN/zeus/releases/tag/v0.8.0
[review club 25228]: https://bitcoincore.reviews/25228
[bitcoin core mempool replacements]: https://github.com/bitcoin/bitcoin/blob/master/doc/policy/mempool-replacements.md
[glozow rbf improvements]: https://gist.github.com/glozow/25d9662c52453bd08b4b4b1d3783b9ff