News: add 70 (2019-10-30) #248
Conversation
| ## News | ||
|
|
||
| - **LN simplified commitments:** in two separate threads, developers | ||
| from LND discussed their work on implementing simplified commitments, |
There was a problem hiding this comment.
'developers from Lightning Labs' or 'developers of LND' (Lightning Labs is the company, LND the product)
There was a problem hiding this comment.
That's an important distinction, thank you for mentioning it. I'll edit.
|
Pushed edit for @jnewbery feedback (thanks!), added a bullet for the Optech schnorr/taproot workshop, and added a short sentence and link to the PR for the LN simplified commitment previously described. |
| notebooks, GitHub repositories, and more information produced for the | ||
| schnorr and taproot workshops held in San Francisco and New York | ||
| City last month. These explain the fundamentals of both proposals, | ||
| guide students though actually using them, and then describe strategies |
There was a problem hiding this comment.
/students though/students through/
|
One typo, otherwise ACK 19d5e93 |
harding
force-pushed
the
2019-10-30-newsletter
branch
from
19d5e93 to
b6886ac
Compare
|
Rebased on master to pull in the schnorr/taproot blog post, updated link to point to it, added C-Lightning release, and fixed typo identified by @jnewbery (thanks!). All FIXMEs fixed now, so this should pass tests. |
| and allows you keep your HD wallet seed encrypted when `lightningd` | ||
| isn't running---plus many other features and several bug fixes. | ||
|
|
||
| - **Help Bitcoin Core release candidate:** experienced users are encouraged to |
There was a problem hiding this comment.
Should this be 'Help test Bitcoin Core release candidate'?
There was a problem hiding this comment.
Agree. Perhaps "Help test the Bitcoin Core release candidate:"
| ## Action items | ||
|
|
||
| - **Upgrade to C-Lightning 0.7.3:** this latest [release][c-lightning | ||
| 0.7.3] adds support for a PostgresSQL backend, makes it possible to |
There was a problem hiding this comment.
s/PostgresSQL/PostgreSQL/
There was a problem hiding this comment.
possibly worth mentioning "in addition to SQLite3" (IIRC)
There was a problem hiding this comment.
Thanks for catching that. A note for anyone else reviewing: this is wrong in the C-Lightning release notes; I checked that the spelling @jonatack proposes is the same as being used by the upstream PostgreSQL project.
|
|
||
| - **Help Bitcoin Core release candidate:** experienced users are encouraged to | ||
| help test the latest release candidates for the upcoming version of | ||
| [Bitcoin Core][Bitcoin Core 0.19.0]. |
There was a problem hiding this comment.
Perhaps provide a link to the testing meta-issue for test reports (or filing a separate issue in case of problems found).
|
|
||
| ## News | ||
|
|
||
| - **LN simplified commitments:** in two separate threads, developers |
There was a problem hiding this comment.
possibly s/threads/mailing list threads (or) lightning-dev mailing list threads/
| LN protocol specification. | ||
|
|
||
| - **Publication of videos and study material from schnorr/taproot workshop:** | ||
| Optech published a [blog post][taproot workshop] with links to videos, Jupyter |
There was a problem hiding this comment.
nit: sometimes Optech writes "jupyter" and other times "Jupyter"... possibly a candidate for the style guide
|
|
||
| - [Why does hashing public keys not actually provide any quantum resistance?]({{bse}}91049) | ||
| Andrew Chow lists several considerations regarding public keys and quantum | ||
| resistance including: needing to reveal the public key during spending, the |
There was a problem hiding this comment.
nits: add a comma after "resistance", remove the colon, and s/needing/the need/
| branch and will probably not be released until version 0.20, expected | ||
| about six months from now. BIP70 was made optional in [version | ||
| 0.18.0][core 0.18.0] and will be disabled by default in the upcoming | ||
| 0.19.0, see [Newsletter #19][pr14451] for more information. |
There was a problem hiding this comment.
s/, see/. See (or) ; see/
|
ACK |
|
Pushed (hopefully) final edits based on @jnewbery and @jonatack feedback (thanks). I split the edits into two commits to make it easier to squash this down into separate commits for the newsletter text added by @bitschmidty and for the text added by myself. |
| help test the latest release candidates for the upcoming version of | ||
| [Bitcoin Core][Bitcoin Core 0.19.0]. | ||
| [Bitcoin Core][Bitcoin Core 0.19.0] and [report][Bitcoin Core #17079] | ||
| any issues you find. |
There was a problem hiding this comment.
I don't know if you want to get into the details, but what is desired afaict is for people to report their RC testing in the meta-issue (to reassure the maintainers that testing is taking place and for which platforms) and to open a separate issue if a problem is encountered while testing.
There was a problem hiding this comment.
That's confusing. I'm going to drop mention of this issue.
harding
force-pushed
the
2019-10-30-newsletter
branch
from
c413436 to
125eb9f
Compare
|
ACK 125eb9f |
|
Oh what a pity This time we do it in sets of 3 Optech workshop materials, your homework @harding rocks the newsletter, shouldn't be strange |
No description provided.