Newsletters: add 344 (2025-03-07) #2211
Conversation
| - **Disclosure of fixed LND vulnerability allowing theft:** Matt | ||
| Morehouse [posted][morehouse failback] to Delving Bitcoin to announce | ||
| the [responsible disclosure][topic responsible disclosures] of a | ||
| vulnerability that affected LND versions before 0.18. Upgarding to |
There was a problem hiding this comment.
| vulnerability that affected LND versions before 0.18. Upgarding to | |
| vulnerability that affected LND versions before 0.18. Upgrading to |
| update the specification. | ||
|
|
||
| - **Discussion about Bitcoin Core's priorities:** several blog posts | ||
| written by Antoine Poinsot about the future of the Bitcoin Core |
There was a problem hiding this comment.
| written by Antoine Poinsot about the future of the Bitcoin Core | |
| by Antoine Poinsot about the future of the Bitcoin Core |
| written by Antoine Poinsot about the future of the Bitcoin Core | ||
| project were linked in a [thread][poinsot pri] on Delving Bitcoin. In | ||
| the [first][poinsot pri1] blog post, Poinsot describes the benefits of | ||
| long-term goal setting and the costs of ad hoc decision making. In |
There was a problem hiding this comment.
| long-term goal setting and the costs of ad hoc decision making. In | |
| long-term goal setting and the costs of ad hoc decision-making. In |
| tightly coupled. Many changes to one project would require also | ||
| making changes to the other projects. However, it would be a clear |
There was a problem hiding this comment.
| tightly coupled. Many changes to one project would require also | |
| making changes to the other projects. However, it would be a clear | |
| tightly coupled. Many changes to one project would also require | |
| changes to the other projects. However, it would be a clear |
| making changes to the other projects. However, it would be a clear | ||
| win to move features that don't currently require a node into a | ||
| library or tool that can be maintained independently. He also |
There was a problem hiding this comment.
| making changes to the other projects. However, it would be a clear | |
| win to move features that don't currently require a node into a | |
| library or tool that can be maintained independently. He also | |
| making changes to the other projects. However, | |
| moving features that don't currently require a node into a | |
| library or tool that can be maintained independently would be a clear win. He also |
There was a problem hiding this comment.
Leaving as-is. The motivation for this change is unclear to me.
| - **Trusted block templates:** a miner connects to a marketplace, selects | ||
| the bids it wants to include in a block, and asks the marketplace to | ||
| construct a block template. The marketplace responds with a block | ||
| header, coinbase transaction, and partial merkle branch that allow |
There was a problem hiding this comment.
| header, coinbase transaction, and partial merkle branch that allow | |
| header, coinbase transaction, and partial merkle branch, allowing |
There was a problem hiding this comment.
Keeping as-is. I think both constructions are correct and the existing construction avoids the use of a comma shortly after a comma-delimited list, making the sentence easier to skim.
| transaction to the marketplace, which verifies the proof of work, | ||
| adds it to the block template, and | ||
| broadcasts the block. The marketplace might include a transaction | ||
| paying the miner in the block template or it might pay the miner |
There was a problem hiding this comment.
| paying the miner in the block template or it might pay the miner | |
| paying the miner in the block template, or it might pay the miner |
There was a problem hiding this comment.
Keeping as-is. "It might pay" doesn't make sense here as an independent sentence, therefore it's not an independent clause, therefore this is a simple conjunction.
| [TEE][] secure enclave, connect to marketplaces and select bids they | ||
| want to include in their blocks, and receive the transactions in | ||
| those bids encrypted to the TEE's enclave key. The block template | ||
| is constructed within the TEE and it provides the host operating |
There was a problem hiding this comment.
| is constructed within the TEE and it provides the host operating | |
| is constructed within the TEE, and provides the host operating |
| provides it to the TEE, which verifies it and returns the full | ||
| decrypted block template for the miner to add to the header and broadcast. Again, the block | ||
| template might include a transaction paying the miner from a UTXO | ||
| belonging to the marketplace or the marketplace might pay the miner |
There was a problem hiding this comment.
| belonging to the marketplace or the marketplace might pay the miner | |
| belonging to the marketplace, or the marketplace might pay the miner |
There was a problem hiding this comment.
Same comment as above: #2211 (comment)
| belonging to the marketplace or the marketplace might pay the miner | ||
| later. | ||
|
|
||
| Both schemes would effectively require there to be multiple competing |
There was a problem hiding this comment.
| Both schemes would effectively require there to be multiple competing | |
| Both schemes would effectively require multiple competing |
| brings the [BOLT12][] parameter setting in line with that of [BOLT11][]. | ||
|
|
||
| - [Rust Bitcoin #4114][] lowers the minimum non-witness transaction size from 85 | ||
| bytes to 62 bytes, aligning with Bitcoin Core’s policy (see Newsletter |
There was a problem hiding this comment.
I think this "62" is a typo that should be "65". Will make that change.
|
Made edits for all feedback, thanks @LarryRuane ! Added lede, updated releases/RCs, added topic entries. Skipped adding a MEV topic page but added it to #721 (comment) . Reviewed and made some small edits to @Gustavojfe section (thanks!). Thanks everyone! |
bitschmidty
force-pushed
the
2025-03-07-newsletter
branch
from
f77ab6b to
8bc7072
Compare
|
Didnt have a chance to review fully this week, just a skim, but looks great and will have to come back. Squashed |
(Optional) Topic page about MEV @harding