Registering MYID.id will cost 0.00416 BTC. Continue? (y/n): y
{
“error”: “Couldn’t broadcast transaction. You can try again.”
}
Note: MYID is not the actual name I am trying to register, just using it here as a placeholder.
I have enough bitcoins to pay, as is shown when I run ‘blockstack balance’. I have tried waiting a while and trying again but I get the same response. Here is what I see when I run whois and lookup:
Thank you for your reply, I killed the two daemon processes, and then ran the command again, but I still got the same error. Where does blockstack store its log files?
I just checked the status of the remote server and everything is normal. I also tried registering a new name from a freshly installed CLI version and that also worked:
{
"message": "The name has been queued up for registration and will take a few hours to go through. You can check on the status at any time by running 'blockstack info'.",
"success": true
}```
Looks like there is something going on at your installation. We don't have explicit debugging going to a file currently (this is only the first release and we're adding new features). Are you comfortable with editing Python code?
I have installed blockstack on my linux machine (Fedora 20 Linux 64bit) and I am getting the same error (as on my OSX machine). So I think I am doing something wrong.
The only thing config. wise that I am changing, is the value of “payment_addresses” in file wallet.json to my bitcoin address.
Oh oh, yeah that’s the issue then. That value is not meant to be changed manually. We should make that clearer in instructions. We currently do not support importing private keys into the CLI wallet (see this issue). So you need to
I think what is going on is that the CLI is trying to sign transactions from the payment address you entered in wallet.json but the wallet does not have access to the private key of that address.
I have a similar issue but I am not sure I have a registrar.rpc_daemon.
I did a pip install of blockstack but never really manually start any background daemon (nor is explained on the guide). So naturally there is no daemon. Doing the ps -A |grep registrar.rpc_daemon turned out with no return.
The daemon starts automatically and terminates automatically as well (if it’s not used for sometime). Normally, you never need to think about the daemon at all. If it’s not running and you issue a new register/update/transfer command the CLI will first start the daemon.
Can you post the output of a register command? And we’ll add more documentation about this under troubleshooting. Thanks!
Are there any pending transactions on the payment address you’re using? You can go to https://live.blockcypher.com to check if there are any 0 confirmation transactions where your payment address is used.
We’re working on more helpful error messages in the next version.
Also, please join http://chat.blockstack.org and chat in #server or DM me directly and happy to help you with debugging the issue.
I’ll check the chat out, but yeah I dont think this are pending transaction, the installation is brand new and the transfer to fund the newly created wallet had more than 6 confirmations last night (up to 80 today). As you can see it shows a balance alright.
This issue was resolved by @muneeb on #Slack. The reason was my balance was too low. I added a couple bucks and it worked. @muneeb said will be fixed in later release.