Chat archive · 2017-06

After reading vanessa’s story below I decided to try some things out... and if any of you are having problems with nicehash or with your own rig, set a c=bitconnectcoin and d=1024 and see if you get solid hashes I got almost all the power i was missing back

It is not the difficulty... its something to do with the coinswitching, i had already tried a wide range of difficulty settings leading up to that. I kept having the hang ups i mentioned below every single time it switched coins, and i suspect since a config of specifying a coin basically overrides that part of the system and the hash rate returned that it has nothing to do with the diff directly. I will say also that i ran it for a few minutes with no difficulty setting (vardiff) and it produced similar results to running without a c argument

im going to experiment with higher diffs specifying a coin... just this mod alone got me back about 18~mh

the 1024 was just a suggestion based on what vanessa’s hardware was capable of (everyone else should be able to handle it too)

i tried using the h=100 argument, and i got no results, for completness i will attempt to run it without specifying a coin and a h=1000

@GregoryGHarding :  heya, just wanted to thank you for your scrolling chat advice

you had mentioned solo mining a few days back, i finaly found some coins i can do it with succsefully with my temporary tiny hash power

Confirmed... I ran the miners for a few hours and the megahash went down as expected. The only technique which restores full hashing power on the zeus pieces is the C= some coin (ive been using bitconnectcoin) h=1000 and h=100 had no impact

early data ... i switched all my miners over to specifying a coin... I went from 600 to 640MH!!!! i am about to log out but i will post tomorrow what the figures are when i login ... anyone who was losing money try adding c=bitconnectcoin d=2048 or d=4096, it did wounders for me

Any recommendation for X11 when mining on Nicehash for the best profit? a=x11 g=off c=torcoin is good?

You will need a custom d= on NH will just disconnect you instantly and you will waste order set up charge

I’ll try a=x11 g=off c=torcoin c=cryptoclubcoin c=centurion c=dash c=reddbytecoin d=0.05 for X11 in Nicehash.

Let me know if d=0.5 lets you mine? It would not connect for me the other day without really high d

Giving Nicehash another go with c=BitConnectcoin and d=8192 - so far looks good today. By the way, any lower value for d= than 8192 would result in the order eventually cancelling.

tmopar wrote: early data ... i switched all my miners over to specifying a coin... I went from 600 to 640MH!!!! i am about to log out but i will post tomorrow what the figures are when i login ... anyone who was losing money try adding c=bitconnectcoin d=2048 or d=4096, it did wounders for me

But this means you’re probably making less money. The system already accounts for losses in hashrate by switching coins. I suspect that you are losing more than the 8% you gained in profit

Hey Steve, I posted a reply that I hope will be helpful.

I am, i am going where the data leads. I have the motivation of wanting to make the most coin. I can already tell that my numbers are looking almost preupgrade with the changes i made last night. I will post final confirmations tonight

