Fix broken URLs to lists.linuxfoundation.org (#2018)

* update lists.linuxfoundation.org urls to gnusha.org/url Unfortunately, lists.linuxfoundation.org is no longer hosting the bitcoin-dev and lightning-dev static email archives, nor any others for that matter. gnusha.org/url is a web service that redirects old style archive urls to a new location where the content can be viewed. "img/posts/taproot-workshop/taproot-workshop.pdf" is not updated. For more information see: bitcoin/bitcoin#29782 (comment) bitcoin/bitcoin#31240 bitcointranscripts/bitcointranscripts#566 https://x.com/kanzure/status/1853779672514826334 https://gnusha.org/url/ * update lists.linuxfoundation.org attachment urls A few lists.linuxfoundation.org urls were linking over to an attachment file, which is not supported by the gnusha.org/url service at this time. Instead, these links have been replaced by a link to the attachment in the public-inbox archive on gnusha.org/pi/bitcoindev.
bitcoinops · Nov 11, 2024 · 7d0572a · 7d0572a
1 parent 38d9857
commit 7d0572a
Show file tree

Hide file tree

Showing 805 changed files with 2,761 additions and 2,761 deletions.
diff --git a/_includes/specials/bech32/01-intro.md b/_includes/specials/bech32/01-intro.md
@@ -98,5 +98,5 @@ addresses.  For most platforms, it should be a very easy change.  See
 set of test vectors you can use to ensure your implementation works
 correctly.
 
-[bech32 proposed]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-March/013749.html
+[bech32 proposed]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-March/013749.html
 [bech32 ref libs]: https://github.com/sipa/bech32/tree/master/ref
diff --git a/_includes/specials/bech32/14-security.md b/_includes/specials/bech32/14-security.md
@@ -113,5 +113,5 @@ bech32 sending support so that they can send payments to those
 security-conscious users.
 
 [bech32 fee savings]: /en/bech32-sending-support/#fee-savings-with-native-segwit
-[sipa collision resistance]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-January/012205.html
+[sipa collision resistance]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-January/012205.html
 [collision attack]: https://en.wikipedia.org/wiki/Collision_attack
diff --git a/_includes/specials/bech32/zh/01-intro.md b/_includes/specials/bech32/zh/01-intro.md
@@ -54,5 +54,5 @@ Bech32 原生 segwit 地址几乎在两年前首次公开[提议][bech32 propose
 
 以上是你需要在软件后端进行的全部更改，以启用发送到 bech32 地址。对于大多数平台，这应该是一个非常简单的更改。参见 [BIP173][] 和[参考实现][bech32 ref libs]以获取一组测试向量，用于确保你的实现正常工作。
 
-[bech32 proposed]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-March/013749.html
+[bech32 proposed]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-March/013749.html
 [bech32 ref libs]: https://github.com/sipa/bech32/tree/master/ref
diff --git a/_includes/specials/bech32/zh/14-security.md b/_includes/specials/bech32/zh/14-security.md
@@ -33,5 +33,5 @@
 总结来说，希望获得最高安全性的多方多重签名用户应该迁移到 bech32 P2WSH 地址，以利用其额外的碰撞抵抗性。随着用户进行这种迁移，各服务确保他们实现 bech32 发送支持以便能够向这些注重安全的用户发送支付将变得更加重要。
 
 [bech32 fee savings]: /zh/bech32-sending-support/#使用原生-segwit-节省费用
-[sipa collision resistance]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-January/012205.html
+[sipa collision resistance]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-January/012205.html
 [collision attack]: https://en.wikipedia.org/wiki/Collision_attack
diff --git a/_includes/specials/policy/cs/06-consistency.md b/_includes/specials/policy/cs/06-consistency.md
@@ -82,6 +82,6 @@ jaká pravidla byla přijata pro co nejlepší fungování celé sítě.
 
 [policy01]: /cs/newsletters/2023/05/17/#%C4%8Dek%C3%A1n%C3%AD-na-potvrzen%C3%AD-1-k-%C4%8Demu-je-mempool
 [policy04]: /cs/newsletters/2023/06/07/#%C4%8Dek%C3%A1n%C3%AD-na-potvrzen%C3%AD-4-odhad-poplatk%C5%AF
-[aj mempool consistency]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-October/021116.html
+[aj mempool consistency]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-October/021116.html
 [se maxmempool]: https://bitcoin.stackexchange.com/questions/118137/how-does-it-contribute-to-the-bitcoin-network-when-i-run-a-node-with-a-bigger-th
 
diff --git a/_includes/specials/policy/cs/07-network-resources.md b/_includes/specials/policy/cs/07-network-resources.md
@@ -79,7 +79,7 @@ Příští týden prozkoumáme pravidla mempoolu jako vstupní brány protokolů
 druhé vrstvy a systémů chytrých kontraktů.
 
 [policy01]: /cs/newsletters/2023/05/17/#%C4%8Dek%C3%A1n%C3%AD-na-potvrzen%C3%AD-1-k-%C4%8Demu-je-mempool
-[unbounded]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011865.html
+[unbounded]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011865.html
 [lopp storms]: https://blog.lopp.net/history-bitcoin-transaction-dust-spam-storms/
 [ultraprune]: https://github.com/bitcoin/bitcoin/pull/1677
 [pooled resource]: /cs/newsletters/2023/05/03/#bitcoin-core-25325

diff --git a/_includes/specials/policy/cs/08-interface.md b/_includes/specials/policy/cs/08-interface.md
@@ -90,8 +90,8 @@ Tyto třecí plochy zdůrazňují nejen důležitost pravidel jako rozhraní pro
 v rámci ekosystému bitcoinu, ale také ukazují místa, která potřebují vylepšit.
 Příští týden se podíváme na návrhy pravidel a otevřené otázky.
 
-[full rbf pinning]: https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-May/003033.html
-[rbf ml]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019817.html
+[full rbf pinning]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-May/003033.html
+[rbf ml]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019817.html
 [n25038 notes]: https://bitcoincore.reviews/25038
 [policy01]: /cs/newsletters/2023/05/17/#čekání-na-potvrzení-1-k-čemu-je-mempool
 [policy02]: /cs/newsletters/2023/05/24/#čekání-na-potvrzení-2-incentivy

diff --git a/_includes/specials/policy/en/06-consistency.md b/_includes/specials/policy/en/06-consistency.md
@@ -96,6 +96,6 @@ network’s interests as a whole.
 
 [policy01]: /en/newsletters/2023/05/17/#waiting-for-confirmation-1-why-do-we-have-a-mempool
 [policy04]: /en/newsletters/2023/06/07/#waiting-for-confirmation-4-feerate-estimation
-[aj mempool consistency]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-October/021116.html
+[aj mempool consistency]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-October/021116.html
 [se maxmempool]: https://bitcoin.stackexchange.com/questions/118137/how-does-it-contribute-to-the-bitcoin-network-when-i-run-a-node-with-a-bigger-th
 
diff --git a/_includes/specials/policy/en/07-network-resources.md b/_includes/specials/policy/en/07-network-resources.md
@@ -85,7 +85,7 @@ will explore mempool policy as an interface for second-layer protocols and
 smart contract systems.
 
 [policy01]: /en/newsletters/2023/05/17/#waiting-for-confirmation-1-why-do-we-have-a-mempool
-[unbounded]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011865.html
+[unbounded]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011865.html
 [lopp storms]: https://blog.lopp.net/history-bitcoin-transaction-dust-spam-storms/
 [ultraprune]: https://github.com/bitcoin/bitcoin/pull/1677
 [pooled resource]: /en/newsletters/2023/05/03/#bitcoin-core-25325

diff --git a/_includes/specials/policy/en/08-interface.md b/_includes/specials/policy/en/08-interface.md
@@ -108,8 +108,8 @@ as an interface for applications and protocols in the Bitcoin
 ecosystem, but where it needs to improve. Next week’s post will
 discuss policy proposals and open questions.
 
-[full rbf pinning]: https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-May/003033.html
-[rbf ml]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019817.html
+[full rbf pinning]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-May/003033.html
+[rbf ml]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019817.html
 [n25038 notes]: https://bitcoincore.reviews/25038
 [policy01]: /en/newsletters/2023/05/17/#waiting-for-confirmation-1-why-do-we-have-a-mempool
 [policy02]: /en/newsletters/2023/05/24/#waiting-for-confirmation-2-incentives

diff --git a/_includes/specials/policy/fr/06-consistence.md b/_includes/specials/policy/fr/06-consistence.md
@@ -67,6 +67,6 @@ répondre aux intérêts du réseau dans son ensemble.
 
 [policy01]: /fr/newsletters/2023/05/17/#en-attente-de-confirmation-1--pourquoi-avons-nous-un-mempool-
 [policy04]: /fr/newsletters/2023/06/07/#en-attente-de-confirmation-4--estimation-du-taux-de-frais
-[aj mempool consistency]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-October/021116.html
+[aj mempool consistency]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-October/021116.html
 [se maxmempool]: https://bitcoin.stackexchange.com/questions/118137/how-does-it-contribute-to-the-bitcoin-network-when-i-run-a-node-with-a-bigger-th
 
diff --git a/_includes/specials/policy/fr/07-ressources-du-reseau.md b/_includes/specials/policy/fr/07-ressources-du-reseau.md
@@ -74,7 +74,7 @@ la semaine prochaine explorera la politique de mempool comme une interface pour
 et les systèmes de contrats intelligents.
 
 [policy01]: /fr/newsletters/2023/05/17/#en-attente-de-confirmation-1--pourquoi-avons-nous-un-mempool-
-[unbounded]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011865.html
+[unbounded]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011865.html
 [lopp storms]: https://blog.lopp.net/history-bitcoin-transaction-dust-spam-storms/
 [ultraprune]: https://github.com/bitcoin/bitcoin/pull/1677
 [pooled resource]: /fr/newsletters/2023/05/03/#bitcoin-core-25325

diff --git a/_includes/specials/policy/fr/08-interface.md b/_includes/specials/policy/fr/08-interface.md
@@ -78,8 +78,8 @@ Ces points de friction mettent en évidence non seulement l'importance de la pol
 et les protocoles dans l'écosystème Bitcoin, mais aussi les domaines dans lesquels elle doit s'améliorer. Le prochain article de la
 semaine prochaine abordera les propositions de politique et les questions ouvertes.
 
-[full rbf pinning]: https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-May/003033.html
-[rbf ml]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019817.html
+[full rbf pinning]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-May/003033.html
+[rbf ml]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019817.html
 [n25038 notes]: https://bitcoincore.reviews/25038
 [policy01]: /fr/newsletters/2023/05/17/#en-attente-de-confirmation-1--pourquoi-avons-nous-un-mempool-
 [policy02]: /fr/newsletters/2023/05/24/#en-attente-de-confirmation-2--mesures-dincitation

diff --git a/_includes/specials/policy/ja/06-consistency.md b/_includes/specials/policy/ja/06-consistency.md
@@ -74,5 +74,5 @@ RBFルールへの準拠を要求します。パージされたトランザク
 
 [policy01]: /ja/newsletters/2023/05/17/#承認を待つ-1-なぜmempoolがあるのか
 [policy04]: /ja/newsletters/2023/06/07/#承認を待つ-4-手数料率の推定
-[aj mempool consistency]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-October/021116.html
+[aj mempool consistency]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-October/021116.html
 [se maxmempool]: https://bitcoin.stackexchange.com/questions/118137/how-does-it-contribute-to-the-bitcoin-network-when-i-run-a-node-with-a-bigger-th
diff --git a/_includes/specials/policy/ja/07-network-resources.md b/_includes/specials/policy/ja/07-network-resources.md
@@ -72,7 +72,7 @@ witnessスタックに100を超える項目を持つP2WSHインプットは、
 来週の記事では、2ndレイヤープロトコルやスマートコントラクトシステムのインターフェースとしてのmempoolについて説明します。
 
 [policy01]: /ja/newsletters/2023/05/17/#承認を待つ-1-なぜmempoolがあるのか
-[unbounded]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011865.html
+[unbounded]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011865.html
 [lopp storms]: https://blog.lopp.net/history-bitcoin-transaction-dust-spam-storms/
 [ultraprune]: https://github.com/bitcoin/bitcoin/pull/1677
 [pooled resource]: /ja/newsletters/2023/05/03/#bitcoin-core-25325

diff --git a/_includes/specials/policy/ja/08-interface.md b/_includes/specials/policy/ja/08-interface.md
@@ -80,8 +80,8 @@ Pinningが問題になるのは、複数の参加者が共同でトランザク
 これらの摩擦点は、Bitcoinエコシステムにおけるアプリケーションとプロトコルのインターフェースとしてポリシーの重要性だけでなく、
 改善が必要な部分を浮き彫りにしています。来週の記事では、ポリシーの提案と未解決の問題について説明します。
 
-[full rbf pinning]: https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-May/003033.html
-[rbf ml]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019817.html
+[full rbf pinning]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-May/003033.html
+[rbf ml]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019817.html
 [n25038 notes]: https://bitcoincore.reviews/25038
 [policy01]: /ja/newsletters/2023/05/17/#承認を待つ-1-なぜmempoolがあるのか
 [policy02]: /ja/newsletters/2023/05/24/#承認を待つ-2-インセンティブ

diff --git a/_includes/specials/policy/zh/06-consistency.md b/_includes/specials/policy/zh/06-consistency.md
@@ -18,6 +18,6 @@ Bitcoin Core 的一些规则配置选项存在是为了适应节点操作环境
 
 [policy01]: /zh/newsletters/2023/05/17/#等待确认-1-我们为什么需要一个交易池
 [policy04]: /zh/newsletters/2023/06/07/#等待确认-4费率估算
-[aj mempool consistency]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-October/021116.html
+[aj mempool consistency]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-October/021116.html
 [se maxmempool]: https://bitcoin.stackexchange.com/questions/118137/how-does-it-contribute-to-the-bitcoin-network-when-i-run-a-node-with-a-bigger-th
 
diff --git a/_includes/specials/policy/zh/07-network-resources.md b/_includes/specials/policy/zh/07-network-resources.md
@@ -16,7 +16,7 @@
 我们可以看到，使用交易池规则来保护共享网络资源有助于保护网络的特性，并使未来协议的开发路径保持开放。与此同时，我们正在看到，如何在严格限制区块重量的情况下来扩展网络的矛盾正在推动着最佳实践、良好的技术设计和创新的采用：下周的文章将探讨交易池规则作为二层协议和智能合约系统的接口。
 
 [policy01]: /zh/newsletters/2023/05/17/#等待确认-1-我们为什么需要一个交易池
-[unbounded]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011865.html
+[unbounded]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011865.html
 [lopp storms]: https://blog.lopp.net/history-bitcoin-transaction-dust-spam-storms/
 [ultraprune]: https://github.com/bitcoin/bitcoin/pull/1677
 [pooled resource]: /zh/newsletters/2023/05/03/#bitcoin-core-25325

diff --git a/_includes/specials/policy/zh/08-interface.md b/_includes/specials/policy/zh/08-interface.md
@@ -18,8 +18,8 @@
 
 这些摩擦点不仅显示了交易池作为比特币生态系统中的应用和协议的接口的重要性，还指明了需要提升的地方。下周，我们会讨论交易池规则的变更提议以及悬而未决的问题。
 
-[full rbf pinning]: https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-May/003033.html
-[rbf ml]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019817.html
+[full rbf pinning]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-May/003033.html
+[rbf ml]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019817.html
 [n25038 notes]: https://bitcoincore.reviews/25038
 [policy01]: /zh/newsletters/2023/05/17/#等待确认-1-我们为什么需要一个交易池
 [policy02]: /zh/newsletters/2023/05/24/#等待确认-2激励

diff --git a/_includes/specials/taproot/en/17-keypath-universality.md b/_includes/specials/taproot/en/17-keypath-universality.md
@@ -68,6 +68,6 @@ contract even when it doesn't seem like an option.
 {% endauto_anchor %}
 
 [p4tr vaults]: /en/preparing-for-taproot/#vaults-with-taproot
-[maxwell taproot]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-January/015614.html
+[maxwell taproot]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-January/015614.html
 [irc log1]: https://gnusha.org/taproot-bip-review/2020-02-09.log
 [irc log2]: https://gnusha.org/taproot-bip-review/2020-02-10.log
diff --git a/_includes/specials/taproot/en/19-future.md b/_includes/specials/taproot/en/19-future.md
@@ -124,8 +124,8 @@ rules.
 
 [news166 tluv]: /en/newsletters/2021/09/15/#covenant-opcode-proposal
 [wuille entroot]: https://gist.github.com/sipa/ca1502f8465d0d5032d9dd2465f32603
-[towns groot]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-July/016249.html
-[maxwell graftroot]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-February/015700.html
+[towns groot]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-July/016249.html
+[maxwell graftroot]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-February/015700.html
 [p4tr multisignatures]: /en/preparing-for-taproot/#multisignature-overview
 [p4tr vaults]: /en/preparing-for-taproot/#vaults-with-taproot
 [rubin delegation]: /en/newsletters/2021/03/24/#signing-delegation-under-existing-consensus-rules
@@ -134,4 +134,4 @@ rules.
 [rubin pqc]: https://rubin.io/blog/2021/07/06/quantum-bitcoin/
 [poelstra cat]: https://www.wpsoftware.net/andrew/blog/cat-and-schnorr-tricks-i.html
 [bip32 reverse derivation]: https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki#implications
-[sipa groot agg]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-October/016461.html
+[sipa groot agg]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-October/016461.html
diff --git a/_includes/specials/taproot/en/21-thanks.md b/_includes/specials/taproot/en/21-thanks.md
@@ -501,6 +501,6 @@ accept taproot-compliant blocks, making it safe for everyone to use
 taproot's features.
 
 {% include linkers/issues.md issues="17977,19953" %}
-[maxwell taproot post]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-January/015614.html
+[maxwell taproot post]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-January/015614.html
 [good morning]: /en/preparing-for-taproot/#a-good-morning
 [news69 review]: /en/newsletters/2019/10/23/#taproot-review
diff --git a/_includes/specials/taproot/ja/17-keypath-universality.md b/_includes/specials/taproot/ja/17-keypath-universality.md
@@ -52,6 +52,6 @@ Taprootベースのコントラクトでkeypathを使用する機会があるか
 {% endauto_anchor %}
 
 [p4tr vaults]: /ja/preparing-for-taproot/#vaultとtaproot
-[maxwell taproot]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-January/015614.html
+[maxwell taproot]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-January/015614.html
 [irc log1]: https://gnusha.org/taproot-bip-review/2020-02-09.log
 [irc log2]: https://gnusha.org/taproot-bip-review/2020-02-10.log
diff --git a/_includes/specials/taproot/ja/19-future.md b/_includes/specials/taproot/ja/19-future.md
@@ -96,8 +96,8 @@ Bitcoinのコンセンサスルールを変更する労力に値するかどう
 
 [news166 tluv]: /ja/newsletters/2021/09/15/#covenant-opcode-proposal-covenant-opcode
 [wuille entroot]: https://gist.github.com/sipa/ca1502f8465d0d5032d9dd2465f32603
-[towns groot]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-July/016249.html
-[maxwell graftroot]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-February/015700.html
+[towns groot]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-July/016249.html
+[maxwell graftroot]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-February/015700.html
 [p4tr multisignatures]: /ja/preparing-for-taproot/#マルチシグの概要
 [p4tr vaults]: /ja/preparing-for-taproot/#vaultとtaproot
 [rubin delegation]: /ja/newsletters/2021/03/24/#signing-delegation-under-existing-consensus-rules
@@ -107,4 +107,4 @@ Bitcoinのコンセンサスルールを変更する労力に値するかどう
 [rubin pqc]: https://rubin.io/blog/2021/07/06/quantum-bitcoin/
 [poelstra cat]: https://www.wpsoftware.net/andrew/blog/cat-and-schnorr-tricks-i.html
 [bip32 reverse derivation]: https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki#implications
-[sipa groot agg]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-October/016461.html
+[sipa groot agg]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-October/016461.html
diff --git a/_includes/specials/taproot/ja/21-thanks.md b/_includes/specials/taproot/ja/21-thanks.md
@@ -486,6 +486,6 @@ Taprootのアクティベーションは始まりに過ぎません。
 誰もがTaprootの機能を安全に利用できるようになります。
 
 {% include linkers/issues.md issues="17977,19953" %}
-[maxwell taproot post]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-January/015614.html
+[maxwell taproot post]: https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-January/015614.html
 [good morning]: /ja/preparing-for-taproot/#a-good-morning
 [news69 review]: /ja/newsletters/2019/10/23/#taproot