@@ -25,7 +25,7 @@ selection---including why Bitcoin Core has a more restrictive policy
25
25
than allowed by consensus and how wallets can use that policy most
26
26
effectively._
27
27
28
- {% include specials/policy/en/10-get-involved.md %}
28
+ {% include specials/policy/en/10-get-involved.md %} {% assign timestamp="2:01" %}
29
29
30
30
## Changes to services and client software
31
31
@@ -37,55 +37,55 @@ wallets and services.*
37
37
derivatives non-custodially using [ DLCs] [ topic dlc ] in an [ offchain contract] [ 10101 blog2 ]
38
38
that can also be used to send, receive, and forward LN payments. The DLCs rely
39
39
on oracles that use [ adaptor signatures] [ topic adaptor signatures ] for price
40
- [ attestation] [ 10101 blog1 ] .
40
+ [ attestation] [ 10101 blog1 ] . {% assign timestamp="14:56" %}
41
41
42
42
- ** LDK Node announced:**
43
43
The LDK team [ announced] [ ldk blog ] LDK Node [ v0.1.0] [ LDK Node v0.1.0 ] . LDK Node is a
44
44
Lightning node Rust library that uses the LDK and BDK libraries to enable developers
45
45
to quickly setup a self-custodial Lightning node while still providing a high degree of
46
- customization for different use cases.
46
+ customization for different use cases. {% assign timestamp="17:14" %}
47
47
48
48
- ** Payjoin SDK announced:**
49
49
[ Payjoin Dev Kit (PDK)] [ PDK github ] was [ announced] [ PDK blog ] as a Rust
50
50
library that implements [ BIP78] [ ] for use in wallets and services that wish to
51
- integrate [ payjoin] [ topic payjoin ] functionality.
51
+ integrate [ payjoin] [ topic payjoin ] functionality. {% assign timestamp="20:09" %}
52
52
53
53
- ** Validating Lightning Signer (VLS) beta announced:**
54
54
VLS allows the separation of a Lightning node from the keys that control its
55
55
funds. A Lightning node running with VLS will route signing requests to a
56
56
remote signing device instead of local keys. The [ beta release] [ VLS gitlab ]
57
57
supports CLN and LDK, layer-1 and layer-2 validation rules, backup/recovery
58
58
capabilities, and provides a reference implementation. The [ blog
59
- post] [ VLS blog ] announcement also calls for testing, feature requests, and feedback from the community.
59
+ post] [ VLS blog ] announcement also calls for testing, feature requests, and feedback from the community. {% assign timestamp="25:27" %}
60
60
61
61
- ** BitGo adds MuSig2 support:**
62
62
BitGo [ announced] [ bitgo blog ] support for [ BIP327] [ ] ([ MuSig2] [ topic musig ] )
63
63
and noted the reduced fees and additional privacy compared to their other
64
- supported address types.
64
+ supported address types. {% assign timestamp="37:42" %}
65
65
66
66
- ** Peach adds RBF support:**
67
67
The [ Peach Bitcoin] [ peach website ] mobile application for peer-to-peer
68
- exchange [ announced] [ peach tweet ] support for [ Replace-By-Fee (RBF)] [ topic rbf ] fee bumping.
68
+ exchange [ announced] [ peach tweet ] support for [ Replace-By-Fee (RBF)] [ topic rbf ] fee bumping. {% assign timestamp="44:34" %}
69
69
70
70
- ** Phoenix wallet adds splicing support:**
71
71
ACINQ [ announced] [ acinq blog ] beta testing for the next version of their
72
72
Phoenix mobile Lightning wallet. The wallet supports a single dynamic channel
73
73
that is rebalanced using [ splicing] [ topic splicing ] and
74
74
a mechanism similar to the [ swap-in-potentiam] [ news233 sip ] technique (see
75
- [ Podcast #259 ] [ pod259 phoenix ] ).
75
+ [ Podcast #259 ] [ pod259 phoenix ] ). {% assign timestamp="46:34" %}
76
76
77
77
- ** Mining Development Kit call for feedback:**
78
78
The team working on the Mining Development Kit (MDK) has [ posted an update] [ MDK blog ] on their
79
79
progress to develop hardware, software, and firmware for Bitcoin mining systems. The post
80
- calls for feedback from the community about use cases, scope, and approach.
80
+ calls for feedback from the community about use cases, scope, and approach. {% assign timestamp="49:27" %}
81
81
82
82
- ** Binance adds Lightning support:**
83
83
Binance [ announced] [ binance blog ] support for sending (withdrawals) and
84
- receiving (deposits) using the Lightning Network.
84
+ receiving (deposits) using the Lightning Network. {% assign timestamp="51:33" %}
85
85
86
86
- ** Nunchuk adds CPFP support:**
87
87
Nunchuk [ announced] [ nunchuk blog ] support for [ Child-Pays-For-Parent
88
- (CPFP)] [ topic cpfp ] fee bumping for both senders and receivers of a transaction.
88
+ (CPFP)] [ topic cpfp ] fee bumping for both senders and receivers of a transaction. {% assign timestamp="53:35" %}
89
89
90
90
## Notable code and documentation changes
91
91
@@ -103,15 +103,15 @@ Proposals (BIPs)][bips repo], [Lightning BOLTs][bolts repo], and
103
103
anonymity networks] to peers on Tor and I2P. This helps prevent
104
104
someone from associating a node's regular network address to one of its
105
105
addresses on an anonymity network. CJDNS is treated differently from
106
- Tor and I2P at the moment, although that may change in the future.
106
+ Tor and I2P at the moment, although that may change in the future. {% assign timestamp="54:57" %}
107
107
108
108
- [ Core Lightning #6347 ] [ ] adds the ability for a plugin to subscribe to
109
- every event notification using the wildcard ` * ` .
109
+ every event notification using the wildcard ` * ` . {% assign timestamp="58:07" %}
110
110
111
111
- [ Core Lightning #6035 ] [ ] adds the ability to request a [ bech32m] [ topic
112
112
bech32] address for receiving deposits to [ P2TR] [ topic taproot ] output
113
113
scripts. Transaction change will also now be sent to a P2TR output by
114
- default.
114
+ default. {% assign timestamp="1:00:47" %}
115
115
116
116
- [ LND #7768 ] [ ] implements BOLTs [ #1032 ] [ bolts #1032 ] and [ #1063 ] [ bolts
117
117
#1063 ] (see [ Newsletter #225 ] [ news225 bolts1032 ] ), allowing the
@@ -121,7 +121,7 @@ Proposals (BIPs)][bips repo], [Lightning BOLTs][bolts repo], and
121
121
requirement that the amount and expiry delta equal exactly the amount
122
122
they requested, but that exactitude meant a forwarding node could
123
123
probe the next hop to see if it was the final receiver by slightly
124
- changing either value.
124
+ changing either value. {% assign timestamp="1:02:28" %}
125
125
126
126
- [ Libsecp256k1 #1313 ] [ ] begins automatic testing using development
127
127
snapshots of the GCC and Clang compilers which may allow detection of
@@ -131,7 +131,7 @@ Proposals (BIPs)][bips repo], [Lightning BOLTs][bolts repo], and
131
131
side channels] . See [ Newsletter #246 ] [ news246 secp ] for one occasion
132
132
where that may have happened and [ Newsletter #251 ] [ news251 secp ] for
133
133
another occasion and an announcement that this sort of testing was
134
- planned.
134
+ planned. {% assign timestamp="1:05:33" %}
135
135
136
136
{% include references.md %}
137
137
{% include linkers/issues.md v=2 issues="27411,6347,6035,7768,1032,1063,1313" %}
0 commit comments