Hey @Rimann, replies inline
I understand that it’s not the 12-word phrase. What I don’t understand is what the blockstack-core password is? I followed the instructions in your walkthrough as closley as I could. But I was still never given or asked to establish a 'blockstack-core password." Your instructions say to move the ~/.blockstack directory out of the way and that a new one will be created but it doesn’t say how the new one is created. I tried running blockstack setup again for the third time but nowhere during the setup process does anything refer to a “blockstack-core password.” There is a default API password, a default bitcoind password, and at the end it asks me to set up a wallet password. What part of the setup process am I missing?
I think I see the point of confusion. I’m assuming that since you know about
blockstack setup, you have installed the CLI at some point in the past and are familiar with the CLI’s wallet password prompt? The password that the Linux script calls the “Blockstack Core password” is used for the same purpose as the wallet password in the Blockstack CLI.
The Blockstack Browser has its own wallet, which is seeded from the 12-word phrase. It relies on a CLI instance running in Docker to carry out name registrations, for which it needs to know the Dockerized CLI’s wallet password.
There’s a more detailed technical discussion as to where the various pieces of the system run here, if you’re interested.
I also read through your post on utter utter garbage yet am still oblivious to where the block-stack core password comes from. Or whether or not its equivalent to the API password or wallet password in the setup process (you have made it very clear that it is NOT the 12 word phrase).
The API password is used to authenticate RESTful calls between the Browser process and the Dockerized CLI (which is running
blockstack api start). You can see it in your
~/.blockstack/client.ini file. It is distinct from the 12-word phrase and the “Blockstack Core password.”
If the core password IS the API or wallet password created in this process, I would like to know because that means my problem is related to one of the error messages after entering the password and not a wrong password itself. Here is the output on entering a password after running start and recieving a prompt for my “blockstack core” password.
This might be part of the problem. The Linux script assumes that the user has not installed the CLI, and that it has free reign over the contents of
~/.blockstack. If you run
blockstack setup outside of the Linux script, it may cause it to break. The password that would be used here as the “Blockstack Core password” is the same password you entered for the “wallet password” in
docker: Error response from daemon: Conflict. The container name "/blockstack-api" is already in use by container "b28869519d91bde72bccbbd7ffa69ee0bc30eb6f457096d100347b04637f0929". You have to remove (or rename) that container to be able to reuse that name.
Actually, this error looks different. Do you have any containers running when you try to start the script? You may need to run
docker ps to see them, and run
docker kill to stop them if
./Blockstack-for-Linux.sh stop does not do the trick.
Again thanks for your patience and willingness to help
No, thank you for being so patient with us