Back to Referenda
Proposal #41
Referenda #41
Recovering funds impacted by the unsupported Bitcoin version bug
3mos ago
PreimageInvalid

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

Edited
Reply
Up 2
Share
Votes
AyePassing thresholdNay
50%50%
Aye
0 vKINT
Nay
0 vKINT
Turnout
0 vKINT
Electorate
0 vKINT
Check all votes
Passed

How Kintsugi Governance Works.

Metadata
Proposer
Hash
Delay
0
End
02022-06-26 08:12:00
Threshold
Call
Table
Json
callIndex0x1f02
sectiontreasury
methodapproveProposal
args
proposalId9
TimelineLatest activity 3mos ago
2022-06-09 07:51:06
Proposed
Index
#41
2022-06-17 12:04:30
Tabled
Referenda Index
#41
Deposit
5 vKINT
2022-06-17 12:04:30
Started
referendumIndex
41
voteThreshold
SuperMajorityAgainst
2022-06-26 08:12:00
Passed
referendumIndex
41
2022-06-27 12:40:12
PreimageInvalid
proposalHash
0x0714bc351f70f6b6d73092444bbdf423702794993580b0359bbbafaba76eaa7a
referendumIndex
41
Comments
3mos ago

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.

Reply
Up
3mos ago

@a3aP...FtV4
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

Edited
Reply
Up 1