@@ -24,7 +24,7 @@ describing notable changes to popular Bitcoin infrastructure software.
2424- ** Testing HTLC endorsement:** several weeks ago, Carla Kirk-Cohen and
2525 Clara Shikhelman [ posted] [ kcs endorsement ] to the Lightning-Dev mailing list about
2626 the next steps they and others planned to take to test the idea of
27- [ HTLC] [ topic htlc ] endorsement (see [ Newsletter #239 ] [ news239
27+ [[ HTLC]] endorsement (see [ Newsletter #239 ] [ news239
2828 endorsement] ) as part of a mitigation for [ channel jamming
2929 attacks] [ topic channel jamming attacks ] . Most notably, they provided a
3030 short [ proposed specification] [ bolts #1071 ] that could be deployed
@@ -64,8 +64,8 @@ describing notable changes to popular Bitcoin infrastructure software.
6464
6565- ** Challenges with zero-conf channels when dual funding:** Bastien
6666 Teinturier [ posted] [ teinturier 0conf ] to the Lightning-Dev mailing list about the
67- challenges of allowing [ zero-conf channels ] [ topic zero-conf channels] when using the
68- [ dual-funding protocol] [ topic dual funding ] . Zero-conf channels can be used even before the
67+ challenges of allowing [[ zero-conf channels] ] when using the
68+ [[ dual-funding|dual-funding protocol]] . Zero-conf channels can be used even before the
6969 channel open transaction is confirmed; this is trustless in some
7070 cases. Dual-funded channels are channels that were created using the
7171 dual-funding protocol, which may include channels where the open
@@ -99,13 +99,13 @@ describing notable changes to popular Bitcoin infrastructure software.
9999
100100 - * Batched payment forwarding:* rather than Alice paying Bob, Alice
101101 instead pays several people Bob owes money (or wants to establish
102- a credit with). Gould's example considers an exchange that has a
102+ a credit with). Gould's example [[ payment batching|batching ]] considers an exchange that has a
103103 steady stream of deposits and withdrawals; payjoin allows withdrawals
104104 to be paid for by new deposits when possible.
105105
106106 Both of these techniques allow reducing what would be at least two
107107 transactions into a single transaction, saving a considerable amount
108- of block space. When [ batching ] [ topic payment batching ] is used,
108+ of block space. When is used,
109109 the space savings may be even larger. Even better from the
110110 perspective of the original receiver (e.g. Bob),
111111 the original spender (e.g. Alice) may pay all or some of the
@@ -200,7 +200,7 @@ Proposals (BIPs)][bips repo], [Lightning BOLTs][bolts repo], and
200200 continue trying to download the block from peers that claim to have it
201201 until one of the received blocks has been written to disk.
202202
203- - [ LDK #2286 ] [ ] allows creating and signing [ PSBTs ] [ topic psbt] for
203+ - [ LDK #2286 ] [ ] allows creating and signing [[ psbt|PSBTs ] ] for
204204 outputs controlled by the local wallet.
205205
206206- [ LDK #1794 ] [ ] begins adding support for [ dual funding] [ topic dual
0 commit comments