WrappedBTC / bitcoin-token-smart-contracts

MIT License
132 stars 96 forks source link

WBTC Sent to contract address #15

Open flip909 opened 4 years ago

flip909 commented 4 years ago

Hi, Is there a way to recover WBTC from the contract address via the DAO or other?

I have sent a reasonable portion of my portfolio to the contract address by mistake...

Can see that the reclaim function is for the owner only. I read that its controlled by a DAO and to reach out if funds were sent to the contract.

Thanks for any help

yaronvel commented 4 years ago

hey @flip909, i can confirm that it seems this can be technically done. And the relevant dao members will be approached to trigger it.

flip909 commented 4 years ago

Thank you so much. Really appreciated.

Would I have to provide TX info or would the function send any WBTC that was sent to the contract address, back to senders addresses?

yaronvel commented 4 years ago

Thank you so much. Really appreciated.

Would I have to provide TX info or would the function send any WBTC that was sent to the contract address, back to senders addresses?

providing the tx and sender address would help, to make sure both sides means the same return address and amount. In any case it would send it back the the sender.

If you could provide a digital signature with the sender address (or a message of your choice) it would be even better. This could help you sign https://mycrypto.com/sign-and-verify-message/sign

flip909 commented 4 years ago

Thank you so much. Really appreciated. Would I have to provide TX info or would the function send any WBTC that was sent to the contract address, back to senders addresses?

providing the tx and sender address would help, to make sure both sides means the same return address and amount. In any case it would send it back the the sender.

If you could provide a digital signature with the sender address (or a message of your choice) it would be even better. This could help you sign https://mycrypto.com/sign-and-verify-message/sign

TX : 0xb0fb97ae17cf78523749faa9d1630e636960ec0a261f300d2ba977e699fa40e8

Address : 0x617e1eeddc9953beabdf21e03b8ecc1cfdc39149

Signature : { "address": "0x617e1eeddc9953beabdf21e03b8ecc1cfdc39149", "msg": "hi yaronvel, proof of address ownership for issue #15", "sig": "0xdc256bffb81fe354f6fa71a1c34ea4514bc1f0d5d445a36d30271175cfba8e1d0aa5f68a3c2980c4751ecc24ba58c27a29a6e445d4b7d3fd48097b38c29952e11c", "version": "2" }

ravz commented 4 years ago

hello, I would really appreciate mine too please

TX : 0xfbf5d77ac175a7e3f1e9f30dfd734ad5f7a58fd9efa97ce9296dea9f202aa9e5

Address : 0x382126c0849d6f62ebc49c3732394ecc482f0767

Signature : { "address": "0x382126c0849d6f62ebc49c3732394ecc482f0767", "msg": "hi yaronvel, proof of address ownership for issue #15", "sig": "0xca5bc3c79eec514cf886173354ef26e32acc06f2c765f0b059f78a43fb3222e9529925fc2e541c767efa7d5de412cc59573762ccd0289f58eb061168ec12b0731c", "version": "3", "signer": "MEW" }

flip909 commented 3 years ago

Thank you so much. Really appreciated. Would I have to provide TX info or would the function send any WBTC that was sent to the contract address, back to senders addresses?

providing the tx and sender address would help, to make sure both sides means the same return address and amount. In any case it would send it back the the sender.

If you could provide a digital signature with the sender address (or a message of your choice) it would be even better. This could help you sign https://mycrypto.com/sign-and-verify-message/sign

Hi @yaronvel , may I ask how things are moving along? thanks.

yaronvel commented 3 years ago

@ravz @flip909 to the best of my knowledge, a sufficient quorum was still not formed, hence the vote was not initiated. You can find a list of the DAO members here. 11 members must approve it.

ravz commented 3 years ago

@yaronvel are you able to tell us which members have agreed to-date

flip909 commented 3 years ago

Thanks. may I have some detail about the proposal number or some identifier so I may try to contact them directly?

yaronvel commented 3 years ago

Thanks. may I have some detail about the proposal number or some identifier so I may try to contact them directly?

a proposal was not initiated yet, so it does not have a concrete identifier or proposal number.

yaronvel commented 3 years ago

@yaronvel are you able to tell us which members have agreed to-date

I prefer not to refer to off-chain discussions. I could say that there is not really an opposition to that proposal. But only few actively committed to vote.

flip909 commented 3 years ago

Thanks.

Is the proposal still open?

yaronvel commented 3 years ago

Thanks.

Is the proposal still open?

It never got open (in the technical sense). It is still in the offchain stage, where the support of the dao members is being inquired

flip909 commented 3 years ago

Many thanks for your help @yaronvel, it is appreciated.

Am trying to contact DAO members and make them aware of this situation. If I am able to contact at least 11 and get agreement, you are able to help proceed with this through the correct process?

yaronvel commented 3 years ago

Many thanks for your help @yaronvel, it is appreciated.

Am trying to contact DAO members and make them aware of this situation. If I am able to contact at least 11 and get agreement, you are able to help proceed with this through the correct process?

If 11 members to express their support it should be enough for the process to start. Personally I can help encoding transactions, but I do not hold any keys that can execute such transactions. One of the supporting members would have to do it, but I do not expect it to be a problem.

ravz commented 3 years ago

hi @yaronvel could you please have another attempt to convince the DAO members to support this

tranvictor commented 3 years ago

hi @ravz, this is Victor from Kyber. Your WBTC amount is significant, Kyber and Yaron will try to convince the Dao in the next few days.

Hi @flip909, since your amount is not as significant, we will have to prioritize it after Ravz's but we will try our best as well. Please understand.

tranvictor commented 3 years ago

Our procedure will be this:

  1. the DAO will call 0xca06411bd7a7296d7dbdd0050dfc846e95febeb7.callReclaimToken() to send all WBTC in the WTBC contract to itself as it is the owner of WBTC contract. This needs 11 approvals out of 18 members.
  2. the DAO will call 0xca06411bd7a7296d7dbdd0050dfc846e95febeb7.reclaimToken() to send all WBTC there (as result of the previous operation) to the DAO as the DAO is the owner of 0xca06411bd7a7296d7dbdd0050dfc846e95febeb7. This needs 11 approvals out of 18 members as well.
  3. the DAO will call WBTC.transfer() to transfer the WBTC to 0x4dbbbFb0e68bE9D8F5a377A4654604a62E851e80. This is WBTC mini DAO which requires 5 out of 7 approvals to do an operation.
  4. the mini DAO will call WBTC.transfer() to transfer 879314800 (wbtc wei) to @ravz at 0x382126c0849d6f62ebc49c3732394ecc482f0767.
  5. the mini DAO will call WBTC.transfer() to transfer 7854583 (wbtc wei) to @flip909 at 0x617e1eeddc9953beabdf21e03b8ecc1cfdc39149.

@ravz @flip909 please confirm that you agree with the procedure. Thanks.

ravz commented 3 years ago

thank you @tranvictor and I agree

junkfoodcb commented 3 years ago

Our procedure will be this:

  1. the DAO will call 0xca06411bd7a7296d7dbdd0050dfc846e95febeb7.callReclaimToken() to send all WBTC in the WTBC contract to itself as it is the owner of WBTC contract. This needs 11 approvals out of 18 members.
  2. the DAO will call 0xca06411bd7a7296d7dbdd0050dfc846e95febeb7.reclaimToken() to send all WBTC there (as result of the previous operation) to the DAO as the DAO is the owner of 0xca06411bd7a7296d7dbdd0050dfc846e95febeb7. This needs 11 approvals out of 18 members as well.
  3. the DAO will call WBTC.transfer() to transfer the WBTC to 0x4dbbbFb0e68bE9D8F5a377A4654604a62E851e80. This is WBTC mini DAO which requires 5 out of 7 approvals to do an operation.
  4. the mini DAO will call WBTC.transfer() to transfer 879314800 (wbtc wei) to @ravz at 0x382126c0849d6f62ebc49c3732394ecc482f0767.
  5. the mini DAO will call WBTC.transfer() to transfer 7854583 (wbtc wei) to @flip909 at 0x617e1eeddc9953beabdf21e03b8ecc1cfdc39149.

