Plugins: create clickable anchor links

_plugins/auto-anchor.rb

@@ -21,7 +21,8 @@
         ## Remove double-quotes from titles before attempting to slugify
         title.gsub!('"', '')
         ## Use Liquid/Jekyll slugify filter to choose our id
-        id_prefix = '- {:#{{ "' + title + '" | slugify: "latin" }}} '
+        slug = "\#{{ \"#{title}\" | slugify: 'latin' }}"
+        id_prefix = "- {:#{slug} .anchor-list} <a href=\"#{slug}\" class=\"anchor-list-link\">●</a>"
         string.sub!(/-/, id_prefix)
       end
     end

_posts/en/newsletters/2018-06-08-newsletter.md

@@ -80,31 +80,31 @@ A new maintenance release of Bitcoin Core is coming soon with a change to relay
 
 ## On this day in Bitcoin commit history…
 
-- **2017:** Andrew Chow authored commit [ec6902d][commitec6902d] paving the way to remove the last parts of the confusing “safe mode” functionality added to Bitcoin 0.3.x after the [value overflow incident][value overflow].
+- **<!--n-->2017:** Andrew Chow authored commit [ec6902d][commitec6902d] paving the way to remove the last parts of the confusing “safe mode” functionality added to Bitcoin 0.3.x after the [value overflow incident][value overflow].
 
 [commitec6902d]: https://github.com/bitcoin/bitcoin/commit/ec6902d0ea2bbe75179684fc71849d5e34647a14
 [value overflow]: https://en.bitcoin.it/wiki/Value_overflow_incident
 
