Chat archive · 2017-04
mickeekung · Mon Apr 17, 2017 09:58 AM UTC
Many xnonce supported RIG on MRR seems not working for me.
crazyq3 · Mon Apr 17, 2017 10:04 AM UTC
i am coonect my baikal . Hash rate calculated...
crazyq3 · Mon Apr 17, 2017 10:04 AM UTC
Need Extranonce or not need for this pool?
crazyq3 · Mon Apr 17, 2017 10:10 AM UTC
If connect from rigrentals. not work. Work only if connect from miner
crazyq3 · Mon Apr 17, 2017 10:12 AM UTC
need work this. for switch from rentals
crazyq3 · Mon Apr 17, 2017 10:14 AM UTC
why calculating Hashrating... ? not see his
avgswsiss · Mon Apr 17, 2017 10:15 AM UTC
it stays for hours and still stays- looks like it isnt working.
crazyq3 · Mon Apr 17, 2017 10:16 AM UTC
i add 1800 Mh/s . Pool have speed 720 now only
avgswsiss · Mon Apr 17, 2017 10:16 AM UTC
it looks for me this is not real-time as well. some minutes behind.
crazyq3 · Mon Apr 17, 2017 10:17 AM UTC
ok i will stay my baikals 2-3 hours . iw will work will conect other
crazyq3 · Mon Apr 17, 2017 10:21 AM UTC
i most add coin for payout? my balance BTC not change
crazyq3 · Mon Apr 17, 2017 10:38 AM UTC
30 min stay 1.8 Gh/s x11 and balance not change. it normal?
avgswsiss · Mon Apr 17, 2017 10:38 AM UTC
no, it is not
x11 seems not to work at all. i have switched away until Chris looks into it
mickeekung · Mon Apr 17, 2017 10:39 AM UTC
Dear renter, Please raise your difficulty setting at the pool. It is now 0.06 which is too low for this rig to perform efficiently. Raise it to above 1 please.
<<<<<<<<<How can I raise the difficulty of Prohashing?
mickeekung · Mon Apr 17, 2017 10:50 AM UTC
Thanks seems like the pool doesn’t respond the diff rate at that time.
avgswsiss · Mon Apr 17, 2017 10:51 AM UTC
yep. looks hashrate reporting is even freezes now. But Chris has made this clear.
crazyq3 · Mon Apr 17, 2017 10:55 AM UTC
write plz when will all work . i will back my miners
rootdude · Mon Apr 17, 2017 10:55 AM UTC
I use d=0.08 for 150MH Baikal
crazyq3 · Mon Apr 17, 2017 10:56 AM UTC
baikals work all ok. but balance not change
rootdude · Mon Apr 17, 2017 10:57 AM UTC
d=0.6 for 600MH and d=1 for 900MH
crazyq3 · Mon Apr 17, 2017 11:03 AM UTC
i stay d=1 . work but balance not change
piet · Mon Apr 17, 2017 11:09 AM UTC
got it working with scrypt, need a=scrypt d=diff and voila (without a= you cant set diff anymore)
FRISKIE · Mon Apr 17, 2017 12:01 PM UTC
Seems about the worst issue now is the earning trackers and other stats in the console, keep disappearing for a while, for me at least
crazyq3 · Mon Apr 17, 2017 12:03 PM UTC
i not see balance speed and money not add
olkah · Mon Apr 17, 2017 12:04 PM UTC
prohashing.com:3333 does not work
crazyq3 · Mon Apr 17, 2017 12:05 PM UTC
need wait when all will work.
FRISKIE · Mon Apr 17, 2017 12:05 PM UTC
Assume the backend is working fine just displays hung, hope so at least!
crazyq3 · Mon Apr 17, 2017 12:06 PM UTC
)) i will beter back my miners on pool when will all work
Steve Sokolowski · Mon Apr 17, 2017 12:06 PM UTC
we’re not aware of anything causing lost money, but I’m going to be at this all day today fixing some of the display issues and that NiceHash connectivity problem
FRISKIE · Mon Apr 17, 2017 12:07 PM UTC
Doing great Steve, anyone expecting major upgrades to go any better than this probably never performed one before
mickeekung · Mon Apr 17, 2017 12:08 PM UTC
Miningrigrentals have the problem same as Nicehash too?
crazyq3 · Mon Apr 17, 2017 12:09 PM UTC
Miningrigrentals work all ok with nicehash
crazyq3 · Mon Apr 17, 2017 12:09 PM UTC
not work with prohashing now
FRISKIE · Mon Apr 17, 2017 12:09 PM UTC
What problem do you have with Nicehash now? The problem with static diff was sorted out by using the a=scrypt command to explicitly set
avgswsiss · Mon Apr 17, 2017 12:10 PM UTC
Steve- nice to see you. Rejection issue is more important i think. I get almost 90% from time to time rejected. Scrypt.
avgswsiss · Mon Apr 17, 2017 12:11 PM UTC
Steve- I have now lowered to d=rate to one of the miners to see what is does over next 30 min.
FRISKIE · Mon Apr 17, 2017 12:11 PM UTC
+1 that mate, periods of high reject here too, comes in waves though
avgswsiss · Mon Apr 17, 2017 12:12 PM UTC
correct, in waves- it wasn’t before.
Steve Sokolowski · Mon Apr 17, 2017 12:13 PM UTC
what are the errors that are being returned as a reason for the rejections?
mickeekung · Mon Apr 17, 2017 12:14 PM UTC
Both primary and merge mined shares are stale
olkah · Mon Apr 17, 2017 12:24 PM UTC
Steve today was not payments why ???
avgswsiss · Mon Apr 17, 2017 12:25 PM UTC
Steve- Add Duplicate as well, but mailny like Friskie and Mickeekung said for me as well.
piet · Mon Apr 17, 2017 12:26 PM UTC
besides the stale (both mined) im seeing a lot "New block detected on network before pool notification" Will increase speed to see what happens
rootdude · Mon Apr 17, 2017 12:29 PM UTC
Same as being reported... lots of stales with merge mining. Other than that looks pretty good except displays. Nice work Steve/Chris!
Forum notification · Mon Apr 17, 2017 12:46 PM UTC
avgswsiss · Mon Apr 17, 2017 12:47 PM UTC
soundposition- This has already been confirmed from Chris-
viewtopic.php?f=7&t=1393 Steve Sokolowski · Mon Apr 17, 2017 01:00 PM UTC
I think the merge mining issue is resolved
piet · Mon Apr 17, 2017 01:00 PM UTC
default is 4096, i think, please correct me if i`m wrong! as long as you set a=scrypt or a=x11 is working, in my case
Steve Sokolowski · Mon Apr 17, 2017 01:00 PM UTC
but I don’t want to restart until I’m sure that I’ve fixed some of the other problems
Steve Sokolowski · Mon Apr 17, 2017 01:01 PM UTC
there may be no choice with NiceHash and that "a=" non-default, because they will disconnect if the wrong diff is sent initially
FRISKIE · Mon Apr 17, 2017 01:21 PM UTC
Yes, the behavior with Nicehash is that you must use "a=" to explicitly set scrypt, if you do this it will also recognize the "d=" value
FRISKIE · Mon Apr 17, 2017 01:22 PM UTC
If you allow it to default to scrypt by not using the "a=" argument the diff will also default to var dif , regardless what value you use for "d="
dronKZ · Mon Apr 17, 2017 01:25 PM UTC
When using d = 2048, the miner starts with 4096, solve the problem with the diff
FRISKIE · Mon Apr 17, 2017 01:26 PM UTC
I am using password argus a=scrypt d=8192 for Nicehash and able to keep a stable connection
piet · Mon Apr 17, 2017 01:26 PM UTC
put a= in front of it....
dronKZ wrote: When using d = 2048, the miner starts with 4096, solve the problem with the diff dronKZ · Mon Apr 17, 2017 01:27 PM UTC
у меня гридседы не могут 4096 взять
mickeekung · Mon Apr 17, 2017 01:29 PM UTC
He said ’’I can not use the 4096’’ from google translate
dronKZ · Mon Apr 17, 2017 01:30 PM UTC
No display of earnings, speed
FRISKIE · Mon Apr 17, 2017 01:33 PM UTC
@ dronKZ, Steve said they’ve made some changes and will restart the server soon, lets see how things look after that.
jinxorbit · Mon Apr 17, 2017 01:34 PM UTC
My miners are showing a 12-15% pool rejected rate. Scrypt A4’s.
FRISKIE · Mon Apr 17, 2017 01:35 PM UTC
Confirm that and seeing a rough wave of rejects also
Chris Sokolowski · Mon Apr 17, 2017 01:50 PM UTC
trying a new release, should fix a lot of issues
avgswsiss · Mon Apr 17, 2017 01:51 PM UTC
reconnected- let’s see Chris.
avgswsiss · Mon Apr 17, 2017 01:54 PM UTC
Chris- X11 looks bad with rejection. Any suggested static difficulty to set?
piet · Mon Apr 17, 2017 01:55 PM UTC
some website stats are up
mickeekung · Mon Apr 17, 2017 01:57 PM UTC
Some of Hashrate calculation becomes live and bitcoin earning display more frequency. Thanks
Chris Sokolowski · Mon Apr 17, 2017 01:58 PM UTC
avgswsiss wrote: Chris- X11 looks bad with rejection. Any suggested static difficulty to set? I think this may be an issue with us not estimating a realistic hashrate when the server starts, therefore assigning you to coins that are too easy. What is the average hashrate of a single X11 ASIC these days?
avgswsiss · Mon Apr 17, 2017 01:59 PM UTC
Chris- average hashrate per unit should be around 500, if you take smallest 150 MH miner and largest 900 MH miner. But here, i dont take into consideration lot of people mining with GPU, CPU etc., which i dont do.
jinxorbit · Mon Apr 17, 2017 02:00 PM UTC
Since reconnect less than 1% reject.
Steve Sokolowski · Mon Apr 17, 2017 02:00 PM UTC
and the hashrates will now calculate
Steve Sokolowski · Mon Apr 17, 2017 02:01 PM UTC
I’d like an update on rejected shares if possible, because that will be the next thing I look at
jinxorbit · Mon Apr 17, 2017 02:01 PM UTC
jinxorbit wrote: Since reconnect less than 1% reject. Scrypt....
avgswsiss · Mon Apr 17, 2017 02:01 PM UTC
Chris- i currently have 50 GH/s capacity, all ASIC miners, splited on 4 different stratums with 20 GH, 16 GH and smaller.
Steve Sokolowski · Mon Apr 17, 2017 02:01 PM UTC
that’s great jinx, keep us updated
Chris Sokolowski · Mon Apr 17, 2017 02:02 PM UTC
I’m not worried about GPUs on X11 since they are barely profitable. The current initial hashrate on X11 is 40 MH/s. I’ll change the system to estimate 500 MH/s initially for an X11 miner. People with GPUs and CPUs will have their difficulty reduced automatically after we get an actual estimate of hashrate.
avgswsiss · Mon Apr 17, 2017 02:03 PM UTC
Steve: With my 131072 static diff, ZERO rejections, while with my Dynamic diff i will have to wait few more minutes and to see. Until now, only one REJECTION- GREAT WORK!
