Quote from: PawGo on Today at 10:38:02 AM

Anyway: when I launch

Code:

blockstack import_wallet wallet.json

it asks me for

Code:

Payment private key ('payment_privkey'):
Name owner private key ('owner_privkey'):
optional: Data-signing private key ('data_privkey'):

Is it correct?

No, my bad. I actually ran blockstack import , not blockstack import_wallet. I just checked my command history and import_wallet does something different from importing the wallet.

I also had a local bitcoin core running on the same machine that I installed blockstack on. It seems that blockstack requires bitcoin core so it can do the actual importing and payment handling, and blockstack's just a strawman without it.

@PawGo did you have to do any hack or workaround to make blockstack run or did it work out of the box?

I am wondering why Interactive is set to False in this configure() function. It's supposed to be True by default, and it was in interactive mode for me.

If we can find a way to make blockstack run in interactive mode, it will ask for the parameters and it'll solve the obstacle he's facing because this is the section that's failing:

Code:

   blockchain_writer_opts['utxo_provider'] = blockchain_writer_defaults['utxo_provider']
   if not interactive and (len(missing_bitcoin_opts) > 0 or len(missing_writer_opts) > 0 or len(missing_reader_opts) > 0 or len(missing_blockstack_opts) > 0):

   # cannot continue
   raise Exception("Missing configuration fields: %s" % (",".join( missing_bitcoin_opts + missing_writer_opts + missing_reader_opts + missing_blockstack_opts )) )

As you can see it's only triggered if interactive mode is off. I remember during the first time I ran blockstack that the next step after this is that it prompts you if you want to subscribe an email to some mailing list.

OP, you have to open /home/parallels/.local/bin/blockstack in a text editor and edit line 91 and change it from:

Code:

res = configure(interactive=False, force=False)

To:

Code:

res = configure(interactive=True, force=False)

Then try running the commands again (make a backup copy of wallet.json before running anything! It seems to overwrite the wallet file!)