You are viewing a single comment's thread from:

RE: [UPDATED 7/6] How-To Mine Steem Power in Windows

in #steem8 years ago

Great, That was the info I was looking for. So generate an address with the bulk wallet page, uncheck compressed addresses, then use your new name and the private key?

Mine crashes and references the witnesses and witness\privatekey line. and does the same crash just faster if I put the private key in the # WIF PRIVASTE KEY line. What am I doing wrong?

Sort:  

For each account you plan on mining with (see other mining posts for why you might want to use more than one) you need a witness = "bbqbear" and miner = ["bbqbear","5yourprivkeyhere"] lines in your config.ini. You do not need the private-key = line for mining.

Hmm, I deleted the config file and started again. The private key is from Account\Permissions\owner right?
The seed nodes cause a config file error if there is more than one,
3063457ms th_a main.cpp:119 main ] Error parsing logging config from config file D:\STEEM\witness_node_data_dir\co
nfig.ini, using default config

With only 1 seed node it just gives an error on the name line every time. these are the witness and miner lines
witness = "bbqbear"
miner = ["bbqbear","bigolprivatekeyxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"]
and this is the error
initminer public key: STMxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
chain id: 0000000000000000000000000000000000000000000000000000000000000000


2411656ms th_a witness.cpp:98 plugin_initialize ] _witnesses: []
Can someone post a complete working windows config file?

"get it going with only 1 hps" according to @arhag that means you are in the queue! And as long as you are in the queue, you can't hash with the same account.

lmao! I've been shutting it down each time it says that. omg I'm an idiot. :/ Thanks for letting me know!

Welp, mine shut down after no issue for several hours and now I can't get it going again. Even with a fresh start I either get it going with only 1 hps or it exits right when it starts mining. So I'm pretty tired and going to get some sleep and get on slack tomorrow, hopefully with arhag to see if we can figure out what's causing the problems.

I've updated the config.ini info above to what most say works for them, but will go over everything tomorrow in slack and hopefully we can get a consensus on proper format, then I will post one here.

If anyone comes across some new info prior to that please post it here for everyone, thanks!

Complete minus private keys of course :)

@tuck-fheman
"get it going with only 1 hps" according to @arhag that means you are in the queue! And as long as you are in the queue, you can't hash with the same account.

Your "edit" just solved my problem - yay!