Skip to content

Commit cdfc4a4

Browse files
committed
Podcasts: add 248 recap
1 parent 5b3c401 commit cdfc4a4

2 files changed

Lines changed: 562 additions & 11 deletions

File tree

_posts/en/newsletters/2023-04-26-newsletter.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ Bitcoin infrastructure software.
5757

5858
Additional feedback is requested from anyone using the BIP35
5959
`mempool` message for any purpose. You can reply to either the
60-
mailing list post or the PR linked previously.
60+
mailing list post or the PR linked previously. {% assign timestamp="0:41" %}
6161

6262
## Selected Q&A from Bitcoin Stack Exchange
6363

@@ -73,21 +73,21 @@ answers posted since our last update.*
7373
- [How many sigops are in the invalid block 783426?]({{bse}}117837)
7474
Vojtěch Strnad provided a script that iterates through all transactions in a
7575
block and counts the [sigops]({{bse}}117359) and notes that there were 80,003 sigops in the
76-
block, making it [invalid][max sigops].
76+
block, making it [invalid][max sigops]. {% assign timestamp="15:27" %}
7777

7878
- [How would an adversary increase the required fee to replace a transaction by up to 500 times?]({{bse}}117734)
7979
In referencing a draft BIP for [ephemeral anchors][topic ephemeral anchors],
8080
Michael Folkson asks how the referenced 500 times increase in required fees
8181
for a transaction replacement could occur. Antoine Poinsot gives an example
8282
of how an attacker could use the [Replace-By-Fee (RBF)][topic rbf] fee bumping
8383
rules to require additional replacement transactions to pay significantly
84-
higher fees.
84+
higher fees. {% assign timestamp="19:10" %}
8585

8686
- [Best Practices with Multiple CPFPs & CPFP + RBF?]({{bse}}117877)
8787
Sdaftuar explains considerations around using RBF and [Child Pays For Parent
8888
(CPFP)][topic cpfp] fee bumping techniques in the scenario that an initial
8989
CPFP fee bumping attempt failed to offer a sufficient feerate to get the
90-
initial transaction confirmed.
90+
initial transaction confirmed. {% assign timestamp="22:51" %}
9191

9292
## Releases and release candidates
9393

@@ -98,16 +98,16 @@ release candidates.*
9898
- [LDK 0.0.115][] is a release of this library for building LN-enabled
9999
wallets and applications. It includes several new features and bug
100100
fixes, including more support for the experimental [offers][topic
101-
offers] protocol and improved security and privacy.
101+
offers] protocol and improved security and privacy. {% assign timestamp="25:01" %}
102102

103103
- [LND v0.16.1-beta][] is a minor release of this LN implementation that
104104
includes several bug fixes and other improvements. Its release notes
105105
note that its default CLTV delta has been increased from 40 blocks to
106106
80 blocks (see [Newsletter #40][news40 cltv] where we covered a
107-
previous change in LND's default CLTV delta).
107+
previous change in LND's default CLTV delta). {% assign timestamp="25:48" %}
108108

109109
- [Core Lightning 23.05rc1][] is a release candidate for the next
110-
version of this LN implementation.
110+
version of this LN implementation. {% assign timestamp="27:01" %}
111111

112112
## Notable code and documentation changes
113113

@@ -123,12 +123,12 @@ Proposals (BIPs)][bips repo], [Lightning BOLTs][bolts repo], and
123123
the mempool to monitor for unconfirmed transactions containing
124124
preimages for the HTLCs in the node's channels. This allows the node
125125
to resolve the HTLCs faster than waiting for those transactions to
126-
confirm.
126+
confirm. {% assign timestamp="27:35" %}
127127

128128
- [LND #6903][] updates the `openchannel` RPC with a new `fundmax`
129129
option that will allocate all channel funds towards a new channel,
130130
with the exception of any amount that needs to be kept onchain for
131-
adding fees to channels using [anchor outputs][topic anchor outputs].
131+
adding fees to channels using [anchor outputs][topic anchor outputs]. {% assign timestamp="28:10" %}
132132

133133
- [LDK #2198][] increases the amount of time LDK waits before sending a
134134
gossip message announcing that a channel is down (e.g. because the
@@ -140,13 +140,13 @@ Proposals (BIPs)][bips repo], [Lightning BOLTs][bolts repo], and
140140
block (approximately every 10 minutes on average). Although the PR
141141
notes that sending slower updates involves tradeoffs, it updates LDK
142142
to wait about 10 minutes before broadcasting a channel disabled
143-
message.
143+
message. {% assign timestamp="29:40" %}
144144

145145
- [Bitcoin Inquisition #23][] adds part of the support for [ephemeral
146146
anchors][topic ephemeral anchors]. It doesn't include support for [v3
147147
transaction relay][topic v3 transaction relay], which ephemeral anchors
148148
depends on to stop [transaction pinning attacks][topic transaction
149-
pinning].
149+
pinning]. {% assign timestamp="32:37" %}
150150

151151
{% include references.md %}
152152
{% include linkers/issues.md v=2 issues="7564,6903,2198,1059,23,27426" %}

0 commit comments

Comments
 (0)