BitShares Forum
Other => Graveyard => DevShares => Topic started by: davidpbrown on January 29, 2015, 05:57:14 pm
-
Client gives error at start: No WIF Error starting rpc server
I see the rpc detail in config.json has
"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.
-
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.
-
We should make it disable encrypted RPC if no key is provided.
Done: https://github.com/BitShares/bitshares/commit/4c9a24d8b261860675a3732a48722cefb9509e27
-
good to know we actually "have" an encrypted RPC interface ... where can I read how to connect and use it?
-
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.
-
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