Existing Wallet not found by Blockstack Browser


Dear Blockstackers,

yesterday I loaded my Blockstack wallet with 0.007 BTC and successfully registered stulle.id at a price of 0.004 BTC using the Blockstack Browser UI, resulting in [https://explorer.blockstack.org/name/stulle.id]. This morning the Blockstack Browser showed a remaining balance of 0.00411018 BTC.

To keep up with the latest Blockstack developments, I then pulled new versions of the Docker images from Quay, v0.17.0.6 for Blockstack Core and v0.17.1 for Blockstack Browser, and ran the required containers:

E:\> docker ps | findstr -i blockstack
5f77a7b976a7  quay.io/blockstack/blockstack-browser:v0.17.1 "blockstack-cors-p..."  6 hours ago Up 6 hours>1337/tcp   blockstack-browser-cors
5742a8bcfa11  quay.io/blockstack/blockstack-browser:v0.17.1 "blockstack-browser"    6 hours ago Up 6 hours>8888/tcp   blockstack-browser-static
6bae75d01a1d  quay.io/blockstack/blockstack-core:v0.17.0.6  "blockstack api st..."  6 hours ago Up 6 hours>6270/tcp   blockstack-api

The Blockstack Browser now shows a zero balance and a new Bitcoin address:

It seems to me that the updated Client just ignores the existing file ~\.blockstack\wallet.json, although the core recognizes the wallet as expected:

E:\> docker exec -it blockstack-api /bin/bash

root@6bae75d01a1d:/src/blockstack# mount -t cifs
// on /tmp type cifs (rw,relatime,vers=3.02,sec=ntlmssp,cache=strict,username=markus,domain=SANTACLARA,uid=0,...)
// on /root/.blockstack type cifs (rw,relatime,vers=3.02,sec=ntlmssp,cache=strict,username=markus,domain=SANTACLARA,uid=0,...)

root@6bae75d01a1d:/src/blockstack# ls -laFgi /root/.blockstack
total 33
   844424930421035 drwxr-xr-x 2 root 4096 Oct 12 06:47 ./
            112299 drwx------ 1 root 4096 Oct 12 04:56 ../
  1407374883847931 -rwxr-xr-x 1 root    1 Oct 12 04:56 api_endpoint.pid*
 52917295621828455 -rwxr-xr-x 1 root 1106 Oct 12 04:56 client.ini*
104427216359947334 -rwxr-xr-x 1 root 1106 Oct 12 04:56 client.ini.legacy.1507784214*
  2814749767107945 -rwxr-xr-x 1 root   36 Oct  8 13:14 client.uuid*
  1688849860557948 drwxr-xr-x 2 root    0 Oct  8 13:45 drivers/
  1407374883847291 -rwxr-xr-x 1 root 7168 Oct 11 08:13 queues.db*
  2251799813979900 -rwxr-xr-x 1 root    0 Oct 12 04:56 registrar.lock*
  5629499534303981 drwxr-xr-x 2 root    0 Oct  8 13:14 storage-disk/
  1125899907136639 -rwxr-xr-x 1 root 4096 Oct 12 06:47 subdomains.db*
  5066549580883091 -rwxr-xr-x 1 root 2021 Oct  8 13:14 wallet.json*
root@6bae75d01a1d:/src/blockstack# which blockstack

root@6bae75d01a1d:/src/blockstack# blockstack --api_password 12345... wallet
Payment address:        3EQTxEdHSKi2xAZujAimbfi2uTrcMvDVuj
Owner address:          3FHncKWCmqVDCwTCDLuW2tQcNVyC3kxSzm
Data public key:        0425c6787d3689c0c2dde115a9ae4f574d36c965c277e4184d8c8903b8dc2f95aff2c276ebf4a459b8b7eef77d19814a4dbb8892bc3f1ea5faa3b0794526e7bf9f
3EQTxEdHSKi2xAZujAimbfi2uTrcMvDVuj: 0.00411018
Names Owned:
3FHncKWCmqVDCwTCDLuW2tQcNVyC3kxSzm: []

How can I make the existing wallet known to the browser?

Thank you in advance!



For the sake of completeness: I retried with Blockstack Core version v0.17.1-browser from Quay:

E:\>docker ps | findstr -i blockstack
e35d50f65369  quay.io/blockstack/blockstack-browser:v0.17.1        "blockstack-cors-p..."   35 minutes ago      Up 35 minutes>1337/tcp   blockstack-browser-cors
a7ef239d72a4  quay.io/blockstack/blockstack-browser:v0.17.1        "blockstack-browser"     35 minutes ago      Up 35 minutes>8888/tcp   blockstack-browser-static
89595548c2d0  quay.io/blockstack/blockstack-core:v0.17.1-browser   "blockstack api st..."   35 minutes ago      Up 35 minutes>6270/tcp   blockstack-api

Unfortunately the error pattern remains unchanged, the Blockstack Browser still does not find the existing wallet.

"Name registration in progress"

Hi, sorry about the confusion –

We changed the wallet address location in the 0.17 release – we moved the bitcoin wallet from stored in a local file (that wallet.json you found) to being completely derived from the 12-word secret phrase.

Funds stored in the old wallet should be obtainable, however, by opening the browser to http://localhost:8888/wallet/send-core – you’ll get an interface to send funds out of the old address.


Dear Aaron, that worked perfectly - I got my money back :wink:

Thank you a lot!


@aaron I cannot get this to work. Going to /send-core gives me:

53 PM

And restoring an existing keychain is not possible because legacy wallets don’t have a keychain phrase:

Sign in with legacy wallet/no keychain phrase?