Author Topic: No WIF Error starting rpc server  (Read 4541 times)

0 Members and 1 Guest are viewing this topic.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
good to know we actually "have" an encrypted RPC interface ... where can I read how to connect and use it?

Requires using our c++ code to talk to it.   It is used by the light wallet.
Hmm too bad .. not gonna see this feature in python-bitsharesrpc anytime soon then .. gonna read the code though

Offline bytemaster

good to know we actually "have" an encrypted RPC interface ... where can I read how to connect and use it?

Requires using our c++ code to talk to it.   It is used by the light wallet.   
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
good to know we actually "have" an encrypted RPC interface ... where can I read how to connect and use it?


Offline modprobe

You can use the bts_create_key utility (in programs/utils) to generate a private key to use. We should make it disable encrypted RPC if no key is provided.

Offline davidpbrown

Client gives error at start: No WIF Error starting rpc server

I see the rpc detail in config.json has
Code: [Select]
    "encrypted_rpc_endpoint": "127.0.0.1:0",
    "encrypted_rpc_wif_key": "",

but are we supposed to be using that and if so, how? I tried to put a random detail there but error then suggests that is invalid; so, I expect there is a way to generate a real private key.
฿://1CBxm54Ah5hiYxiUtD7JGYRXykT5Z6ZuMc