Whilst 100% believe you, in terms of precedent, it would be good to format this proposal with:
1. Headline description of bug - in this case would be: `Using An Unsupported Bitcoin Version`
2. Method to identify that this vault is affected by the bug
3. on-chain proof that the vault suffered as a result

I guess for this particular issue you could also get the article owner to confirm that your listed vault was indeed affected for these amounts, however that is a bit centralized.

[@a3aP...FtV4](/member/a3aPvmjypKaDtjRgYbDL2CCkseYR3SLwvPevL6j7wF67aFtV4) 
that's fair points. For some of them only the dev team working on the bug identification and ways to fix or not to fix is able to confirm some identity. 
Adding here my discord id (Marvel#5748) to help better identification


I am the owner of the vault impacted by the unsupported bitcoin version bug detailed in the Kintsugi post mortem here  https://medium.com/interlay/kintsugi-the-first-60-days-of-decentralized-bitcoin-87085c2bf717

As of today, 19 KSM and 0.02 BTC are locked and can't be recovered. I've submitted a treasury proposal to get some KINT as partial compensation

Recovering funds impacted by the unsupported Bitcoin version bug