Newsletters: add 89 (2020-03-18) #372

harding · 2020-03-16T03:11:38Z

Services/Clients section @bitschmidty
LND #3821 @dongcarl

Another short one this week.

adamjonas

Very small nit. Looks good otherwise.

adamjonas · 2020-03-16T12:46:52Z

_posts/en/newsletters/2020-03-18-newsletter.md

+- [Bitcoin Core #16902][] changes consensus code to fix an inefficiency
+  in the parsing of `OP_IF` and related opcodes.  In legacy and segwit
+  v0 script, the inefficiency isn't believed to cause any significant
+  problems, but the proposal for [tapscript][topic tapscript] would


This sentence is a couple of ideas. Suggest breaking it up.

Suggested change

problems, but the proposal for [tapscript][topic tapscript] would

problems. Still, the proposal for [tapscript][topic tapscript] would

dongcarl · 2020-03-16T21:15:55Z

An attempt:

LND #3821 adds anchor commitments for LN channels and enables it by default if both participating nodes of a channel signal support. Anchor commitment transactions can be fee bumped unilaterally by either party, which is useful because commitment transactions might be broadcast a long time after they commit to their on-chain feerate. See the "Anchor outputs" topic for more details.

harding · 2020-03-17T09:43:09Z

@dongcarl LGTM, thanks! Added to the newsletter as written except that I removed the last sentence and placed its link in the first sentence (without otherwise editing that sentence).

Also ACK @bitschmidty's section. Thanks!

jnewbery

Just a couple of small comments inline, plus one question (already asked in IRC):

https://github.com/bitcoinops/bitcoinops.github.io/pull/372/files#diff-96058f7a7c88130ae0773bd17e1a4dc3R39 links to the scaling book before we've announced it. Is everyone ok with that? If so, should we remove https://bitcoinops.org/en/scaling/fee-bumping/ until I've fixed the todos?

jnewbery · 2020-03-17T13:58:40Z

_posts/en/newsletters/2020-03-18-newsletter.md

+  inefficiency now reduces the number of changes that need to be made in the
+  proposed schnorr, taproot, and tapscript soft fork.  For more
+  information, see the Bitcoin Core PR Review Club [meeting notes][club
+  #16902] about this PR and a [related PR][Bitcoin Core #18002] also


I parsed this sentence as "see (the Review Club meeting about this PR) and a related PR" instead of "see the Review Club meeting about (this PR and a related PR)". I suggest removing "and a related PR also merged this week". I don't think it's critical information that the Review Club also covered another refactor PR.

jnewbery · 2020-03-17T14:03:01Z

_posts/en/newsletters/2020-03-18-newsletter.md

+  merged this week.
+
+- [LND #3821][] adds [anchor commitments][topic anchor outputs] for
+  LN channels and enables it by default if both participating nodes of a


I'm not sure 'it' is correct here. It refers to "anchor commitments" which is plural, so suggests to me that we should use 'them'. Alternatively, "LND 3821 implements anchor commitments for enables this feature for new LN channels by default ..." or similar

Agree, was about to suggest s/it/this feature/

jnewbery · 2020-03-17T14:27:32Z

Pushed a commit to link to the github version of the scaling book

jonatack

Good newletter @harding! A few comments below. Question: what plans for the review club feature (and frequency)? Last week's coin selection sessions were well-attended and some interesting ideas generated.

jonatack · 2020-03-17T16:04:13Z

_posts/en/newsletters/2020-03-18-newsletter.md

+generating a single onchain transaction, multiple payments will be
+[combined into a single transaction][scaling payment batching] once every 10 minutes.
+
+- **Bitstamp supports bech32:** Bitstamp users can now benefit from using native


Perhaps hoist "deposits and withdrawals" to the bitstamp title for clear quick comparison to the derebit title while skim reading.

jonatack · 2020-03-17T16:17:36Z

_posts/en/newsletters/2020-03-18-newsletter.md

+[news85 ln stuck]: /en/newsletters/2020/02/19/#c-lightning-3500
+[coinbase batching blog]: https://blog.coinbase.com/coinbase-rolls-out-bitcoin-transaction-batching-5f6d09b8b045
+[bitstamp bech32 blog]: https://www.bitstamp.net/article/weve-added-support-bech32-bitcoin-addresses-bitsta/
+[deribit bech32 withdrawal tweet]: https://twitter.com/DeribitExchange/status/1234904442169851909


Tried to find a better link for this on deribit's blog but it seems to be down currently (which surely explains why the tweet is being used here instead).

There wasn’t anything on the blog when I looked (and it was up)

jonatack · 2020-03-17T16:21:10Z

_posts/en/newsletters/2020-03-18-newsletter.md

+  merged this week.
+
+- [LND #3821][] adds [anchor commitments][topic anchor outputs] for
+  LN channels and enables it by default if both participating nodes of a


Agree, was about to suggest s/it/this feature/

jonatack · 2020-03-17T16:28:06Z

_posts/en/newsletters/2020-03-18-newsletter.md

+
+- [LND #3821][] adds [anchor commitments][topic anchor outputs] for
+  LN channels and enables it by default if both participating nodes of a
+  channel signal support. Anchor commitment transactions can be fee


Looked at the changeset to verify that anchor commitments are auto-enabled if both participants signal support"; comment and code seems to be here, lines 1114-1126: https://github.com/lightningnetwork/lnd/pull/3821/files#diff-691ca64693e704fd2e5080998f3e640eR1114

jonatack · 2020-03-17T16:32:34Z

_posts/en/newsletters/2020-03-18-newsletter.md

+  commit to their on-chain feerate.
+
+- [LND #3963][] adds detailed [documentation][lnd op safety] about how
+  to use LND safely.


This looks like a PR of truly high value to users that might be worth a bit more pizzazz here. FWIW I like the name "lnd Operational Safety Guidelines".

jonatack · 2020-03-17T16:39:24Z

_posts/en/newsletters/2020-03-18-newsletter.md

+- [LND #3963][] adds detailed [documentation][lnd op safety] about how
+  to use LND safely.
+
+- [Eclair #1319][] implements the same solution as described in


ISTM the PR title or a short description could be useful here, e.g. Eclair #1319 "Funder reserve for future fee increase" or descriptive equivalent, before writing that it is the same solution as described in Newsletter #85.

jonatack · 2020-03-17T16:41:23Z

_posts/en/newsletters/2020-03-18-newsletter.md

+  inefficiency now reduces the number of changes that need to be made in the
+  proposed schnorr, taproot, and tapscript soft fork.  For more
+  information, see the Bitcoin Core PR Review Club [meeting notes][club
+  #16902] about this PR and a [related PR][Bitcoin Core #18002] also


jonatack · 2020-03-17T16:51:11Z

(verified the links so far as well)

jnewbery · 2020-03-17T17:51:29Z

@jonatack

Question: what plans for the review club feature (and frequency)?

Plan is one per month, on the second week, with a summary of the most interesting discussion over the previous month's meetings.

That gives the following schedule:

1st week: no special section
2nd week: Bitcoin Core PR Review Club
3rd week: Changes to services and client software
4th week: Selected Q&A from Bitcoin StackExchange

Let me know if you want to write some of the Bitcoin Core PR Review Club sections.

jonatack · 2020-03-23T22:20:22Z

Plan is one per month, on the second week, with a summary of the most interesting discussion over the previous month's meetings.

Let me know if you want to write some of the Bitcoin Core PR Review Club sections.

Sure 👍

jnewbery mentioned this pull request Mar 16, 2020

[DO NOT MERGE] Test Travis #373

Closed

adamjonas reviewed Mar 16, 2020

View reviewed changes

jnewbery added the newsletters Publishing/translating/editing newsletters label Mar 16, 2020

jnewbery reviewed Mar 17, 2020

View reviewed changes

jonatack reviewed Mar 17, 2020

View reviewed changes

harding and others added 3 commits March 18, 2020 06:42

Newsletters: add 89 (2020-03-18)

e45a31a

news89: add client services section

ab215f8

News89: add description for LND 3821

12a854c

bitschmidty force-pushed the 2020-03-18-newsletter branch from ddd689a to 12a854c Compare March 18, 2020 11:48

bitschmidty merged commit e1551aa into bitcoinops:master Mar 18, 2020

	problems, but the proposal for [tapscript][topic tapscript] would
	problems. Still, the proposal for [tapscript][topic tapscript] would

Newsletters: add 89 (2020-03-18) #372

Newsletters: add 89 (2020-03-18) #372

Uh oh!

Conversation

harding commented Mar 16, 2020 • edited by bitschmidty Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

adamjonas left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

dongcarl commented Mar 16, 2020

Uh oh!

harding commented Mar 17, 2020

Uh oh!

jnewbery 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!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jnewbery commented Mar 17, 2020

Uh oh!

jonatack 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!

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!

jonatack commented Mar 17, 2020

Uh oh!

jnewbery commented Mar 17, 2020

Uh oh!

jonatack commented Mar 23, 2020

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

harding commented Mar 16, 2020 •

edited by bitschmidty

Loading