5 SBD Bounty: How to use ( and set up ) cli_wallet to change my passwordssteemCreated with Sketch.

in steemhelp •  8 years ago 

Some months ago, I mined @balkanbot.

Without the cli_wallet I can not change the passwords, because ( from what I understand ) the active- and owner key are the same ( because it's a mined account ) - I simply can't lock into Steemit now.

I would like to use the account.

I can't find any documentation for normal people on how to use the cli_wallet.

First person to link me to a comprehensive guide or to guide me through the process ( I have successfully compiled steemd before ) will get the 5 SBD.

Contact me here or in Steemit.chat.

Thanks

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

I would gladly help you on this. I went through this not long time ago.
Use update_account

Parameters:
    accountname: The name of the account (type: string)
    json_meta: New JSON Metadata to be associated with the account (type:
        string)
    owner: New public owner key for the account (type: public_key_type)
    active: New public active key for the account (type: public_key_type)
    posting: New public posting key for the account (type: public_key_type)
    memo: New public memo key for the account (type: public_key_type)
    broadcast: true if you wish to broadcast the transaction (type: bool)

so your command would look like this:
update_account balkanbot "" key1 key2 key3 key4 true

key1, key2, key3, key4 should be public keys for your key pairs.
key1 might be your current public key so you won't change key for owner
To generate new key pairs using cli_wallet use suggest_brain_key command.
For each key pair that would be generated by that command:
wif_priv_key is what you should save in safe place (private key)
pub_key is what you should use for key1 (then next for key2, and so on)

I hope that this makes sense :)

  ·  8 years ago (edited)

Thanks.

That step seems comprehensible enough.

I don't have a cli_wallet. Do I have to compile steemd and resync and all that ?

Update: I have the cli_wallet now.

Hi @felixxx, you can use my (or any other public) node for that, like this:
./cli_wallet -swss://gtg.steem.house:8090

Thanks.

Found that here: https://www.steem.center/index.php?title=How_to_obtain_the_STEEM_client#Running_CLI_Wallet_without_a_Steem_Daemon

I'm actually still stuck compiling the cli_wallet (at 69%).
Going through other posts; I think that I ran out of memory during the process ...

Do I need 8GB RAM even if I only want to use the cli_wallet ?
As stated here:
https://github.com/steemit/steem

It still explains how to mine, also.

I should have done that PW changing while my Steemd was still intact, now I have to go through the whole hassle again.

Simplest way is to use docker.
If you already have it on your system, then simple:
docker run -ti steemit/steem /usr/local/steemd-default/bin/cli_wallet -swss://gtg.steem.house:8090
would do the thing.

Thanks.

I tried using docker like described here:
https://github.com/steemit/steem/blob/master/doc/building.md

It ended up compiling the same as when I did it by hand ( and failing ) :(

Your suggestion worked:

Thanks

My pleasure. Thanks to you and @decentral we have now some decent ;-) tutorial here. :-)

Also, here: https://gtg.steem.house/get/steem/debian_jessie/ you can get xz-compressed binaries suitable for Debian Jessie, but should work well on Ubuntu too.
So:
https://gtg.steem.house/get/steem/debian_jessie/cli_wallet-v0.18.2.xz
xz -d cli_wallet-v0.18.2.xz
chmod 755 cli_wallet-v0.18.2
./cli_wallet -swss://gtg.steem.house:8090

Works on my Ubuntu. Thanks for the tip. That seems to be the fastest way to get cli_wallet running.

As long as it is compatible with your system (In your case apparently it is).
Using docker has some advantages:

  • it is official way to get official binaries
  • it works for all modern systems (as long as they support docker)
  • no need to put additional trust in me (my binaries could have been maliciously altered if I'm evil), we already trust developers (to some extent ;-) )

my binaries could have been maliciously altered if I'm evil

you don't look like ... wait, what? ;)

Loading...