-- **2016:** Luke Dashjr’s PR [#7935][PR7953] was merged adding support for [BIP9] versionbits to the GetBlockTemplate RPC call, allowing miners to signal support for future soft forks—such as the soft fork that activated [BIP141] segregated witness.
+- **<!--n-->2016:** Luke Dashjr’s PR [#7935][PR7953] was merged adding support for [BIP9] versionbits to the GetBlockTemplate RPC call, allowing miners to signal support for future soft forks—such as the soft fork that activated [BIP141] segregated witness.
 
 [PR7953]: https://github.com/bitcoin/bitcoin/pull/7935
 [BIP9]: https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki
 [BIP141]: https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki
 
-- **2015:** Gavin Andresen authored commit [65b94545][commit65b94545] to refine the criteria a node uses to detect that it may no longer be receiving blocks from the best block chain.
+- **<!--n-->2015:** Gavin Andresen authored commit [65b94545][commit65b94545] to refine the criteria a node uses to detect that it may no longer be receiving blocks from the best block chain.
 
 [commit65b94545]: https://github.com/bitcoin/bitcoin/commit/65b94545036ae6e38e79e9c7166a3ba1ddb83f66
 
-- **2014:** Cozz Lovan authored commit [95a93836][commit95a93836] removing a legacy part of the GUI that assumed any transaction fee below 0.01 BTC was a low transaction fee.
+- **<!--n-->2014:** Cozz Lovan authored commit [95a93836][commit95a93836] removing a legacy part of the GUI that assumed any transaction fee below 0.01 BTC was a low transaction fee.
 
 [commit95a93836]: https://github.com/bitcoin/bitcoin/commit/95a93836d8ab3e5f2412503dfafdf54db4f8c1ee
 
-- **2013:** Wladimir van der Laan authored commit [3e9c8ba][commit3e9c8ba] fixing a bug related to the data directory.
+- **<!--n-->2013:** Wladimir van der Laan authored commit [3e9c8ba][commit3e9c8ba] fixing a bug related to the data directory.
 
 [commit3e9c8ba]: https://github.com/bitcoin/bitcoin/commit/3e9c8bab54371364f8e70c3b44e732c593b43a76
 
-- **2012:** Luke Dashjr authored several commits (e.g. [9655d73][commit9655d73]) related to enabling IPv6 support.
+- **<!--n-->2012:** Luke Dashjr authored several commits (e.g. [9655d73][commit9655d73]) related to enabling IPv6 support.
 
 [commit9655d73]: https://github.com/bitcoin/bitcoin/commit/9655d73f49cd4da189ddb2ed708c26dc4cb3babe
 
-- **2011, 2010, 2009:** no commits dated June 8th.
+- **<!--n-->2011, 2010, 2009:** no commits dated June 8th.

_posts/en/newsletters/2018-07-17-newsletter.md

@@ -82,12 +82,12 @@ flag, and several notable recent Bitcoin Core merges.
 
 ## Notable Bitcoin Core merges
 
-- **[#13072][]:** The `createmultisig` RPC can now create P2SH-wrapped
+- **<!--n-->[#13072][]:** The `createmultisig` RPC can now create P2SH-wrapped
   segwit and native segwit addresses.
 
-- **[#13543][]:** Support for the RISC-V CPU architecture added.
+- **<!--n-->[#13543][]:** Support for the RISC-V CPU architecture added.
 
-- **[#13386][]:** New specialized SHA256 functions that take advantage
+- **<!--n-->[#13386][]:** New specialized SHA256 functions that take advantage
   of CPU extensions and knowledge of specific data inputs used by Bitcoin
   Core (such as the very common case where the input data is exactly 64
   bytes, as used for every calculation in a Bitcoin merkle tree).  This
@@ -96,7 +96,7 @@ flag, and several notable recent Bitcoin Core merges.
   code mainly helps speed up validation of blocks, both historic blocks
   during initial sync and new blocks during normal operation.
 
-- **[#13452][]:** The `verifytxoutproof` RPC is no longer vulnerable to
+- **<!--n-->[#13452][]:** The `verifytxoutproof` RPC is no longer vulnerable to
   a particular [expensive attack][tx-as-internal-node] against SPV
   proofs publicly disclosed in early June.  The attack was considered
   unlikely given that much cheaper attacks of roughly equal
@@ -105,11 +105,11 @@ flag, and several notable recent Bitcoin Core merges.
   `getblock` RPC.  None of this mitigates the attack for actual SPV
   clients.
 
-- **[#13570][]:** New `getzmqnotifications` RPC that "returns
+- **<!--n-->[#13570][]:** New `getzmqnotifications` RPC that "returns
   information about all active ZMQ notification endpoints.  This is
   useful for software that layers on top of bitcoind."
 
-- **[#13096][]:** Increase the maximum size of transactions that will be
+- **<!--n-->[#13096][]:** Increase the maximum size of transactions that will be
   relayed by default from 99,999 vbytes to 100,000 vbytes.
 
 [newsletter #3]: /en/newsletters/2018/07/10/

_posts/en/newsletters/2018-07-24-newsletter.md

@@ -14,7 +14,7 @@ Bitcoin transactions, and news on several other notable Bitcoin Core merges.
 
 ## Action items
 
-- Bitcoin Core [0.16.2RC2][] released for testing in preparation for a
+- [Bitcoin Core 0.16.2RC2][] released for testing in preparation for a
   maintenance release that will provide bugfixes and backports.
   Community testing is highly appreciated.  Note, there was no RC1 due
   to a metadata problem being detected during the release process.
@@ -97,7 +97,7 @@ Bitcoin transactions, and news on several other notable Bitcoin Core merges.
 git log --merges b25a4c2284babdf1e8cf0ec3b1402200dd25f33f..07ce278455757fb46dab95fb9b97a3f6b1b84faf
 {% endcomment %}
 
-- [#9662][Bitcoin Core #9662]: New wallets can now be created with private keys disabled.
+- [Bitcoin Core #9662][]: New wallets can now be created with private keys disabled.
   This is primarily meant for users who want to exclusively use their
   wallet in conjunction with another program or hardware wallet that
   stores private keys.  This could also be useful to companies that want
@@ -106,7 +106,7 @@ git log --merges b25a4c2284babdf1e8cf0ec3b1402200dd25f33f..07ce278455757fb46dab9
   performing whatever actions they desire, such as using the
   [`fundrawtransaction`][rpc fundrawtransaction] RPC.
 
-- [#12196][Bitcoin Core #12196]: New `scantxoutset` RPC method that allows searching the
+- [Bitcoin Core #12196][]: New `scantxoutset` RPC method that allows searching the
   set of spendable bitcoins (UTXOs) for those matching an address,
   public key, private key, or HD keypath.  The main expected use for
   this is "funds sweeping" where transactions matching an old wallet are
@@ -117,12 +117,12 @@ git log --merges b25a4c2284babdf1e8cf0ec3b1402200dd25f33f..07ce278455757fb46dab9
   updated to support output script descriptors, which is planned to
   happen before 0.17.
 
-- [#13604][Bitcoin Core #13604]: Bitcoin-Qt is now built by default in addition to bitcoind
+- [Bitcoin Core #13604][]: Bitcoin-Qt is now built by default in addition to bitcoind
   on 32-bit ARM systems, and should be distributed by default with the
   other binaries for that system from BitcoinCore.org for future
   releases.  Bitcoin-Qt with 64-bit ARM is not yet supported by default.
 
-- [#13298][Bitcoin Core #13298]: The node now sends all announcements ([invs][inv]) for
+- [Bitcoin Core #13298][]: The node now sends all announcements ([invs][inv]) for
   new transactions to all of its incoming peers at the same time, after
   a random delay.  Previously, Satoshi Nakamoto [added a feature][rand
   delay] to Bitcoin (the software) that waited for a different random
@@ -149,7 +149,7 @@ git log --merges b25a4c2284babdf1e8cf0ec3b1402200dd25f33f..07ce278455757fb46dab9
     nodes no longer find making multiple connections to be useful,
     reducing overall wasted bandwidth.
 
-- [#13652][Bitcoin Core #13652]: The [`abandontransaction`][rpc abandontransaction] RPC has
+- [Bitcoin Core #13652][]: The [`abandontransaction`][rpc abandontransaction] RPC has
   been fixed to abandon all descendant transactions, not just children.
 
 ## Coming attractions
@@ -165,7 +165,7 @@ to share your experiences in implementing better Bitcoin technology, please cont
 [rand delay]: https://github.com/bitcoin/bitcoin/commit/22f721dbf23cf5ce9e3ded9bcfb65a3894cc0f8c#diff-118fcbaaba162ba17933c7893247df3aR718
 [p2shinfo bech32]: https://p2sh.info/dashboard/db/bech32-statistics?orgId=1
 [consolidate utxos]: https://en.bitcoin.it/wiki/Techniques_to_reduce_transaction_fees#Consolidation
-[0.16.2rc2]: https://bitcoincore.org/bin/bitcoin-core-0.16.2/test.rc2/
+[Bitcoin Core 0.16.2rc2]: https://bitcoincore.org/bin/bitcoin-core-0.16.2/test.rc2/
 [announce bmag]: https://bitcoinmagazine.com/articles/chaincode-devs-google-alumni-create-industry-group-help-bitcoin-scale/
 [announce cdesk]: https://www.coindesk.com/bitcoins-biggest-startups-are-backing-a-new-effort-to-keep-fees-low/
 [inv]: https://bitcoin.org/en/developer-reference#inv

_posts/en/newsletters/2018-09-25-newsletter.md

@@ -33,13 +33,13 @@ infrastructure projects.
     following versions remains highly recommended for any system,
     especially those systems handling money:
 
-    - [0.16.3][] (current stable)
+    * [0.16.3][] (current stable)
 
-    - [0.17.0RC4][bcc 0.17] (release candidate for next major version)
+    * [0.17.0RC4][bcc 0.17] (release candidate for next major version)
 
-    - [0.15.2][] (backport to old version, may have other issues)
+    * [0.15.2][] (backport to old version, may have other issues)
 
-    - [0.14.3][] (backport to old version, may have other issues)
+    * [0.14.3][] (backport to old version, may have other issues)
 
 - **Allocate time to test Bitcoin Core 0.17RC4:** Bitcoin Core has
   uploaded [binaries][bcc 0.17] for 0.17 Release Candidate (RC) 4.

_posts/en/newsletters/2018-11-27-newsletter.md

@@ -161,7 +161,7 @@ commits].*
   all uppercase (but not mixed case) per the [BIP173][] bech32
   specification.
 
-- C-Lightning [#2081][c-lightning #2081] and [#2092][c-lightning #2092]
+- C-Lightning [<!--c-lightning-->#2081][c-lightning #2081] and [#2092][c-lightning #2092]
   fix a problem with running multiple RPC commands in parallel.  As a
   user-visible change, `lightningd` now adds a double newline (`\n\n`)
   instead of just a single newline to the final output from an RPC.  As

_posts/en/newsletters/2019-02-05-newsletter.md

@@ -21,7 +21,7 @@ popular Bitcoin infrastructure projects.
 
 ## News
 
-- **2019 Chaincode Residency:** Chaincode Labs opened applications for its
+- **Chaincode Residency 2019:** Chaincode Labs opened applications for its
   [fourth residency program][residency] to be held in New York over
   summer 2019. The program combines a 3 week seminar and discussion series
   covering Bitcoin and Lightning protocol development with a two month period for

_posts/en/newsletters/2019-03-05-newsletter.md

@@ -447,7 +447,7 @@ More information:
   signers of an output to give someone else permission to spend it
   without creating an onchain transaction)
 
-- [`1 OP_RETURN` bug description][1return] - a fixed bug that allowed
+- [<!--op-->`1 OP_RETURN` bug description][1return] - a fixed bug that allowed
   anyone to spend anyone else's bitcoins.  Called "by far the worst
   security problem Bitcoin ever had".  Satoshi Nakamoto's
   [fix][1opreturn fix] for this bug involved separating the

_posts/en/newsletters/2019-04-23-newsletter.md

@@ -128,7 +128,7 @@ backported to its pending release.*
   Optech's [RBF usability study][] and so allows fee bumps made by
   Bitcoin Core users to succeed more often.
 
-- C-Lightning PRs [#2541][c-lightning #2541], [#2545][c-lightning
+- C-Lightning PRs [<!--c-lightning-->#2541][c-lightning #2541], [#2545][c-lightning
   #2545], and [#2546][c-lightning #2546] implement multiple changes to
   the gossip subsystem used for tracking which channels are available
   and calculating routes across them.  This work was motivated by the

_posts/en/newsletters/2019-10-16-newsletter.md

@@ -44,23 +44,23 @@ notable changes to popular Bitcoin infrastructure projects.
   the Bitcoin-Dev mailing list with a summary of recent changes to the
   proposal.  Changes include:
 
-    - 32-byte public keys instead of 33-byte keys (mentioned in
+    * 32-byte public keys instead of 33-byte keys (mentioned in
       [Newsletter #59][32 byte pubkey]).
 
-    - No support for P2SH-wrapped taproot addresses (mentioned in
+    * No support for P2SH-wrapped taproot addresses (mentioned in
       [#65][p2sh-wrapped taproot]).
 
-    - 32-bit txin positions in the signature hash data rather than
+    * 32-bit txin positions in the signature hash data rather than
       16-bit indexes.
 
-    - Tagged hashes are now used in [bip-schnorr][].  They were
+    * Tagged hashes are now used in [bip-schnorr][].  They were
       previously only used in [bip-taproot][] and [bip-tapscript][].
 
-    - The 10,000-byte and 201 non-push opcode limits have been dropped
+    * The 10,000-byte and 201 non-push opcode limits have been dropped
       from [bip-tapscript][] (mentioned in [#65][tapscript resource
       limits]).
 
-    - The maximum depth of the merkle tree has been increased from 32
+    * The maximum depth of the merkle tree has been increased from 32
       levels to 128 levels.
 
     Wuille's email and the updated BIPs provide rationales for each of

_posts/en/newsletters/2019-12-28-newsletter.md

@@ -60,45 +60,45 @@ words can express for all that you've done to help Bitcoin.
 
 ## Contents
 
-- January
-    - [BIP127 proof of reserves](#bip127)
-- February
-    - [Bitcoin Core compatible with HWI](#core-hwi)
-    - <a href="#miniscript">Miniscript</a>
-- March
-    - [Consensus cleanup soft fork proposal](#cleanup)
-    - <a href="#signet">Signet</a>
-    - [Lightning Loop](#loop)
-- April
-    - <a href="#assumeutxo">AssumeUTXO</a>
-    - [Trampoline payments](#trampoline)
-- May
-    - <a href="#taproot">Taproot</a>
-    - [SIGHASH_ANYPREVOUT](#anyprevout)
-    - [OP_CHECKTEMPLATEVERIFY](#ctv)
-- June
-    - [Erlay and other P2P relay improvements](#erlay-and-other-p2p-improvements)
-    - <a href="#watchtowers">Watchtowers</a>
-- July
-    - [Reproducible builds](#reproducibility)
-- August
-    - [Vaults without covenants](#vaults)
-- September
-    - <a href="#snicker">SNICKER</a>
-    - [LN vulnerability](#ln-cve)
-- October
-    - [LN anchor outputs](#anchor-outputs)
-- November
-    - <a href="#bech32-mutability">Bech32 mutability</a>
-    - [Bitcoin Core OpenSSL removal](#openssl)
-    - [Bitcoin Core BIP70 removal](#bip70)
-- December
-    - [Multipath payments](#multipath)
-- Featured summaries
-    - [Major releases of popular infrastructure projects](#releases)
-    - [Notable technical conferences and other events](#conferences)
-    - [Bitcoin Optech](#optech)
-    - [New open source infrastructure solutions](#new-infrastructure)
+* January
+    * [BIP127 proof of reserves](#bip127)
+* February
+    * [Bitcoin Core compatible with HWI](#core-hwi)
+    * <a href="#miniscript">Miniscript</a>
+* March
+    * [Consensus cleanup soft fork proposal](#cleanup)
+    * <a href="#signet">Signet</a>
+    * [Lightning Loop](#loop)
+* April
+    * <a href="#assumeutxo">AssumeUTXO</a>
+    * [Trampoline payments](#trampoline)
+* May
+    * <a href="#taproot">Taproot</a>
+    * [SIGHASH_ANYPREVOUT](#anyprevout)
+    * [OP_CHECKTEMPLATEVERIFY](#ctv)
+* June
+    * [Erlay and other P2P relay improvements](#erlay-and-other-p2p-improvements)
+    * <a href="#watchtowers">Watchtowers</a>
+* July
+    * [Reproducible builds](#reproducibility)
+* August
+    * [Vaults without covenants](#vaults)
+* September
+    * <a href="#snicker">SNICKER</a>
+    * [LN vulnerability](#ln-cve)
+* October
+    * [LN anchor outputs](#anchor-outputs)
+* November
+    * <a href="#bech32-mutability">Bech32 mutability</a>
+    * [Bitcoin Core OpenSSL removal](#openssl)
+    * [Bitcoin Core BIP70 removal](#bip70)
+* December
+    * [Multipath payments](#multipath)
+* Featured summaries
+    * [Major releases of popular infrastructure projects](#releases)
+    * [Notable technical conferences and other events](#conferences)
+    * [Bitcoin Optech](#optech)
+    * [New open source infrastructure solutions](#new-infrastructure)
 
 ## January
 

_posts/en/newsletters/2020-02-05-newsletter.md

@@ -137,14 +137,14 @@ public key may leak the secret key through an (invalid) signature."
     channel without affecting the spendability of other funds already in
     the channel).  Replies to Neigut's proposal included:
 
-    - A suggestion to set the nLockTime field's value to a recent or
+    * A suggestion to set the nLockTime field's value to a recent or
       upcoming block height in order to implement anti-fee sniping which
       helps disincentivize block chain reorganizations and which will
       help funding transactions blend in with other wallets that have
       already implement anti-fee sniping (including LND's sweeping mode,
       see [Newsletter #18][news18 lnd afs]).
 
-    - More broadly, a suggestion to implement a common set of values for
+    * More broadly, a suggestion to implement a common set of values for
       free parameters in a transaction (such as nVersion, nSequence,
       nLockTime, input ordering, and output ordering) with other
       collaborative transaction creation systems (such as
@@ -153,12 +153,12 @@ public key may leak the secret key through an (invalid) signature."
       created (especially if [taproot][topic taproot] is adopted, as
       mutual LN close transactions can look like single-sig spends).
 
-    - A suggestion to communicate proposed transaction details using
+    * A suggestion to communicate proposed transaction details using
       [BIP174][] Partially-Signed Bitcoin Transactions ([PSBTs][topic
       psbt]).  Though Neigut replied that she thinks PSBT is "a bit
       overweight for transaction collaboration between two peers."
 
-    - {:#podle} A sub-discussion about how to avoid probing where Mallory starts
+    * {:#podle} A sub-discussion about how to avoid probing where Mallory starts
       the process of opening a dual-funded channel with Bob but then
       aborts after she receives the identity of one of Bob's UTXOs.
       By aborting before the funding transaction is complete, Mallory