dudes i will putting chris up to ` percent, i experimented all day

er 1 %

i started off here with 256khs, and have each week gotten myself mor power

these guys (brothers)have never steered me wrong, (look at me iloveyoucoin solo mining results)

Hats off to ya gents, and thank you Gregory for the refinment tips, solo et al

i think i will make a post in the gen section, to help me keep record and for others if they are interested in the development week by week\

Howdy ladies and gentlemen, i’m new to the whole prohashing thing haha Had a single GPU miner up using CCMiner for about an hour, I could see my miner live. After about an hour I stopped it because I dont see any payments or confirmations anywhere in my account?

Any ideas?

payouts are once a day... you should see the balances going up in the earnings though

Thx tmopar, sadly I havnt seen any yet ( I dont have a pass set and it is mining random / easiest correct? Could this be the problem? Also I have a BTC address set so dont think there is a problem there

If X11 ? you need to specify in pass

Ok gotcha i’ll try a specific one and report back haha thx m8

you can mine scrypt on gpu tooo its not recommended because of roi ... are you doin X11 or scrypt

I was trying x11 but yeah was really just interested in the random coin feature

its not random its chosen for you based on mining output of your rig and market conditions

have things settled down now?

hi very new at this and just trying to set up my account, in the help guide it says Point your miner toward prohashing.com:3333. how do i do this?

Long running system task message again with no block updates. Are we being credited "behind the scenes" for our shares?

@Steve Sokolowski :  does long running task involve manual remedy by Admin to account for lag? Or is it auto? Reason I ask I know last week or so there were couple occasions Chris had to manually adjust our balances

Live balances is updating right now but some period is not be recorded.

mickeekung wrote: Live balances is updating right now but some period is not be recorded.

yes I believe ~1 hour of missing rewards .... in two minds to disconnect if these shares are going unrewarded

No rewards for me between 1159-13:14 gmt+1 and looks like it’s still possibly not updating ? Live blocks appearing on Charts page feed and hash rates being recorded on Earnings page but no individual user block stats during this period or balance credits

@ Chris/Steve - there is a direct correlation between these "long running tasks" and a rise in rejects - please investigate.

Can anybody confirm it’s still OK to mine and we will be rewarded same value of share submitted?

how is the stability now? is it safe to mine?

I’m personally waiting until the task completes and everything catches back up.

n00bminer wrote: how is the stability now? is it safe to mine?

In my opinion, YES you’ll get the balance that not be recorded later after Chris solve this.

I switched over from litecoinpool (which is stable, less profit)

I’m disconnecting from here until after share lag resolved.

I’m disconnecting from here until after share lag resolved.

I am as well.

I can see some historical blocks that I mined during the start of the lag period appearing in my stats but I want to know if I am being rewarded at BTC value *when mined* and not BTC value after lag period when the system catches up

Uhum, will be interesting to know, please post your findings later.

I wonder the same thing, the WAMP needs a time stamp to at least be able to log it , I have gotten to the point to logging eveything I can, of course prof updates stop when there is lag and my script didn’t take that into account so I hit my self with a pretty good loss this morning so I am happy about that.

Yes, time-stamps are nice to have with any kind of event

mjgraham wrote: I wonder the same thing, the WAMP needs a time stamp to at least be able to log it , I have gotten to the point to logging eveything I can, of course prof updates stop when there is lag and my script didn’t take that into account so I hit my self with a pretty good loss this morning so I am happy about that.

Oops, sorry about that. We’ll add a timestamp to the list of tasks this weekend. I didn’t even think until now that the WAMP data was delayed when that happens.

Good move What’s up with the current task? The lag is a bit worse than usual

Steve Sokolowski wrote:

mjgraham wrote: I wonder the same thing, the WAMP needs a time stamp to at least be able to log it , I have gotten to the point to logging eveything I can, of course prof updates stop when there is lag and my script didn’t take that into account so I hit my self with a pretty good loss this morning so I am happy about that.

Oops, sorry about that. We’ll add a timestamp to the list of tasks this weekend. I didn’t even think until now that the WAMP data was delayed when that happens.

Thanks also it would be cool to be able to get the initial balance or for me sending the diff in balance is not as handy. I tired what is listed in the FAQ just get a not authorized error.

best performing coins 2017 so far below

Miner disconnected.

So it’s not just me that can’t connect right now?

mining server down?

From my side it would appear so, can’t connect for about half hour or so . .

Stable enough to connect again and profitability figures back in sync?

1 of my miners is still connected and mining, the A2 bounced and went to litecoinpool

Frisk, how did your numbers look after those settings yesterday

Steve Sokolowski wrote:

mjgraham wrote: I wonder the same thing, the WAMP needs a time stamp to at least be able to log it , I have gotten to the point to logging eveything I can, of course prof updates stop when there is lag and my script didn’t take that into account so I hit my self with a pretty good loss this morning so I am happy about that.

Oops, sorry about that. We’ll add a timestamp to the list of tasks this weekend. I didn’t even think until now that the WAMP data was delayed when that happens.

I will second this request, this appears to be affecting my profitability as well.

My balance today is also lower than expected. It seems as if my balance didn’t catch up from the delayed shares since ~13:00 CEST, even though I have been submitting shares between ~13:00 - ~15:00 CEST.

I wonder if anyone can assist a newbie? I’ve registered on here, but when I attempt to go to prohashing.com:3333 my stsem cannot find the address

@morticia001 :  You configure your miner to that not your web browser. Best google the configuration for the miner you are using. Or tell us what miner you are using

@Maznoz :  I’m doing a good chunk of money this morning but think its more down to incorrect profitability data being broadcast on WAMP for >2 hours? Steve’s post earlier says we should be auto credited for blocks mined during the lag

*down a good

@AvPro :  It could very well be the incorrect profitability data, however it has not been like that in the past when there were long(er) periods of delayed shares. Those times the balance did actually catch up. Today I have been watching the balance with half an eye and as far as I can tell it hasn’t increased during or after the period of delayed shares today (I stopped my mining around 15:00 CEST). I have no logs to confirm this though.

update, I ran yesterday 50/50 specifying a coin and running with autochoices selected, identical difficulties. It seemed as though the earnings in the first part when I ran specifying a coin were quicker but on the whole earnings were flat with the previous day. Today, I am running all on auto coin selection and i will directly compare profitability. if its greater i will stick with it, if its less, I will run a whole day specifying a coin and then update with more data when I have it.

are there any decent IOS mining monitors anymore? esp for this pool/api/wamp?

phew, I am waiting for the missing credit.

mickeekung wrote: phew, I am waiting for the missing credit.

Chris just successfully ran the query

My balances seem to have recovered a bit (still at a loss, probably due to the WAMP data being out of date). Thanks for looking into this.

@ all who use Nicehash - after endless trial and error and losses (since the upgrades) I have finally arrived at a set of PW arguments that returned a decent profit yesterday: d=8192 h=1000 g=off

@ Steve & Chris - you’ll likely want to update the Help section for Nicehash where the advice for using h= says to start with a value of 1 , then increase to 1.5 etc. - these values are so low as to be useless now. Perhaps start with a value of 100 , test and increment in steps of 100-200 to find the value that offsets Nicehash penalties best while not causing unacceptable profit loss on Prohashing side.

FRISKIE wrote: @ Steve & Chris - you’ll likely want to update the Help section for Nicehash where the advice for using h= says to start with a value of 1 , then increase to 1.5 etc. - these values are so low as to be useless now. Perhaps start with a value of 100 , test and increment in steps of 100-200 to find the value that offsets Nicehash penalties best while not causing unacceptable profit loss on Prohashing side.

Thanks FRISKIE. How about X11? Do you have trick like this?

Wrong tag I need to tag that FRISKIE wrote ’’@ all who use Nicehash - after endless trial and error and losses (since the upgrades) I have finally arrived at a set of PW arguments that returned a decent profit yesterday: d=8192 h=1000 g=off’’

Thanks FRISKIE. How about X11? Do you have trick like this?

I haven’t been able to work on X11 yet, total focus on getting profitability with Scrypt mining first. In the coming days I’ll try to run some test orders with various settings to check profitability.