|
| 1 | +--- |
| 2 | +title: 'Bitcoin Optech Newsletter #89' |
| 3 | +permalink: /en/newsletters/2020/03/18/ |
| 4 | +name: 2020-03-18-newsletter |
| 5 | +slug: 2020-03-18-newsletter |
| 6 | +type: newsletter |
| 7 | +layout: newsletter |
| 8 | +lang: en |
| 9 | +--- |
| 10 | +This week's newsletter summarizes an update to a proposed standard for |
| 11 | +LN and includes our regular sections about notable changes to services, |
| 12 | +client software, and popular Bitcoin infrastructure projects. |
| 13 | + |
| 14 | +## Action items |
| 15 | + |
| 16 | +*None this week.* |
| 17 | + |
| 18 | +## News |
| 19 | + |
| 20 | +- **Proposed watchtower BOLT updated:** Sergi Delgado Segura |
| 21 | + [emailed][segura email] the Lightning-Dev mailing list an [updated |
| 22 | + version][watchtower bolt] of a suggested protocol for |
| 23 | + [watchtower][topic watchtowers] communication. See [Newsletter |
| 24 | + #75][news75 watchtower] for our original description of this proposal. According to |
| 25 | + Segura, the update includes details about "user accounts, payment |
| 26 | + methods, and message signing." His email also provides a list of |
| 27 | + features he would like to add, with discussion about each near the end |
| 28 | + of the email. |
| 29 | + |
| 30 | +## Changes to services and client software |
| 31 | + |
| 32 | +*In this monthly feature, we highlight interesting updates to Bitcoin |
| 33 | +wallets and services.* |
| 34 | + |
| 35 | +FIXME:bitschmidty |
| 36 | + |
| 37 | +## Notable code and documentation changes |
| 38 | + |
| 39 | +*Notable changes this week in [Bitcoin Core][bitcoin core repo], |
| 40 | +[C-Lightning][c-lightning repo], [Eclair][eclair repo], [LND][lnd repo], |
| 41 | +[libsecp256k1][libsecp256k1 repo], [Bitcoin Improvement Proposals |
| 42 | +(BIPs)][bips repo], and [Lightning BOLTs][bolts repo].* |
| 43 | + |
| 44 | +- [Bitcoin Core #16902][] changes consensus code to fix an inefficiency |
| 45 | + in the parsing of `OP_IF` and related opcodes. In legacy and segwit |
| 46 | + v0 script, the inefficiency isn't believed to cause any significant |
| 47 | + problems, but the proposal for [tapscript][topic tapscript] would |
| 48 | + allow the inefficiency to be exploited in order to create transactions |
| 49 | + in blocks that could take a large amount of CPU to verify. Fixing the |
| 50 | + inefficiency reduces the number of changes that need to be made in the |
| 51 | + proposed schnorr, taproot, and tapscript soft fork. For more |
| 52 | + information, see the Bitcoin Core PR Review Club [meeting notes][club |
| 53 | + #16902] about this PR and a [related PR][Bitcoin Core #18002] also |
| 54 | + merged this week. |
| 55 | + |
| 56 | +- [LND #3821][] [anchor] pluggable anchor commitments FIXME:dongcarl |
| 57 | + |
| 58 | +- [LND #3963][] adds detailed [documentation][lnd op safety] about how |
| 59 | + to use LND safely. |
| 60 | + |
| 61 | +- [Eclair #1319][] implements the same solution as described in |
| 62 | + [Newsletter #85][news85 ln stuck] for a rare stuck-channels problem |
| 63 | + where payments are rejected for insufficient funds when the channel |
| 64 | + funder is receiving the money but doesn't have enough balance to |
| 65 | + afford the payment's commitment (HTLC) cost. |
| 66 | + |
| 67 | +{% include references.md %} |
| 68 | +{% include linkers/issues.md issues="16902,3821,3963,18002,1319" %} |
| 69 | +[lnd op safety]: https://github.com/lightningnetwork/lnd/blob/master/docs/safety.md |
| 70 | +[segura email]: https://lists.linuxfoundation.org/pipermail/lightning-dev/2020-March/002586.html |
| 71 | +[watchtower bolt]: https://github.com/sr-gi/bolt13/blob/master/13-watchtowers.md |
| 72 | +[club #16902]: https://bitcoincore.reviews/16902/ |
| 73 | +[news75 watchtower]: /en/newsletters/2019/12/04/#proposed-watchtower-bolt |
| 74 | +[news85 ln stuck]: /en/newsletters/2020/02/19/#c-lightning-3500 |
0 commit comments