Newsletters: add 321 (2024-09-20) #1901
Merged
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
vostrnad
reviewed
Sep 18, 2024
Comment on lines
40
to
146
| - [Bitcoin Core 28.0rc1][] is a release candidate for the next major | ||
| version of the predominant full node implementation. A [testing | ||
| guide][bcc testing] is available. |
There was a problem hiding this comment.
v28.0rc2 was tagged yesterday.
|
just added merge summaries |
bitschmidty
reviewed
Sep 19, 2024
| situation (see [Newsletter #271][news271 noderc]). | ||
|
|
||
| - **DNS seeding for non-IP addresses:** FIXME:virtu [posted][virtu seed] | ||
| to Delving Bitcoin a survey of the availability of seed nodes for |
There was a problem hiding this comment.
maybe
Suggested change
| to Delving Bitcoin a survey of the availability of seed nodes for | |
| to Delving Bitcoin a survey of the availability of seed nodes on |
Suggested change
| to Delving Bitcoin a survey of the availability of seed nodes for | |
| to Delving Bitcoin a survey of the availability of seed nodes for |
| She can provide the authentication token to Bob using [NFC][] or | ||
| another widely available data transfer protocol that doesn't require | ||
| Alice to access the internet, keeping the protocol simple enough to | ||
| implement even on devices with limited computing resources, like smart |
There was a problem hiding this comment.
Suggested change
| implement even on devices with limited computing resources, like smart | |
| implement, even on devices with limited computing resources, like smart |
Suggested change
| implement even on devices with limited computing resources, like smart | |
| implement even on devices with limited computing resources, like smart |
| limit was no longer sufficient to complete an Initial Block Download (IBD) | ||
| without flushing the UTXO set from RAM to disk. It was decided to remove the | ||
| limit altogether, rather than raise it, because there was no optimal value | ||
| that would be future-proof, and to give users complete flexibility. |
There was a problem hiding this comment.
It might be interesting for readers, the research Lopp did that found 25% improvement w/ no flush: bitcoin/bitcoin#28358 (comment)
| [zmn lnoff]: https://delvingbitcoin.org/t/privately-sending-payments-while-offline-with-bolt12/1134/2 | ||
| [t-bast lnoff]: https://delvingbitcoin.org/t/privately-sending-payments-while-offline-with-bolt12/1134/4 | ||
| [news271 noderc]: /en/newsletters/2023/10/04/#secure-remote-control-of-ln-nodes | ||
| [delving cluster]: https://delvingbitcoin.org/t/how-to-linearize-your-cluster/303 |
There was a problem hiding this comment.
Suggested change
| [delving cluster]: https://delvingbitcoin.org/t/how-to-linearize-your-cluster/303 | |
| [delving cluster]: https://delvingbitcoin.org/t/how-to-linearize-your-cluster/303#h-2-finding-high-feerate-subsets-5 |
| mempool][topic cluster mempool] project. See Newsletter [#315][news315 | ||
| cluster]. | ||
|
|
||
| - [Bitcoin Core #30807][] changes the signaling of a [assumeUTXO][topic |
There was a problem hiding this comment.
Suggested change
| - [Bitcoin Core #30807][] changes the signaling of a [assumeUTXO][topic | |
| - [Bitcoin Core #30807][] changes the signaling of an [assumeUTXO][topic |
|
|
||
| - [Bitcoin Core #30807][] changes the signaling of a [assumeUTXO][topic | ||
| assumeutxo] node that is syncing the background chain from `NODE_NETWORK` to | ||
| `NODE_NETWORK_LIMITED` so that peer nodes don’t request a block from it. This |
There was a problem hiding this comment.
maybe
Suggested change
| `NODE_NETWORK_LIMITED` so that peer nodes don’t request a block from it. This | |
| `NODE_NETWORK_LIMITED` so that peer nodes don’t request a historical block from it. This |
| fixes a bug where a peer would request a historical block and get no response, | ||
| causing it to disconnect from the assumeUTXO node. | ||
|
|
||
| - [LND #8981][] refactors the `paymentDescriptor` type to quarantine it within |
There was a problem hiding this comment.
Might be good to note briefly what quarantining the type means
vostrnad
reviewed
Sep 19, 2024
| development branch, so those changes will likely not be released until | ||
| about six months after the release of the upcoming version 28._ | ||
|
|
||
| - [Bitcoin Core #28358][] drops the `dbcache` limit because the previous 16GB |
There was a problem hiding this comment.
Suggested change
| - [Bitcoin Core #28358][] drops the `dbcache` limit because the previous 16GB | |
| - [Bitcoin Core #28358][] drops the `dbcache` limit because the previous 16 GB |
| - [Bitcoin Core #28358][] drops the `dbcache` limit because the previous 16GB | ||
| limit was no longer sufficient to complete an Initial Block Download (IBD) | ||
| without flushing the UTXO set from RAM to disk. It was decided to remove the | ||
| limit altogether, rather than raise it, because there was no optimal value |
There was a problem hiding this comment.
Suggested change
| limit altogether, rather than raise it, because there was no optimal value | |
| limit altogether rather than raise it, because there was no optimal value |
| that would be future-proof, and to give users complete flexibility. | ||
|
|
||
| - [Bitcoin Core #30286][] optimizes the candidate search algorithm used in | ||
| cluster linearizations, based on the framework laid out in the Section 2 of |
There was a problem hiding this comment.
Suggested change
| cluster linearizations, based on the framework laid out in the Section 2 of | |
| cluster linearizations, based on the framework laid out in Section 2 of |
azuchi
reviewed
Sep 20, 2024
| payments, and summarizes research about DNS seeding for non-IP network | ||
| addresses. Also included are our regular sections describing changes to | ||
| clients and services, announcing new releases and release candidates, | ||
| and summarizing notable changes to popular Bitcoin infrastruture |
There was a problem hiding this comment.
Suggested change
| and summarizing notable changes to popular Bitcoin infrastruture | |
| and summarizing notable changes to popular Bitcoin infrastructure |
|
Made edits for all feedback; added lede; updated releases/RCs; and reviewed other contributions. Also updated topic entries for this newsletter and also newsletters 319 and 320, which I ran out of time to do. Thanks everyone (and apologies for my tardiness)! |
bitschmidty
force-pushed
the
2024-09-20-newsletter
branch
from
5f47875 to
7bdf0d5
Compare
|
Pushed a small change to the news section. ACK topics from 321, 320, 319. Squashed. Thank you @harding @Gustavojfe @azuchi @vostrnad for contributing this week! |
bitschmidty
force-pushed
the
2024-09-20-newsletter
branch
from
7bdf0d5 to
7abc65c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Uh oh!
There was an error while loading. Please reload this page.