InvestorsHub Logo

Zorax

01/08/18 12:28 PM

#108 RE: Circus Boy #107

You do need to ask people like stock, because pluscoin site itself gives you absolutely nothing if you don't have experience with this.
Very poorly written communications and badly rushed to the public.

But good luck.

stocktrademan

01/08/18 12:52 PM

#109 RE: Circus Boy #107


May I ask two questions?

1) I have two CPU's that run all the time, one set at 10, the other set at 1000. How can I tell if they continue to mine?
I'm gonna let each run for a month and then compare the results if there are any.
Or another way to ask the same question, how will I know if one or both stop mining?



The best way I know of is to load the PlusOneCoin wallet,

go to the help tab,
select Debug Window,
on the right side there's a little button near Debug Log File
click the Open button.

This loads up a text document called debug,
scroll to the bottom,

you should see something that looks like this at the bottom

2018-01-08 17:44:54 CreateNewBlock(): total size: 180 block weight: 720 txs: 0 fees: 0 sigops 400


this means it is mining correctly.

To see if it is continuing to run, leave the first text notepad open. Wait 10-20 seconds to let the program work,
Then go back to the PlusOneCoin app and re-click the Debug Log File Open button.

This loads up another text notepad window, but it is updated.
Scroll to the bottom of that one, and compare that it has new entries compared to the previous text window.

So the new one has more entries with new updated time stamps. If the additional entries do not have any of the CreateNewBlock kind, it is just sitting there and not mining. I look to see if there are not any of them for over a minute to say it is just sitting there or not. If you see new CreateNewBlock entries it is working fine. You can check more log files anytime you want without messing with it also from time to time, just close the text log windows when done so you don't get confused or take up too much computer memory. But leave the PlusOneApp wallet program running of course.

2018-01-08 17:44:54 keypool added key 108, size=101
2018-01-08 17:44:54 keypool reserve 8
2018-01-08 17:44:54 CreateNewBlock(): total size: 180 block weight: 720 txs: 0 fees: 0 sigops 400
2018-01-08 17:45:03 CreateNewBlock(): total size: 180 block weight: 720 txs: 0 fees: 0 sigops 400
2018-01-08 17:45:13 CreateNewBlock(): total size: 180 block weight: 720 txs: 0 fees: 0 sigops 400
2018-01-08 17:45:22 CreateNewBlock(): total size: 180 block weight: 720 txs: 0 fees: 0 sigops 400
2018-01-08 17:45:30 CreateNewBlock(): total size: 180 block weight: 720 txs: 0 fees: 0 sigops 400
2018-01-08 17:45:38 CreateNewBlock(): total size: 180 block weight: 720 txs: 0 fees: 0 sigops 400
2018-01-08 17:45:47 CreateNewBlock(): total size: 180 block weight: 720 txs: 0 fees: 0 sigops 400
2018-01-08 17:45:55 CreateNewBlock(): total size: 180 block weight: 720 txs: 0 fees: 0 sigops 400
2018-01-08 17:46:03 CreateNewBlock(): total size: 180 block weight: 720 txs: 0 fees: 0 sigops 400
2018-01-08 17:46:12 CreateNewBlock(): total size: 180 block weight: 720 txs: 0 fees: 0 sigops 400
2018-01-08 17:46:21 CreateNewBlock(): total size: 180 block weight: 720 txs: 0 fees: 0 sigops 400



That's how I tell if it is still mining even though it might not be done yet and it doesn't tell you when it will be done to give you some coins. Who knows it might be weeks or months from now. That's why I went to HappyPool because it updates nearly instantly.


2) To change one CPU from 10 to 1000, I opened the debug window selected Console and at the bottom I changed 10-1 to 1000-1. Then I closed the window. Did it then start mining 1000-1?



Yes that should have worked. There is no speedup in mining rate by using "generate 10 -1" versus "generate 1000 -1" in the debug window. Be sure you are leaving a space between the number you use and the -1 in the command. "generate 1000-1" is incorrect, "generate 1000 -1" is correct.

You can check the log files like above to see if it is mining or not regardless. If unsure you can just close the wallet and then reload it and do it over again. It doesn't remember you want it to mine when you re-load it, so you have to do the command over again each time you re-run the program.

IH Geek [Meatloaf]

01/08/18 1:57 PM

#110 RE: Circus Boy #107

In my opinion, mining with the wallet will be an exercise in frustration at this point. The way to see coins showing up is to use a pool.

You will need either a CPU miner or a GPU miner that supports hmq1725 algo.

Here's a CPU miner:
https://github.com/tpruvot/cpuminer-multi/releases

Here's a GPU miner:
https://github.com/tpruvot/ccminer/releases

Then you need to use a pool. There are two that I know of. One is:
https://happypool.co/

To use HappyPool, there's a bit of configuration, but it's not hard. First, go into your wallet and set up a receive address. Stocktrademan, I think, has instructions for that in some of his documentation.

Then, set your miner up to use that address for a payout. Here's my working command line for ccminer:

ccminer-x64 -a hmq1725 -d 0 -o stratum+tcp://stratum.happypool.co:3700 -u PTUDLgTHFUFC2pGM7VxxboSgFGRFup3bMC -p c=PLUS1,stats -b 0

BE SURE TO CHANGE THE WALLET ADDRESS TO YOUR OWN UNLESS YOU"RE WANTING TO DONATE YOUR MINING TO ME! Donations cheerfully accepted, but seriously, change the address to the one you created above. The wallet address is the long string of gibberish starting with P and ending with C following the -u switch.

The command line will also work for the cpu miner. It would look like this:
cpuminer -a hmq1725 -t 2 -o stratum+tcp://stratum.happypool.co:3700 -u PTUDLgTHFUFC2pGM7VxxboSgFGRFup3bMC -p c=PLUS1,stats -b 0
The extra -t parameter limits the number of CPU cores to use. In this case, I have it restricted to two. Fiddle with that to see what works for you. Or leave it out and it will default to using all the cores.

There's another pool that I'm aware of but haven't used here:
https://pool.coin-miners.info/