 Show Posts
|
|
Pages: [1]
|
If anyone attempting to recover BTC from a Coinbase multisig vault happens to find this thread, I can confirm this github project worked for me. https://github.com/pilsnerbeer/multisig-tool-fixedI have absolutely no affiliation with the github user. I had everything I needed all thee public keys, the users seed and the shared encrypted seed as well as the password used to encrypt the shared seed. If you don't have the required items listed above, this solution won't work for you. One issue that almost tripped me up is the following: when I attempted to send BTC from a multisig wallet ( Legacy (P2PKH): addresses start with a 1) to a newly created wallet (Native SegWit (bech32): addresses start with bc1), the process did not complete. When I used a wallet address that starts with a 3 (Nested SegWit (P2SH): addresses start with a 3) the process worked. see the article below on wallet address types https://help.crypto.com/en/articles/4056348-send-and-receive-btc-ltc-difference-between-segwit-and-legacy-address |
|
|
|
|
Yes, the encrypted shared seed starts with 6P.
The encrypted shared seed is 58 characters in length.
the "cold key" that I found in an old version of my password manager is 30 random characters, not words like a "seed phrase".
regardless, I am getting a pop-up message stating: "Incorrect passphrase for this encrypted private key."
|
|
|
|
|
I'm not sure if this thread can be revived but I may have located what I need but have no idea how to use it.
Long story short, I found an old dead android phone, ordered a battery for it, got it unlocked and while the device was disconnected from the internet, opened my password manager on this device and found an old entry for Coinbase labeled "cold key used to encrypt other keys"
I would like to test decryption of the encrypted shared seed with this key but the only decryption tools I am finding need the "encrypted seed" and a "seed phrase"... I don't have a seed phrase... I have an actual 30 character key. no words, no spaces...
Any suggestions for this situation would be appreciated.
|
|
|
|
Thanks for saving me the couple hundred $$ trying to brute force it. I would, however, like to understand this post a little better https://bitcoin.stackexchange.com/questions/57207/how-to-derive-the-private-key-associated-with-a-coinbase-multi-sig-vault-addressThat seems pretty close to my situation, but I actually have more information than that user did. I certainly don't have the comprehension of the problem that user does, unfortunately.... This probably isn't the best place to ask but wanted to toss it out here. He seemed to be able to obtain everything he needed from getting access to the master private key and the extended private key using ONLY the user seed. Sorry, not trying to be dense, but I am not understanding the difference I am attempting to contact the OP for that post as well thanks |
|
|
|
Users picked their own passphrase, so it depends on how good OP's password picking abilities at the time were. Also, there is hopefully a higher chance he remembers some of a password or passphrase he picked himself rather than one he was given.
In the event anyone else in the same boat is following this thread my post on stack exchange covers how to test decryption of shared seed for a multisig vault https://bitcoin.stackexchange.com/questions/111851/how-to-test-decryption-of-shared-seed-for-a-multisig-vaultUnfortunately, all my attempts at a password failed. In addition to that, researching my email leads me to believe I was using a password manager that supports strong password creation at the time of the vault creation so I didn't pick a password. That is what rubs me the wrong way in this situation since I stored (what I thought to be) all the essential information for the vault (user seed, shared seed, all three public keys, etc). I was (and still am) a noob and didn't understand any of the working parts. Continuing down the rabbit hole... On the topic of brute forcing, This YouTube video covers running BTCRecover with Vast.ai (rented servers) https://www.youtube.com/watch?v=8Zqc-2Te3zQ and in the first 10 seconds, he states that "In one 24 hour period, with $50 worth of hash power, this could knock over about as much as my CPU could do if it was running for 3 years straight" I fully understand attempting BIP38 wallet recovery on rented servers is not secure, as there is no ability to do any kind of "Wallet Extract" or anything like that. The server owner would possess the key if decryption succeeds. My two questions are this: As my wallet is multisig, does that decrease the risk dramatically? Assuming the answer to the above question is "yes", I'd be willing to throw a few hundred $$ at this which would get me over a decade of hashing power. Besides, it will make a funny story if nothing else. Assuming my password generator did a great job and produced a really awesome completely random password is a decade going to even come close or are we talking over 100 years to crack? It is not easy to find answers on BIP38, everything seems to be focused on BIP39. |
|
|
|
It would seem so. Is it indeed BIP38 encrypted? It should start with "6P" if it is.
Yes, the encrypted shared seed starts with "6P". but I am thoroughly confused, there is a single vault password and single encrypted shared seed... how does that correspond to two different public addresses? |
|
|
|
|
I have found a way to test decrypting the shared user seed and none of the passwords that I have work.
As I see it, my only option is to attempt to brute force the password used to (BIP38) encrypt the shared seed since coinbase is no longer signing tx, does that sound correct?
Looking into BIP38 brute forcing... the encrypted seed and public address (and dictionaries) are used for the process.
Another point of confusion for me... which address? Allow me to explain...
I have two transactions going into "My Vault" and each transaction went into a separate bitcoin address.
|
|
|
|
I am not certain that I do not know the decryption key for the shared seed. Unfortunately, there isn't any way to "test" it.
So essentially what I need is to find someone that understands the decryption process discussed in the ReadMe on the coinbase multisig github https://github.com/coinbase/multisig-tool#bip38 since that is how coinbase decided to do it. and once I verify the password or verify I do not know the password, I could determine next steps... does that sound accurate? |
|
|
|
So you my be able to download and tweak the .js files a bit to find what you need and change it.
I don't know enough about js and the app itself to be sure what would need to be changed. You would also have to find were the /addr is located and change it to /address and a few other things, but I don't see it as an impossible task. Just a long and annoying one.
-Dave
I could potentially make the change you are suggesting to the js file and I am not necessarily opposed to long and annoying (you have no idea how much work I have put into this already). Unfortunately I am a terrible programmer and cannot read or write code well at all and I don't trust myself not to screw it up. On top of that, this is only step 1 and I don't even comprehend steps 2 or step 3-a or step 3-b
I was under the impression that Coinbase's multisig vaults have long been discontinued and they removed all support for them, and so this will no longer be an option. But regardless of what I think - have you tried this? It seems like it would solve all your problems if it is possible.
If you do not have the decryption key (and the above is not possible), then your options are limited to either brute forcing the decryption key so you can use the user seed and shared seed, or seeing if Coinbase will give you access to the Coinbase seed linked to your account (which seems highly unlikely).
I can see my vault on coinbase and when I click "withdraw from vault" nothing happens. I am not certain that I do not know the decryption key for the shared seed. Unfortunately, there isn't any way to "test" it. |
|
|
|
|
sorry about that. one of my first replies suggested I post on the electrum board.
my bad.
|
|
|
|
The lack of a seed phrase isn't the most pressing issue right now. You can worry about how to turn the private keys (rather than seed phrases) in to a wallet later. The first thing you need to obtain is 2 of the 3 private keys.
You have the user seed private key. You will never obtain the Coinbase seed private key, since that was only ever held on Coinbase's servers. You have the shared seed private key, but it is encrypted. If you cannot decrypt it, then you will never be able to recover your wallet?
Do you remember the decryption password? If not, then the first thing you are going to have to do is to try to brute force it.
Agreed, not the most pressing issue. But the possession of a seed phrase as opposed to a "user seed" and a "user public key" and a "shared seed" and a "shared public key" and a "coinbase public key" and a password would simplify things incredibly and that is the frustration. Not at any of you, obviously... In fact, I really appreciate all the responses I am getting. I do not have the decryption password recorded so that may be an issue but the good news is I have the user seed and according to Coinbase's email, (refereced in this post) https://bitcointalk.org/index.php?topic=5316286.msg59002082#msg59002082What if I don’t know my vault password?
If you don’t know your vault password, you can instead copy/paste the user seed into the password field. This will allow you to approve your withdrawal. The user seed was provided to you when you created your multisig vault. So I should be good, right?  I am sure there is a catch...  |
|
|
|
I have the following: (these are just random numbers formatted to look real, they are not valid) - # User seed: (53 characters)
- # User public key: xpub661MyMwAqRbcH1atMf3cfeVgjA4SPncUpKx24PXcD3sY8dpkXapCD4EgviZ6EkEww9seSd7rum2 jRYz5rudFj6gHZT432sHSNHhysqFuYuC
- # Shared seed (encrypted): (58 characters)
- # Shared public key: xpub661MyMwAqRbcH1atMf3cfeVgjA4SPncUpKx24PXcD3sY8dpkXapCD4EgviZ6EkEww9seSd7rum2 jRYz5rudFj6gHZT432sHSNHhysqFuYuC
- # Coinbase public key: xpub661MyMwAqRbcH1atMf3cfeVgjA4SPncUpKx24PXcD3sY8dpkXapCD4EgviZ6EkEww9seSd7rum2 jRYz5rudFj6gHZT432sHSNHhysqFuYuC
can I recover a Coinbase multisig wallet (created in 2016) into electrum using the steps mentioned in this post https://bitcointalk.org/index.php?topic=2088713.msg20875786#msg20875786The lack of a seed phrase is what makes recovering a coinbase multisig vault as difficult as it is. I am no python coder (not coder at all) but was able to get the code from this post on stack exchange https://bitcoin.stackexchange.com/questions/57207/how-to-derive-the-private-key-associated-with-a-coinbase-multi-sig-vault-address to produce something similar to the following: (these are just random numbers formatted to look real, they are not valid) - Master Private Key corresponding to seed: xprvz3PCl3Goz8yXxYt9mx6I9B2YXNX7ulTU0O2a6T43OfjP23A2ahmwx72iJVkmTWy0ZmBZMZcIkVv bZteiiHkucAZFdK1m1kjfMB6542qggKO
- Master Public Key corresponding to seed: xpub661MyMwAqRbcEzdGMFKZXuVwbyHY2zKhiw6YFTrULfNBF53QVfXyoAiKMZKWkQA5444NXtLj9HP mgyN1xLCiJJ9dKAy4nLZJ87trHRnwUDb
- Extended Private key at index 14: xprvz3PCl3Goz8yXxYt9mx6I9B2YXNX7ulTU0O2a6T43OfjP23A2ahmwx72iJVkmTWy0ZmBZMZcIkVv bZteiiHkucAZFdK1m1kjfMB6542qggKO
- WIF format of that key: 3OfjP23A2ahmwx72iJVkmTWy0ZmBZMZcIkVvbZteiiHkucADVDA
Not sure what exactly to do with the values produced from the user seed as that is only 1 of the signatures for a 2 of 3 vault |
|
|
|
So, Coinbase multisig vaults were a 2-of-3 multisig. One key was held solely by Coinbase. One key was held solely by the user. The third key was held by both Coinbase and the user in an encrypted form, with the password you have being the decryption key. When you logged in to the vault, you used your password to decrypt the shared key, which allowed you to make transactions on Coinbase's website using Coinbase's key and the shared key.
Based on that, a seed phrase and a password alone are not going to be enough to access your coins. You also need the shared key which your password decrypts. If you do not have this backed up as well, then your only hope is going to be to ask Coinbase nicely if they still have it stored and can send it to you.
I also don't think Coinbase provided a seed phrase at all for the user key; I think it was an actual private key. You should therefore have two strings of seemingly random letters and numbers, one which will be your user key and the other which will be your encrypted shared key.
You are absolutely correct, end users were not provided a seed phrase. Upon the creation of a (multisig) vault, Coinbase provided the following: (these are just random numbers formatted to look real, they are not valid) - # User seed: L3XCYcQ2pwY3YTuwyPXzWsvVtGnCp4zL2ajP3XQt2pVhPuKiVM7r
- # User public key: xpub661MyMwAqRbcEzdGMFKZXuVwbyHY2zKhiw6YFTrULfNBF53QVfXyoAiKMZKWkQA5444NXtLj9HP mgyN1xLCiJJ9dKAy4nLZJ87trHRnwUDb
- # Shared seed (encrypted): z3PCl3Goz8yXxYt9mx6I9B2YXNX7ulTU0O2a6T43OfjP23A2ahmwx72iJ
- # Shared public key: xpub661MyMwAqRbcEzdGMFKZXuVwbyHY2zKhiw6YFTrULfNBF53QVfXyoAiKMZKWkQA5444NXtLj9HP mgyN1xLCiJJ9dKAy4nLZJ87trHRnwUDb
- # Coinbase public key: xpub661MyMwAqRbcEzdGMFKZXuVwbyHY2zKhiw6YFTrULfNBF53QVfXyoAiKMZKWkQA5444NXtLj9HP mgyN1xLCiJJ9dKAy4nLZJ87trHRnwUDb
The lack of a seed phrase is what makes recovering a coinbase multisig vault as difficult as it is. I am no python coder (not coder at all) but was able to get the code from this post on stack exchange https://bitcoin.stackexchange.com/questions/57207/how-to-derive-the-private-key-associated-with-a-coinbase-multi-sig-vault-address to produce something similar to the following: (these are just random numbers formatted to look real, they are not valid) - Master Private Key corresponding to seed: xprvz3PCl3Goz8yXxYt9mx6I9B2YXNX7ulTU0O2a6T43OfjP23A2ahmwx72iJVkmTWy0ZmBZMZcIkVv bZteiiHkucAZFdK1m1kjfMB6542qggKO
- Master Public Key corresponding to seed: xpub661MyMwAqRbcEzdGMFKZXuVwbyHY2zKhiw6YFTrULfNBF53QVfXyoAiKMZKWkQA5444NXtLj9HP mgyN1xLCiJJ9dKAy4nLZJ87trHRnwUDb
- Extended Private key at index 14: xprvz3PCl3Goz8yXxYt9mx6I9B2YXNX7ulTU0O2a6T43OfjP23A2ahmwx72iJVkmTWy0ZmBZMZcIkVv bZteiiHkucAZFdK1m1kjfMB6542qggKO
- WIF format of that key: 3OfjP23A2ahmwx72iJVkmTWy0ZmBZMZcIkVvbZteiiHkucADVDA
Not sure what exactly to do with the values produced from the user seed as that is only 1 of the signatures for a 2 of 3 vault but I will ask in Electrum. |
|
|
|
The tool is not working anymore? I can only see the error page and also the same result I got when I clicked the tool link from their official blog. The Coinbase Multisig tool on Github does not work due to an SSL handshake error with an api at bitpay.com. here is a screenshot https://imgur.com/USmIsTOIt may be possible to restore the BTC to an electrum wallet. If I figure that out, I will share the details. Here is a snippet of the email I received from Coinbase indicating the steps to access a multisig vault. How do I access my multisig vault?
- Log in to your Coinbase account at www.coinbase.com. You cannot access your multisig vault using the mobile app.
- Navigate to the “Accounts” tab from the top of the screen.
- Select your multisig vault from your list of accounts.
- Press the “Withdraw” button on your multisig vault.
- Select one of your other non-multisig Bitcoin accounts to transfer your funds to, enter in the amount to transfer, and any two factor authentication codes if needed. Then press the “Continue” button.
- On the next screen, enter your vault password into the password field, then press the “Approve” button.
- Once approved, your withdrawal will enter the 48-hour waiting period before the funds are transferred. There is no way to bypass this waiting period.
What if I don’t know my vault password?
If you don’t know your vault password, you can instead copy/paste the user seed into the password field. This will allow you to approve your withdrawal. The user seed was provided to you when you created your multisig vault.
Where do I find my vault password or user seed?
Your vault password is the phrase you chose when you created your multisig vault. The user seed is a string of numbers/letters that was provided to you during the creation of your multisig vault. You should have stored or saved both of these pieces of information when you created your vault.
What if I forgot/lost my vault password or user seed?
Unfortunately, Coinbase cannot provide or recover your vault password or user seed to your multisig vault. This has always been the case for multisig vaults. The multisig vault specifically puts you in control of your own security, and Coinbase does not have access to your vault credentials.
Because the vault cannot be accessed without these credentials, if you have forgotten/lost BOTH the vault password AND the user seed, your vault funds will be inaccessible. We apologize that there is nothing further we can do to help in that case. According to the email, a "user seed" can be used in lieu of a password to approve a transaction which makes no sense to me because that would essentially turn a 2 of 3 wallet into a 1 of 3 wallet? or is it still 2 of 3 because the user seed must sign two times? Unfortunately, all of this assumes one is using the Coinbase UI (or the multisig tool) both of which are no longer functional. Hope this helps |
|
|
|
|