@ravz @flip909 please confirm that you agree with the procedure. Thanks.

Hi @tranvictor i opened another isssue (#17 ) but should have commented here. i did the same thing here's my tx https://etherscan.io/tx/0xaccd5fc1440677e4c625e9e03e9a77a83e7c9b125b7b847e19a76f856605cc1c

i agree to the procedure above and hoping you can help me out too. thanks in advance.

flip909 commented 3 years ago

Our procedure will be this:

  1. the DAO will call 0xca06411bd7a7296d7dbdd0050dfc846e95febeb7.callReclaimToken() to send all WBTC in the WTBC contract to itself as it is the owner of WBTC contract. This needs 11 approvals out of 18 members.
  2. the DAO will call 0xca06411bd7a7296d7dbdd0050dfc846e95febeb7.reclaimToken() to send all WBTC there (as result of the previous operation) to the DAO as the DAO is the owner of 0xca06411bd7a7296d7dbdd0050dfc846e95febeb7. This needs 11 approvals out of 18 members as well.
  3. the DAO will call WBTC.transfer() to transfer the WBTC to 0x4dbbbFb0e68bE9D8F5a377A4654604a62E851e80. This is WBTC mini DAO which requires 5 out of 7 approvals to do an operation.
  4. the mini DAO will call WBTC.transfer() to transfer 879314800 (wbtc wei) to @ravz at 0x382126c0849d6f62ebc49c3732394ecc482f0767.
  5. the mini DAO will call WBTC.transfer() to transfer 7854583 (wbtc wei) to @flip909 at 0x617e1eeddc9953beabdf21e03b8ecc1cfdc39149.

@ravz @flip909 please confirm that you agree with the procedure. Thanks.

Hi @tranvictor , thank you for assisting.

I agree and welcome the help.

junkfoodcb commented 3 years ago

@yaronvel @tranvictor realized i didn't sign message as requested above to prove ownership. here you go....thx.

TX: 0xaccd5fc1440677e4c625e9e03e9a77a83e7c9b125b7b847e19a76f856605cc1c

ADDRESS: 0x00C67d9D6D3D13b42a87424E145826c467CcCd84

{ "address": "0x00C67d9D6D3D13b42a87424E145826c467CcCd84", "msg": "hi yaronvel, proof of address ownership for issue #15", "sig": "0x68b6e30f2f853e75501f3737ae5af5b79b1553708dfcb648dee16cb572dae7f476f1194e6601b229131d4d6db89d1cde32a69cdb86143d9a260d4760ec86f0181b", "version": "2" }

ravz commented 3 years ago

hi @tranvictor any luck with convincing the DAO ?

ravz commented 3 years ago

hi @tranvictor any way we can push this along ?

ravz commented 3 years ago

Hi @tranvictor I'm sorry to be pestering but as you can imagine this is quite important for me; was there any progress in trying to get the DAO to vote on this?

ravz commented 3 years ago

please, can someone care enough to respond

junkfoodcb commented 3 years ago

hi @tranvictor and @yaronvel -- any chance of an update? thanks!

tranvictor commented 3 years ago

@ravz @junkfoodcb and everyone, i'm sorry i have been pushing the dao for a few times and haven't got any assistance, i will keep pushing once in a while but at the end of the day it is out of my control, i'm already doing my best.

junkfoodcb commented 3 years ago

@ravz @junkfoodcb and everyone, i'm sorry i have been pushing the dao for a few times and haven't got any assistance, i will keep pushing once in a while but at the end of the day it is out of my control, i'm already doing my best.

Thanks for the update and I appreciate your help in the matter.

ravz commented 3 years ago

thanks @tranvictor appreciate it

ravz commented 2 years ago

is anyone from the DAO available to help with this issue?

ravz commented 2 years ago

can anyone please assist on this?

aymeric76100 commented 2 years ago

hello I have the same problem.

TX : 0x7d4ac8f0209074ef0ac6a62fb09a4307cb0c38491131671ab2f827b3d95f6950

Address : 0x2e86c1e969f3c121ed865cf4d7879744c9c353df

Signature : { "address": "0x2E86c1E969F3c121eD865CF4d7879744c9c353df", "msg": "address : \"0x2e86c1e969f3c121ed865cf4d7879744c9c353df\nmsg : hi yaronvel, proof of address ownership for issue #15\n", "sig": "0x1881d551d408628a240e80002ca41c08a055495509e7234aecabf33ec20c82c700a9c484b0ce768b2a4d7e23ca26b0cc3574af3dd2ce58233acaca0ce2a7851a01", "version": "2" }

gosuto-inzasheru commented 2 years ago

this is ridiculous; 8 wbtc stuck in the contract, for which a safety function exists, but the "dao" is too lazy to call the function or even respond.

aymeric76100 commented 2 years ago

anyone to answer?

aymeric76100 commented 2 years ago

? :_( svp

ravz commented 2 years ago

Victor Tran from KNC has been the only DAO representative to respond to me, he has attempted multiple times to get the DAO to vote and still nothing. Its very frustrating, I understand that this was the fault of my own stupidity but still the DAO can do something here for very little effort.

I urge others to also comment on the issue here in the hopes that they may see it and do something https://github.com/WrappedBTC/DAO/issues/9

aymeric76100 commented 2 years ago

I beg you, I too sent 0.528 wbtc by mistake (It's an inportant sum for me) I spent 2 nights without sleeping so much I feel bad. please

gosuto-inzasheru commented 2 years ago

As a member of the community, I would like to file the following proposal to the WBTC "DAO":

Once per year, the WBTC contract is swept of any accidental WBTC sent to the contract. The contract has a function specifically designed for this. After the DAO takes a 20% fee, it then returns the rest of the WBTC to the original sender.

I believe this to be a win for all parties; the fee is used to pay the DAO members for their efforts and time invested in this procedure and the user sees back a large sum of their misguided funds.

If this is not the right place and/or way to submit proposals, I am happy to do be redirected elsewhere.

aymeric76100 commented 2 years ago

Yes, yes yes. It would be great if it happened like this.

aymeric76100 commented 2 years ago

is there any news?

aymeric76100 commented 2 years ago

?

cryptovyp commented 2 years ago

same problem, some news? i also write on twitter https://twitter.com/WrappedBTC today but for now no reply, there is other way to contact devs for this problem?

thanks

flip909 commented 2 years ago

Hey All,

I was the one opening this thread. I have tried to contact the individual DAO members regarding this matter with not much sucess. Suggest we all get in a Telegram group and make a plan to reach out to DAO members. I had contact with a couple of them who were willing to help, if we worked together we could probably get in touch with enough required individuals?

Join here if interested in co-ordinating this : https://t.me/+A7yJh2V2eadjZWU0

Best regards

rggithubether commented 1 year ago

hello @flip909 was ur issue resolved? i got the same issue and i just opened a new issue #50.

joekoh-bg commented 1 year ago

Hi, @aymeric76100 you will need to confirm ownership of your address by using the "Sign Message" function here: https://etherscan.io/verifiedSignatures if you want the wbtc returned to you.

The message you posted above looks like it has a copy-paste error and I also cannot verify the signature based off of the information you provided.

aymeric76100 commented 1 year ago

what should i write in the message? Thank you so much

aymeric76100 commented 1 year ago

https://etherscan.io/verifySig/16513 I signed, so it's correct?

rggithubether commented 1 year ago

hi @joekoh-bg would u be able to help me returned my WBTC as well. its been 5 months. here's the github issue #50, i would appreciate your help.

https://github.com/WrappedBTC/bitcoin-token-smart-contracts/issues/50

supervyper2 commented 1 year ago

hallo, i am supervyper, just sign here https://etherscan.io/verifySig/16580 to prove my address this the transaction https://etherscan.io/tx/0xc5597905ff7ba1d4925559d27731baac452d47d27d0111758dae6ed7db935776

thanks for help!