Topic: HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive - page 280. (Read 478849 times)

yes jsut make sure you match coinwarz before you start.

here are some addnodes

84.22.139.7
159.224.220.21
118.209.0.241
162.243.69.147
91.69.177.224
206.72.202.20

What addnodes should be used for solo mining?

Guess time to make that conf file for solo mining. The diff is low enough to solo mine.

I think the blocksfactory is down.. Best to solo mine as long as you match coinwarz.

Coinex is wrong, do not mine there. .018 is correct. The checkpoints are making the rounds and will fix the issue. All other sites seems to be in good shape.

Does the stratum work on that pool? In general, none of the info is updating on there.


What is the current diff? CoinEX has 0.5087 and Coinwarz is showing .018, is there a major fork happening?

./cgminer --scryot -o stratum+tcp://hbn.theblocksfactory.com:3336 -u username.worker -p pass
Typical low reject settings (7950)
thread-conccurency 8192
intensity 13
gpu-thread 2


I <3 mining scryot

I think you are on the right chain. coinex forked off. But I will let everyone know here shorlty.

is it possible to check what chain I`m on?

23:09:51

getinfo


23:09:52

{
"version" : "v1.2.2.0-g38a5c87-hobo",
"protocolversion" : 70002,
"blocks" : 377617,
"moneysupply" : 1875555.88983100,
"connections" : 3,
"wallets" : 1,
"proxy" : "",
"ip" : "98.216.xx.xx",
"difficulty" : 0.02143168,
"testnet" : false,
"paytxfee" : 0.00000000,
"errors" : ""
}

Its ok, just may not count toward the correct blockchain. One will get wipped.   Not lot of time just a few hours. I am still sorting it out.

Can you tell me what your getinfo says?

mining solo is ok now? or better to wait?

Hey we might have a bit of a fork here, coinex.pw is the only working pool and they just crushed the block chain. So just be mindful for a bit while I sort this out.

Hey guys. I made a mistake. The checkpoint server got rebooted last night. And I was bringing it back online, and I didn't let it catch up first before starting the checkpoints. This caused an issue and we rolled back.

My deep regrets on this.

Some polls and miners lost some coins.  I will pay back all. Just hit me up.

Also if you are getting mempool errors. you can solve this by stopping the client and restarting with -salvagewallet.

Again I am truly sorry.

Good glad to hear it! Welcome aboard.  Just for your information best practices for mining are to create a secondary wallet called stake, and move coins in batches from ~default to stake when you accumulate a few hundred or so.  This will keep the wallet running nice and smooth and keep you from using coins that are going to stake.

Can I check the name of the .conf file?

I've set everything up as I would do for any other coin but CGminer starts and then doesen't kick into mining.

Edit:

Resolved think it was the port. Might be that I also saw the .conf elsewhere as hobonickel.conf both now changed and mining away.

Nice write up on cryptonerd.co

http://majesti.co/cryptonerd/did-someone-call-for-some-hobo/

Please make sure you are correct client.  at least 1.2.1.5+
I have PM'd you a few add nodes to try.

hellow！ why my HBN con't connection in China

Here is a quick tutorial on Multiple Wallets.

GUI Interface:
The GUI now includes a wallet stack on the right hand side. These will be all wallets that are currently loaded and in memory. Simply clicking on any of the wallets will change the left side of the gui to show that wallets information.

To create a new wallet click on the new button and navigate to the directory you want to create the wallet in. Then type wallet-walletname.dat. For example wallet-stake.dat, will show up in the gui as stake. All wallets must be preceded by wallet- and end in .dat. Any other names will create an error.

To load an existing wallet click the load button, navigate to the directory you want and open that wallet. If the wallet is encrypted and you would like it to be able to run stake, then you will need to use the rpc command walletpassphrase. This can be done by click on the debug window, then going to the console tab then enter the following command usewallet walletname walletpassphrase timetounlock. The walletname is what you see in the wallet stack in the gui, or when using the listwallets rpc command. Trying to load a file not named wallet-something.dat will cause an error, as well as trying to load the same wallet that is already loaded. No harm will come, but it won't load.

To remove a wallet from memory, highlight the wallet want to remove the click the unload button. The wallet will be flushed from memory and removed from the gui. If you loaded a wallet from a USB, it is a good idea to both wait 10-30 seconds and use the safely remove media button in windows, before you remove the USB.

RPC Methods:
-listwallets
   -Shows all loaded wallet information

-usewallet [params]
   -Use wallet commands on different wallets
   -Example: usewallet HoboOfflineWallet1 sendtoaddress F4ATvAfwcE5RFn358FS1bxauwoB7Ces7KN 100

-loadwallet [rescan=false] [upgradewallet=false] [maxversion=(latest)]
   -Loads a wallet found in the %appdata% directory. If no wallet by the name is found, one is created.

-unloadwallet
   -Unloads a wallet.

Config and Command line arguments:
- You may use the config line usewallets=walletname or the command line -usewallet=walletname
- This will load only the wallets you specify. If you do not use either of these, than all wallets in the %appdata% dir named wallet-*.dat will be loaded. If you specify usewallet="" than only the default wallet will be loaded.
- You may also prevent a certain wallet from loading at start up by using the argument -nousewallet

Staking:
- At time of start up all wallets listed in usewallets or all found in %appdata% will each get a thread to start stake. This should help with CPU exhaustion.
- If you specify usewallet="" than only the default wallet will be loaded and up for stake.
- All wallets specified by -nousewallet will not be up for stake.