Show Posts
|
Pages: [1]
|
If no one can test it with a real Coinbase PDF, would it be possible to test it with the method ABCbits provided earlier on generating 3 random xpub's? I would really appreciate any help and guidance on this. The vault belongs to my love and if there is any bitcoins in there it'll help her tremendously. Can you be specific which kind of help or guidance you need? I already mention my computer environment and command used to run Coinbase tool. I would like to know if the *Coinbase Multisig Vault recovery tool* ( https://coinbase.github.io/multisig-tool/) (which is supposedly no longer working correctly) would generate the EXACT same addresses as the "functional" forked version which is supposedly working correctly ( https://github.com/dlajarretie/multisig-tool). I want to know that for certain. Is there any way to find out if both (non-functional and functional) versions of this coinbase recovery tool will generate the exact same addresses in *Step 1* when you enter all 3 public keys? Because when I enter the 3 public keys in step 1, the addresses that are generated in the list are all empty with zero transactions. Yet, the addresses that are generated are identical in both the non-functional and functional version of the tool. Can someone who has their own PDF with their own 3 public keys test this out and let me know if the 2 tools generate identical addresses for them as well?
|
|
|
I got very sad to learn that Leo has said his farewell to the community. He was extremely helpful to me and I did not get to say a proper goodbye to him. I was meaning to send him a message for weeks but I kept postponing it. I can't believe that he is now gone and I am beating myself up for not sending the message just 1 week earlier. I hope wherever he is, he can somehow find the strength to beat his disease. I want to thank you a lot for so much effort and help you put into helping me. So thank you. And for the community who was following this thread earlier, I want to give some updates and ask for some insights. Earlier in December I finally managed to message Leo the 3 xpub keys so that he can check the addresses for me. However the addresses that he generated for are the exact same ones that the DEPRECATED Coinbase multisig recovery website generates when I enter the xpub keys myself. When I followed the instructions in this thread and used the forked version instead (with correct API) and ran it locally (as per instructions), it also generated the exact same addresses. I assumed I had done it wrongly, because when I clicked F12 on Chrome, it did show the errors I previously mentioned in this thread: I am surprised that the addresses Leo generated are the exact same ones as the DEPRECATED "Coinbase Multisig Vault recovery tool" which can be found on this link: https://coinbase.github.io/multisig-tool/Based on threads of many other users I assumed this tool is no longer working correctly and you'd need a forked version: https://github.com/dlajarretie/multisig-toolThe only difference when I used the deprecated one and the forked one is that in the latter it does not show the "Failed!" message, but both tools still generate the exact same addresess. Shouldn't they generate different addresses if it's deprecated / broken? All addresses show 0 transactions and I am hoping that somehow there's still a way to figure this out. Can someone here with more knowledge than me explain to me if this is correct? Does anyone have access to their own Coinbase PDF and can enter their xpub on the deprecated one and the forked one to see if it generates the same ones? If no one can test it with a real Coinbase PDF, would it be possible to test it with the method ABCbits provided earlier on generating 3 random xpub's? I would really appreciate any help and guidance on this. The vault belongs to my love and if there is any bitcoins in there it'll help her tremendously.
|
|
|
I did quick testing on Debian 11 and it seems to works. But i can't verify whether it works on next step since i only have 3 xpub generated from https://coinb.in/#newHDaddress. Here are the steps, 1. Check my environment. $ node --version v12.22.12 $ npm --version 7.5.2 $ python3 --version Python 3.9.2 $ python2 --version Python 2.7.18
2. Setup and run multisig-tool. $ git clone --depth 1 https://github.com/dlajarretie/multisig-tool Cloning into 'multisig-tool'... remote: Enumerating objects: 29, done. remote: Counting objects: 100% (29/29), done. remote: Compressing objects: 100% (28/28), done. remote: Total 29 (delta 0), reused 12 (delta 0), pack-reused 0 Receiving objects: 100% (29/29), 109.27 KiB | 34.00 KiB/s, done. $ cd multisig-tool/ $ npm install
added 149 packages, and audited 150 packages in 1m
9 vulnerabilities (1 moderate, 4 high, 4 critical)
To address all issues, run: npm audit fix
Run `npm audit` for details. $ npm install bip38 crypto-browserify --save
added 3 packages, and audited 153 packages in 19s
9 vulnerabilities (1 moderate, 4 high, 4 critical)
To address all issues, run: npm audit fix
Run `npm audit` for details. $ ./node_modules/.bin/browserify -r bip38 -s Bip38 > lib/multisig/bip38.js $ make compile cd lib/multisig && \ ../../node_modules/.bin/browserify -r ./vault -r ./views/addresses_view > ../../multisig.js $ make run cd lib/multisig && \ ../../node_modules/.bin/browserify -r ./vault -r ./views/addresses_view > ../../multisig.js python -m SimpleHTTPServer Serving HTTP on 0.0.0.0 port 8000 ... ...
3. Open on Firefox by typing localhost:8000, enter 3 xpub and click continue. Here's the screenshot some time after i click continue. Take note i assume it works since, 1. Firefox only show error message about favicon on it's console (F12). 2. I do not see "Failed!" message or each address turning red. In order to check if "Failed!" message is due to my setup, opposed to the xPub keys, I tried generating it through the link you provided. I went on " https://coinb.in/#newHDaddress" and clicked "generate", then clicked on the ">" arrow next to xPub address. Then I changed "1" to "3" in the "Index (End)" section. I copied address 1, 2 and 3 and entered them in the step 1 of the Coinbase multisig tool. This time when I click "continue" in step 1, it generated a different list of addresses than before when I used the xPub's on the PDF, however the "Failed!" message and text turning red still occured (so "balance" never shows). Did I generate the xPub keys correctly? If so, then the fault here lies in my setup right? Before I started troubleshooting in this thread, I used ChatGPT for tons of hours and did a lot of things (nano editor, re-cloning and weird commands etc.) that I don't understand. So I think at this point it's better if I completely start from scratch (formatting and installing Debian 11). However, this time I want to do it right and not enter any commands that are unnecessary. Could you please tell me step by step what I need to do after I install Debian 11? The lines starting with "$" are the command prompts you used right? I tried to do the same in ubuntu but this one didn't work: $ ./node_modules/.bin/browserify -r bip38 -s Bip38 > lib/multisig/bip38.js
|
|
|
Being unable to find a favicon file is irrelevant. This is simply the little logo icon that different websites use. In the absence of any other errors, something is stopping your browser from correctly fetching the balances. Your browser can visit other websites normally? You don't have any firewall or similar running? The first thing I would try would be to open a terminal in the usual multisig tool directory, and then run the following two commands: The first will delete the multisig.js file (which is responsible for this look up); the second will recompile it from scratch. This is to rule out any error in the file. If that doesn't work then I'm afraid I'm running out of ideas... -Firewall is inactive. -I am connected to a VPN however. -Tried both Firefox and Chrome. After the make clean & make compile command, I did the "python3 -m http.server" again but this time got this error: BrokenPipeError: [Errno 32] Broken pipe Also Chrome's F12 now shows 165 issues: - - Failed to load resource: net::ERR_FAILED insight.bitpay.com/a…YGno8MTeLYGM/utxo:1 (Changed the address in the error code just in case it's not safe to share publicly). The other issues are basically a repeat of the above but with all the other addresses in the list. Btw, user "HCP" also mentioned something about the "Insight API" missing in this thread: https://bitcointalk.org/index.php?topic=5316286.0If that doesn work post your permission sets of the folders/files which cause issues. Not sure if ChatGPT explained correctly on how to do this but I typed "ls -l" in the multisig-tool directory and got the following: total 572 -rw-rw-r-- 1 revived revived 2265 mrt 12 18:12 CONTRIBUTING.md drwxrwxr-x 2 revived revived 4096 mrt 12 18:12 css drwxrwxr-x 4 revived revived 4096 mrt 12 19:01 env -rw-rw-r-- 1 revived revived 4610 mrt 12 18:12 index.html drwxrwxr-x 3 revived revived 4096 mrt 12 18:12 lib -rw-rw-r-- 1 revived revived 11344 mrt 12 18:12 LICENSE -rw-rw-r-- 1 revived revived 428 mrt 12 18:12 Makefile -rw-rw-r-- 1 revived revived 421914 mrt 17 23:00 multisig.js -rw-rw-r-- 1 revived revived 181 mrt 12 18:12 multisig-tool.sublime-project drwxrwxr-x 142 revived revived 4096 mrt 13 21:17 node_modules -rw-rw-r-- 1 revived revived 704 mrt 12 18:52 package.json -rw-rw-r-- 1 revived revived 100713 mrt 13 21:20 package-lock.json -rw-rw-r-- 1 revived revived 3734 mrt 12 18:12 README.md
|
|
|
What error do you see in the console (F12) now?
:8000/favicon.ico:1 Failed to load resource: the server responded with a status of 404 (File not found) Also as soon as I go on " http://0.0.0.0:8000/", then the terminal shows these 2 messages: -code 404, message File not found -"GET /favicon.ico HTTP/1.1" 404 -
|
|
|
Is the alternative "HTTP Server method" the "Running Locally" / make run method? The make run command simply compiles the multisig.js file (which seems to be working fine for you - you can tell for sure by the presence of a file called multisig.js in your multisig-tool folder), and then attempts to launch an HTTP server. Running an HTTP server is the alternative to trying to launch chrome with --allow-file-access-from-files. Since the make run command is trying to launch an HTTP server using a Python 2 command, and you have Python 3 installed, then instead of using make run you can just launch the HTTP server directly using the command I gave above: You should run it from your multisig-tool folder, the one with "index.html" in it. Open a terminal here and enter the command. If it has worked, it should say something like: Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) Then you just open any web browser, and navigate to that address - http://0.0.0.0:8000. The tool will load and hopefully(!) be fully functional. Indeed, the multisig.js file is in the multisig-tool folder. However if I'm not mistaken it was already there (the icon however is changed from a notepad thingy to "JS" in big yellow letters). Also entering "python3 -m http.server" in the same repository terminal did indeed show "Serving HTTP on 0.0.0.0 port 8000 ( http://0.0.0.0:8000/)". And typing " http://0.0.0.0:8000" in the browser did automatically show the Coinbase Multisig Vault recovery tool similar to the web version. However, after entering the 3 xpub keys, I still got the exact same list of addresses, followed by a "Failed!" message and each address turning red, as I did before (using the web version)
|
|
|
index.html:1 Access to fetch at 'file:///home/revived/multisig-tool/lib/multisig/bip38.js' from origin 'null' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes This means your --allow-file-access-from-files isn't working as intended. I've never used Chrome so can't advise otherwise here. I use the alternative HTTP Server method instead, which works just fine. Did you make any headway on that? The command given above is for Python 2: python -m SimpleHTTPServer If you are using Python 3, try the following command: Is the alternative "HTTP Server method" the "Running Locally" / make run method? I installed the BitcoinJS library. And if I'm not mistaken, I performed BIP38's step 1 & 2 correctly: We use the BIP38 library to decrypt the encrypted shared key seeds.
To build the multisig/bip38.js we used:
1. Install packages with npm: "npm install bip38 crypto-browserify --save"
2. Use browserify to resolve dependencies: "browserify -r bip38 -s Bip38 > lib/multisig/bip38.js"
However, I haven't been able to figure out what I've to do in this following step: Then we amend the "lib/multisig/bip38.js" to support progress callbacks and Web Worker messages handling.
We need this as a separate file, because we're using it with web workers. I also can't make out what you mean by the "python3 -m http.server" command, I have Python 3.10.6 but what do I have to do after I enter that command (and should it be in the multisig-tool respository? I'm sorry, I'm a complete beginner and don't know what I'm doing so I need to know every step no matter how basic it is.
|
|
|
What is the next step? Am I supposed to open the index.html file? Because using Chrome to simply use the web version is not an option as the API is broken (I tried it again, which resulted into "Failed!" addresses.) Yes, open your local copy of index.html. Once you open it, hit F12 on your keyboard and click on the Console tab. Does it show you any errors? Ah good to see your reply Leo! It only says the following: index.html:1 Access to fetch at 'file:///home/revived/multisig-tool/lib/multisig/bip38.js' from origin 'null' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, isolated-app, chrome-extension, chrome, https, chrome-untrusted. lib/multisig/bip38.js:1 Failed to load resource: net::ERR_FAILED multisig.js:136 Uncaught (in promise) TypeError: Failed to fetch at require.2 (multisig.js:136:1) at o (multisig.js:1:273) at multisig.js:1:324 at require./vault../address (multisig.js:15193:19) at o (multisig.js:1:273) at HTMLDocument.<anonymous> (tool.js:14:15) at j (jquery-2.1.3.min.js:2:26911) at Object.fireWith [as resolveWith] (jquery-2.1.3.min.js:2:27724) at Function.ready (jquery-2.1.3.min.js:2:29518) at HTMLDocument.I (jquery-2.1.3.min.js:2:29709)
|
|
|
That is I think it suggests running Chrome with this parameter "--allow-access-from-files" Could you please tell me how I can set this up in Linux? Would I still need to perform the other steps? For now, adding parameter --allow-access-from-files when you launch Chrome or chromium-based browser is needed since the current problem is when you execute make run, not silent error when you use the tool on the browser. I launched Chrome with the "-allow-file-access-from-files" parameter by typing the following command: "./chrome --allow-file-access-from-files" What is the next step? Am I supposed to open the index.html file? Because using Chrome to simply use the web version is not an option as the API is broken (I tried it again, which resulted into "Failed!" addresses.)
|
|
|
All your replies are much appreciated. I will try to install either Debian 11 or one of the older Ubuntu versions. Why don't you just use the hosted one since it's ready to use? The hosted version is not working correctly anymore (since years). According to other threads it's due to an SSL handshake error with an api at bipay.com. After inserting the 3 xpub keys in step 1, it generates a list of empty addresses followed by the "failure" message next to each address. That is I think it suggests running Chrome with this parameter "--allow-access-from-files" Could you please tell me how I can set this up in Linux? Would I still need to perform the other steps?
|
|
|
After Coinbase multisig vault was discontinued in 2018, a third-party multisig-tool was introduced on Github. But that one stopped working as well. According to this thread: https://bitcointalk.org/index.php?topic=5436171.msg61722006#msg61722006 the forked version ( https://github.com/dlajarretie/multisig-tool) still works correctly but needs to be run locally. I am stuck halfway in the instructions provided on Github and would appreciate if someone could guide me through the rest. My progress so far:-I installed Linux Ubuntu on a spare computer -I installed npm and browserify -I cloned the repository from: https://github.com/dlajarretie/multisig-toolI entered the following commands in the multisig-tool repository in the terminal:-npm install bitcoinjs-lib -npm install --save bip38 -npm install bip38 crypto-browserify --save -browserify -r bip38 -s Bip38 > lib/multisig/bip38.js The latter command didn't show anything in the terminal, but I do see the "bip38.js" file in the lib/multisig folder so it could've been successful. Are there any other steps I've to perform before going further? When I enter "make run", I get the following error:cd lib/multisig && \ ../../node_modules/.bin/browserify -r ./vault -r ./views/addresses_view > ../../multisig.js python -m SimpleHTTPServer make: python: No such file or directory make: *** [Makefile:2: run] Error 127 I look forward to hearing from the community and very much appreciate the help. Also shoutout to o_e_l_e_o for being extremely helpful in the DM's.
|
|
|
|