Issue a correction in the miniscript bug blogpost

diff --git a/docs/_blog/miniscript_vulnerability.md b/docs/_blog/miniscript_vulnerability.md
index 16d79026fd067ffc994f5d51f6c8ac88ea52c11c..bdb8730ae4d6c1106c676cbefe1cc1b1c0076889 100644 (file)
--- a/docs/_blog/miniscript_vulnerability.md
+++ b/docs/_blog/miniscript_vulnerability.md
@@ -75,6 +75,13 @@ The tool we used has been [published on GitHub][tool-link] and can be run by any
 
 We would like to thank [`sanket1729`][sanket1729] and [`RCasatta`][RCasatta] for their help implementing and running the tool on the bitcoin mainnet blockchain.
 
+## Correction (2022-04-25)
+
+By re-running the tool on the mainnet blockchain for a second time we were able to find one vulnerable output, created and spent a long time ago (around the initial announcement and release date of Miniscript).
+
+The amount was negligible, so we believe this was a small test performed by somebody to play with Miniscript.
+
+
 [spending-policy-demo]: /blog/2021/02/spending-policy-demo
 [security-advisory]: https://github.com/rust-bitcoin/rust-miniscript/blob/70191e5a32f7c072d32476ba0b8861ca57af3df8/doc/security_report_2022_04_20.md
 [blocks-iterator]: https://github.com/RCasatta/blocks_iterator