-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sweep all wbtc from contract sent there by mistake #17
Comments
thanks @gosuto-inzasheru any ETA on when you would do the sweep? |
|
I inited the multisig tx to reclaim all WBTC from WBTC token contract to its owner here: 0x24abcb53aff77c7e32fed1b086ecec696d6d055a7b522692d2e19e1e27ac5e1d After everyone approved and executed this tx, all WBTC on WBTC contract will be transferred to 0xca06411bd7a7296d7dbdd0050dfc846e95febeb7 (this is WBTC token controller contract)
Next, we need to reclaim it from the token controller contract to its owner (WBTC dao multisig). I also init that tx here: 0x9129baedf5a6e209d1f68fec0227dffbeeefcb27b8a67516eb36661f2e47afe5 After everyone approved and executed this tx, all WBTC on the controller (that was supposed to transferred after the first msig tx was executed) will be transferred to WBTC dao multisig at 0xB33f8879d4608711cEBb623F293F8Da13B8A37c5
|
hi, who are we waiting on ? |
What about those that sent tokens to the contract from CEX's? |
it is very difficult if not impossible to verify their identity and send it back, so for now cex addresses have been excluded from the airdrop csv |
We have successfully transferred the WBTC to the gnosis safe msig, ready to distribute guys :) Will coordinate the distribution in the next few days. |
hi @tranvictor thanks for this, I hope we can finally get to an end result of people having their funds returned. |
Hi @ravz, since it is a lot of coordination effort, although it is possible, i still strongly suggest to avoid it and still receive the fund in your original address. |
@tranvictor ok that's fine, could you provide an estimate for when the transaction will occur? I need to transfer it out straight away (it's an old unused wallet and I dont know if its been compromised) |
In this comment (#17 (comment)) i mistakenly said the fund was moved to the msig waiting to distribute. The correct progress is we moved the fund to the big dao msig and since there will be many transfer, we need to move the fund to a safe gnosis msig then do another tx to distribute to everyone at once. So 2 more txs. First is to move to safe gnosis msig, Second is to distribute. Bitgo is about to init the first one, it will take at least a week to be done since many approvals are needed. Second one will be inited right after the first one is done and it only needs 3 approvals, would take only 1-2 days IMO. So i would guess 10 days from now. |
hi @tranvictor I see the tokens are now being held here https://etherscan.io/address/0xb33f8879d4608711cebb623f293f8da13b8a37c5 |
quite some funds were sent to the wbtc contract directly by mistake over the years.
luckily the contract has a function (
reclaimToken
) which sweeps a particular erc20 back toowner
. the controller would need to call that function, forward all those tokens to the newly deployed safe msig and from there they can be distributed amongst users.naive airdrop csv file (ie return to sender), compatible with safe's csv airdrop app:
note: some of these destinations are cex wallets (coinbase, okx, hoo, crypto.com, bittrex, coinlist) which we might want to avoid sending to (in order to prevent funds getting stuck on the other side)... that being said, it is probably impossible to determine for all destinations whether it is still alive/accessible/in use etc.
The text was updated successfully, but these errors were encountered: