Newsletters: add 285 (2024-01-17) by harding · Pull Request #1468 · bitcoinops/bitcoinops.github.io

harding · 2024-01-14T21:29:32Z

Lede, releases/RCs, topic entries @harding
Bitcoin Core 29058 @adamjonas
Other merges @harding

Includes Ark topic that was previously in #1452

bitschmidty · 2024-01-15T18:11:33Z

_posts/en/newsletters/2024-01-17-newsletter.md

+    The new vulnerability was discovered by Morehouse's following up on
+    his prior work on fake funding, which he also responsibly disclosed
+    (see [Newsletter #266][news266 lnbugs]).  When re-testing nodes that
+    had implemented fixes for fake funding, was able to trigger a [race


Suggested change

had implemented fixes for fake funding, was able to trigger a [race

had implemented fixes for fake funding, he was able to trigger a [race

bitschmidty · 2024-01-15T18:15:24Z

_posts/en/newsletters/2024-01-17-newsletter.md

+    In the thread, Black and others describe some of the protocols that
+    would be enabled by this combination of consensus changes:
+    [LN-Symmetry][topic eltoo] (eltoo), [Ark][topic ark]-style
+    [joinpools][topic joinpools], reduced-signatures [DLCs][topic dlc],


Maybe?

Suggested change

[joinpools][topic joinpools], reduced-signatures [DLCs][topic dlc],

[joinpools][topic joinpools], reduced-signature [DLCs][topic dlc],

bitschmidty · 2024-01-15T18:22:01Z

_posts/en/newsletters/2024-01-17-newsletter.md

+  that combines previous proposals for [OP_CHECKTEMPLATEVERIFY][topic
+  op_checktemplateverify] (CTV) and [OP_CHECKSIGFROMSTACK][topic
+  op_checksigfromstack] (CSFS) with a new proposal for an
+  `OP_INTERNALKEY` that places the taproot internal key on the stack.


We have a good explanation of taproot internal keys here: https://bitcoinops.org/en/newsletters/2019/05/14/#complex-spending-with-taproot

Perhaps that or another resource would be helpful for reader

bitschmidty · 2024-01-15T18:31:43Z

_posts/en/newsletters/2024-01-17-newsletter.md

+  attention:
+
+    - *CPFP carve out needs to be removed:* the [CPFP carve out][topic
+      cpfp carve out] mempool policy added to Bitcoin Core in FIXME:year


2019? https://bitcoinops.org/en/newsletters/2019/07/24/#bitcoin-core-15681

bitschmidty · 2024-01-15T18:34:22Z

_posts/en/newsletters/2024-01-17-newsletter.md

+      out unless we restrict the relationships allowed between
+      transactions relayed on the network far beyond the current
+      restrictions.  A cluster with multiple carve outs could
+      significantly exceed its limits, at which point we'd need to


Maybe reword to take out "we’d"

vostrnad · 2024-01-16T00:00:51Z

_posts/en/newsletters/2024-01-17-newsletter.md

+    proposal, such as how to encode the integer value and what
+    [taproot][topic taproot] upgrade feature to use.


Could use a little more detail:

Suggested change

proposal, such as how to encode the integer value and what

[taproot][topic taproot] upgrade feature to use.

proposal such as what integer encoding to use and whether

creating a new set of arithmetic opcodes is preferred to

upgrading existing ones.

vostrnad · 2024-01-16T00:00:58Z

_posts/en/newsletters/2024-01-17-newsletter.md

+      cluster mempool is [v3 transaction relay][topic v3 transaction
+      relay], which would allow regular users of v1 and v2 transactions
+      to continuing using them in all the historically typical ways, but
+      also allow the users of contract protocols like LN to opt-in to v3


Suggested change

also allow the users of contract protocols like LN to opt-in to v3

also allow the users of contract protocols like LN to opt in to v3

vostrnad · 2024-01-16T00:01:27Z

_posts/en/newsletters/2024-01-17-newsletter.md

+  that contain more than 0 satoshis.  An ephemeral anchor pays an output
+  script equivalent to `OP_TRUE`, allowing anyone to spend it.


Suggested change

that contain more than 0 satoshis. An ephemeral anchor pays an output

script equivalent to `OP_TRUE`, allowing anyone to spend it.

that contain more than 0 satoshis. An ephemeral anchor pays to an output

script equivalent to `OP_TRUE`, allowing anyone to spend it.

Personally I'd slightly rewrite this:

Suggested change

that contain more than 0 satoshis. An ephemeral anchor pays an output

script equivalent to `OP_TRUE`, allowing anyone to spend it.

that contain more than 0 satoshis. An ephemeral anchor pays to a

standardized output script that anyone can spend.

Nice improvement, thanks!

vostrnad · 2024-01-16T00:01:31Z

_posts/en/newsletters/2024-01-17-newsletter.md

+  A proposed alternative is to put the trimmed HTLC amounts into the
+  value of the ephemeral anchor outputs.  That way they incentivize
+  confirming both the commitment transaction and a spend of the
+  ephemeral anchor output.  In his post, Sander's analyzes this


Suggested change

ephemeral anchor output. In his post, Sander's analyzes this

ephemeral anchor output. In his post, Sanders analyzes this

murchandamus

Very cool newsletter so far.

murchandamus · 2024-01-16T16:28:12Z

_posts/en/newsletters/2024-01-17-newsletter.md

+    [joinpools][topic joinpools], reduced-signatures [DLCs][topic dlc],
+    and [vaults][topic vaults] without presigned transactions, among
+    other described benefits of the underlying proposals, such as
+    CTV-style congestion control and CSFS-style signature delegation.


Ugh, congestion control is such an absurd application, I really don’t understand why people keep bringing that up.

It's still the first thing described in BIP119:

This BIP proposes a new opcode, OP_CHECKTEMPLATEVERIFY, to be activated as a change to the semantics of OP_NOP4.

The new opcode has applications for transaction congestion control and [...]

(But I also tend to think that it's impractical.)

vostrnad · 2024-01-16T18:05:09Z

_posts/en/newsletters/2024-01-17-newsletter.md

+projects.  Please consider upgrading to new releases or helping to test
+release candidates.*
+
+- [LND 0.0.119][] in a new release of this library for building


Suggested change

- [LND 0.0.119][] in a new release of this library for building

- [LDK 0.0.119][] is a new release of this library for building

Thank you @vostrnad! I just realized I missed the correction from LND to LDK.

azuchi · 2024-01-17T04:36:23Z

_posts/en/newsletters/2024-01-17-newsletter.md

+projects.  Please consider upgrading to new releases or helping to test
+release candidates.*
+
+- [LND 0.0.119][] is a new release of this library for building


Suggested change

- [LND 0.0.119][] is a new release of this library for building

- [LDK 0.0.119][] is a new release of this library for building

Oof, thank you @azuchi !

azuchi · 2024-01-17T04:36:52Z

_posts/en/newsletters/2024-01-17-newsletter.md

+[news269 rpc]: /en/newsletters/2023/09/20/#bitcoin-core-28448
+[news85 stuck]: /en/newsletters/2020/02/19/#c-lightning-3500
+[news89 stuck]: /en/newsletters/2020/03/18/#eclair-1319
+[lnd 0.0.119]: https://github.com/lightningdevkit/rust-lightning/releases/tag/v0.0.119


Suggested change

[lnd 0.0.119]: https://github.com/lightningdevkit/rust-lightning/releases/tag/v0.0.119

[ldk 0.0.119]: https://github.com/lightningdevkit/rust-lightning/releases/tag/v0.0.119

harding · 2024-01-17T06:46:55Z

Made all edits (thanks @bitschmidty @vostrnad @murchandamus @azuchi !), added lede and releases, reviewed @adamjonas contribution (thanks!), and added topic entries. Thanks everyone!

harding mentioned this pull request Jan 14, 2024

Topics: add multiple topics for Newsletter 283 #1452

Merged

bitschmidty reviewed Jan 15, 2024

View reviewed changes

vostrnad reviewed Jan 16, 2024

View reviewed changes

murchandamus reviewed Jan 16, 2024

View reviewed changes

vostrnad reviewed Jan 16, 2024

View reviewed changes

azuchi reviewed Jan 17, 2024

View reviewed changes

harding and others added 2 commits January 17, 2024 05:48

Newsletters: add 285 (2024-01-17)

3c4bcb2

NEWS285: add bitcoin core 29058

125bc7b

bitschmidty force-pushed the 2023-01-17-newsletter branch from d08e42b to 125bc7b Compare January 17, 2024 11:48

bitschmidty merged commit 36eec45 into bitcoinops:master Jan 17, 2024

This was referenced Jan 18, 2024

small spelling and grammar fixups to news285 #1475

Merged

News285: fix typo #1474

Merged

	had implemented fixes for fake funding, was able to trigger a [race
	had implemented fixes for fake funding, he was able to trigger a [race

	[joinpools][topic joinpools], reduced-signatures [DLCs][topic dlc],
	[joinpools][topic joinpools], reduced-signature [DLCs][topic dlc],

		proposal, such as how to encode the integer value and what
		[taproot][topic taproot] upgrade feature to use.

-    proposal, such as how to encode the integer value and what
-    [taproot][topic taproot] upgrade feature to use.
+    proposal such as what integer encoding to use and whether
+    creating a new set of arithmetic opcodes is preferred to
+    upgrading existing ones.

	also allow the users of contract protocols like LN to opt-in to v3
	also allow the users of contract protocols like LN to opt in to v3

		that contain more than 0 satoshis. An ephemeral anchor pays an output
		script equivalent to `OP_TRUE`, allowing anyone to spend it.

	ephemeral anchor output. In his post, Sander's analyzes this
	ephemeral anchor output. In his post, Sanders analyzes this

	- [LND 0.0.119][] in a new release of this library for building
	- [LDK 0.0.119][] is a new release of this library for building

	- [LND 0.0.119][] is a new release of this library for building
	- [LDK 0.0.119][] is a new release of this library for building

	[lnd 0.0.119]: https://github.com/lightningdevkit/rust-lightning/releases/tag/v0.0.119
	[ldk 0.0.119]: https://github.com/lightningdevkit/rust-lightning/releases/tag/v0.0.119

Conversation

harding commented Jan 14, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

murchandamus left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

vostrnad Jan 16, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

harding commented Jan 17, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

harding commented Jan 14, 2024 •

edited

Loading

vostrnad Jan 16, 2024 •

edited

Loading