fixup! add TLUV references

Author: jamesob

bip-0345.mediawiki

@@ -167,7 +167,9 @@ withdrawal by allowing a spending transaction to replace the
 <code>OP_VAULT</code> tapleaf with a prespecified script template, allowing for
 some parameters to be set at spend (trigger) time. All other leaves in the
 taptree must be unchanged, which preserves the recovery path as well as any
-other spending conditions originally included in the vault.
+other spending conditions originally included in the vault. This is similar to
+the <code>TAPLEAF_UPDATE_VERIFY</code> design that was proposed 
+[https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-September/019419.html in 2021].
 
 These tapleaf replacement rules, described more precisely below, ensure a
 timelocked withdrawal, where the timelock is fixed by the original
@@ -598,6 +600,7 @@ deployments for OP_CHECKSEQUENCEVERIFY and OP_CHECKLOCKTIMEVERIFY (see
 * [https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-February/012470.html [bitcoin-dev] Bitcoin Vaults (2016)]
 * [https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-February/015793.html [bitcoin-dev] Simple lock/unlock mechanism (2018)]
 * [https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-April/017755.html [bitcoin-dev] On-chain vaults prototype (2020)]
+* [https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-September/019419.html [bitcoin-dev] TAPLEAF_UPDATE_VERIFY covenant opcode (2021)]
 * [https://arxiv.org/abs/2005.11776 Custody Protocols Using Bitcoin Vaults (2020)]
 * [https://jameso.be/vaults.pdf Vaults and Covenants (2023)]