Chat archive · 2017-09
Maxiimos · Fri Sep 29, 2017 01:04 PM UTC · #34822
I’m at $3.47 on one L3+ as of today
mickeekung · Fri Sep 29, 2017 01:11 PM UTC · #34824
Feel free to PM to Steve. He just appeared a few minutes ago.
Maxiimos · Fri Sep 29, 2017 01:12 PM UTC · #34825
Is everyone else experiencing the same thing on scrypt today?
Alex · Fri Sep 29, 2017 01:14 PM UTC · #34826
Maxiimos wrote: I wonder if this is related to the "n=" change they implimented into the code, I had an error yesterday where a phantom miner was connected to my account for a second causing my miner to assign a random name because it had another miner named "miner1" on my account I had four doing this, this morning
Maxiimos · Fri Sep 29, 2017 01:19 PM UTC · #34827
Alex, I think the problem could be related to this, I’m not sure shares are being assigned correctly due to this "duplicate name" error
Maxiimos · Fri Sep 29, 2017 01:19 PM UTC · #34828
I have no idea how a second miner can show up on my account but that’s definitely a sign of an issue
Alex · Fri Sep 29, 2017 01:21 PM UTC · #34829
I think you are right, but it worked fine yesterday up until the end of the 24hr period. I’m stuck at work so I can’t even change the n= argument to see if this improves things for another 6hrs
Maxiimos · Fri Sep 29, 2017 01:23 PM UTC · #34830
that’s about when my profitability started looking incorrect yesterday, around noon when that error showed up
Maxiimos · Fri Sep 29, 2017 01:23 PM UTC · #34831
I changed my n= argument but nothing changed, I think there could be "phantom miners" taking shares without actually contributing work due to this error or something
Maxiimos · Fri Sep 29, 2017 01:24 PM UTC · #34832
my previous miner name was a generic "miner1" so I changed it to something more unique but the profitability stayed low
hashingpro · Fri Sep 29, 2017 01:24 PM UTC · #34833
on target to make 8.70 bucks today....Oh Scrypt why does thou do this to me.
Maxiimos · Fri Sep 29, 2017 01:25 PM UTC · #34834
I do believe this is an error, even mining LTC should yield higher than that
hashingpro · Fri Sep 29, 2017 01:25 PM UTC · #34835
yeah and mining DASH should be more profitable than auto X11 on here...but it isnt
hashingpro · Fri Sep 29, 2017 01:26 PM UTC · #34836
last 3 days, you could make more on DASH than auto pooling here for x11
hashingpro · Fri Sep 29, 2017 01:26 PM UTC · #34837
so how broke is the auto coin picker?
hashingpro · Fri Sep 29, 2017 01:26 PM UTC · #34838
it cant pick dash 50% more so the profits are at least in line with straight dash mining?
Alex · Fri Sep 29, 2017 01:26 PM UTC · #34839
Dating a girl with a drug addiction and flexible ethics doesn’t seem as bad as it was all those years ago lol
Maxiimos · Fri Sep 29, 2017 01:26 PM UTC · #34840
look at this, check the front page on the profitability graph for scrypt, what does the BTC show for you?
hashingpro · Fri Sep 29, 2017 01:28 PM UTC · #34841
not following max, which chart?
Alex · Fri Sep 29, 2017 01:29 PM UTC · #34842
only x11 blocks are being found
Maxiimos · Fri Sep 29, 2017 01:29 PM UTC · #34844
sorry, I meant the 1MH/s chart, but I realized it hasn’t been updated since Wed
remondis · Fri Sep 29, 2017 01:30 PM UTC · #34847
Take a look on your "Live Balances". Maybe they have fix the problem by now.
hashingpro · Fri Sep 29, 2017 01:30 PM UTC · #34848
thats what WAS paid not what WILL be paid
mickeekung · Fri Sep 29, 2017 01:30 PM UTC · #34849
I just found happy coin but it doesn’t make me happy.
hashingpro · Fri Sep 29, 2017 01:30 PM UTC · #34850
they havent im still on target for 8$ per miner on L3+
hashingpro · Fri Sep 29, 2017 01:30 PM UTC · #34852
and tell me the coin picker works for that x11 one
Maxiimos · Fri Sep 29, 2017 01:31 PM UTC · #34853
the live profitability shows 7.44 cents and we’re on pace for 1.8 cents
hashingpro · Fri Sep 29, 2017 01:31 PM UTC · #34854
i only look at the live stats to see how much is on the network
remondis · Fri Sep 29, 2017 01:32 PM UTC · #34856
Take a look on your "Live Balances". Maybe they have fix the problem by now.
mickeekung · Fri Sep 29, 2017 01:32 PM UTC · #34857
Now Scrypt is raise up. YEY!!
hashingpro · Fri Sep 29, 2017 01:32 PM UTC · #34858
looking at what scrypt is now, vs what we will get paid and average at the end of the day, 2 diff things
hashingpro · Fri Sep 29, 2017 01:32 PM UTC · #34859
@remondis : No they have not.
Maxiimos · Fri Sep 29, 2017 01:33 PM UTC · #34860
I understand hashing, but what I"m saying is even with LTC stand alone profitability being around 3 cents, we’re even under that for today
mickeekung · Fri Sep 29, 2017 01:34 PM UTC · #34861
It might depend on market price for what profit we get. Maybe Steve will said about the market price that makes our profit be lower than it should be.
hashingpro · Fri Sep 29, 2017 01:34 PM UTC · #34862
yes, and im pointing out for the past 3 days, the coin picker hasnt been able top pick over the best X11 coin higher than dash, so why would it be any better on scypt?
hashingpro · Fri Sep 29, 2017 01:35 PM UTC · #34863
No mick that effects the payment you get, not the earnings you earn.
Maxiimos · Fri Sep 29, 2017 01:35 PM UTC · #34864
you think the coinpicker is to blame HP? don’t you think some shares might be incorrectly assigned? Our other clue is the "phantom miner" and "duplicate miner name" errors we are having
vhmanu · Fri Sep 29, 2017 01:35 PM UTC · #34865
Something has to be wrong. Scrypt is going to be a good amount below Litecoinpool
hashingpro · Fri Sep 29, 2017 01:36 PM UTC · #34866
no im not blaming the coin picker, it seems like its picking the right stuff to mine, we just arent being paid correctly or counted or something
hashingpro · Fri Sep 29, 2017 01:36 PM UTC · #34867
the question is, will they be able to add 25% to everyone to make it right today
Maxiimos · Fri Sep 29, 2017 01:36 PM UTC · #34868
it’s showing we have 7000 connected workers, isn’t this number usually around 3500?
hashingpro · Fri Sep 29, 2017 01:36 PM UTC · #34869
or will they say, sorry that work was all lost, we didnt get paid so you cant get paid, sorry wasted day
hashingpro · Fri Sep 29, 2017 01:37 PM UTC · #34870
max the network isnt normally 10TH in size either, normally 3, 6
Maxiimos · Fri Sep 29, 2017 01:37 PM UTC · #34873
you can see that plotted on a graph though, that hashrate for x11 follows the trend
hashingpro · Fri Sep 29, 2017 01:37 PM UTC · #34874
im thinking we are off 50% or more right now
hashingpro · Fri Sep 29, 2017 01:38 PM UTC · #34875
so Im really hoping its a mistake and we get credit
Alex · Fri Sep 29, 2017 01:38 PM UTC · #34876
hashingpro wrote: prolly not hashingpro · Fri Sep 29, 2017 01:38 PM UTC · #34877
They would almost have to, people find out they lost 50-70% profit for 1 day they wont ever come back to here, so they will have to fix it anyways
Maxiimos · Fri Sep 29, 2017 01:38 PM UTC · #34878
I swear that’s the issue, when the code was implemented to remove the "duplicate name" error, it created a bunch of miners that don’t exist
hashingpro · Fri Sep 29, 2017 01:39 PM UTC · #34879
i log in tomorrow and find I only made 8$ and they arent going to fix it, I will never be back.
Maxiimos · Fri Sep 29, 2017 01:39 PM UTC · #34880
makes no sense that the "worker count" would double in a day without the "miner count" going up
hashingpro · Fri Sep 29, 2017 01:39 PM UTC · #34881
doubt anyone else ever will either, will kill the rep
hashingpro · Fri Sep 29, 2017 01:39 PM UTC · #34882
where do you see miner count?
Maxiimos · Fri Sep 29, 2017 01:39 PM UTC · #34883
Can anyone relay that info to Steve?
hashingpro · Fri Sep 29, 2017 01:40 PM UTC · #34884
relay to steve what? if his site is 70% lower payout ever and they dont fix it that he may not have a site the next day, Im pretty sure they know that.
Maxiimos · Fri Sep 29, 2017 01:40 PM UTC · #34885
no, I mean specifically that the error is related to the phantom workers
hashingpro · Fri Sep 29, 2017 01:41 PM UTC · #34886
sure, once you prove that it is then tell him
Maxiimos · Fri Sep 29, 2017 01:41 PM UTC · #34887
I don’t know the best way to let him know that this could be the issue
hashingpro · Fri Sep 29, 2017 01:41 PM UTC · #34888
i havent tested or looked at anything to decide that 1 way or another
hashingpro · Fri Sep 29, 2017 01:41 PM UTC · #34889
im p[retty sure he will know or find the issue, has to be one of 10 things they changed yesterday
hashingpro · Fri Sep 29, 2017 01:42 PM UTC · #34890
something they forgot to do, some bracket in the code they forgot to close, or 1 more state a miner could fall into they didnt plan on and didnt program for
Maxiimos · Fri Sep 29, 2017 01:42 PM UTC · #34891
you’re right, it’s all about how they compensate the miners for the error
hashingpro · Fri Sep 29, 2017 01:43 PM UTC · #34892
well if we all off 50% and no fix, that would answer the question for them if they need to expand or not.
hashingpro · Fri Sep 29, 2017 01:45 PM UTC · #34893
STEVE! wakey wakey hands off snakey time to fix the shares.
Maxiimos · Fri Sep 29, 2017 01:46 PM UTC · #34894
he was in chat about an hour ago but didn’t say anything
MrHollowPoints · Fri Sep 29, 2017 01:58 PM UTC · #34895
So....prohashing is having issues....again?
mycide · Fri Sep 29, 2017 01:59 PM UTC · #34896
had a power outtage this morning as as i sleep til noon i had rigs off for 6 hours, the ground relay had to be reset
Alex · Fri Sep 29, 2017 02:00 PM UTC · #34897
On the live blocks found, would it unusual if no one found a Bitconnectcoin block?
Red and White Shield · Fri Sep 29, 2017 02:04 PM UTC · #34898
hey anyone knows what this means? it is in the L3+ UI on the area of the fans and chip temp i have this
Red and White Shield · Fri Sep 29, 2017 02:04 PM UTC · #34899
STATUS=E,When=1,506,693,782,Code=45,Msg=Access denied to ’stats’ command,Description=cgminer 4.9.0| STATUS=E,When=1,506,693,782,Code=45,Msg=Access denied to ’stats’ command,Description=cgminer 4.9.0|
Jules9 · Fri Sep 29, 2017 02:04 PM UTC · #34900
we are way off today. what happened
Alex · Fri Sep 29, 2017 02:07 PM UTC · #34902
@ Jules9 we have no idea, it might have something to with n=argument fix?
mycide · Fri Sep 29, 2017 02:07 PM UTC · #34903
im no programmer but it seems it’s returning access denied to you, try to log back in to rig? or there is something else wrong.
tomos81 · Fri Sep 29, 2017 02:10 PM UTC · #34907
any1 have problem with main site? it tells me "refused to connect"
Alex · Fri Sep 29, 2017 02:12 PM UTC · #34909
@tomos81 not the main page, but the earnings page for me, they might be restarting the server?
mycide · Fri Sep 29, 2017 02:12 PM UTC · #34910
make a hard reset. pull the plugg, wait for a minute reconnect. relog, and seee if it works.
tomos81 · Fri Sep 29, 2017 02:13 PM UTC · #34911
@Alex : it’s a long restart
Red and White Shield · Fri Sep 29, 2017 02:15 PM UTC · #34913
oh is it better then the OS reboot? i thought that plugging on and off wasnt very good for the psu
mycide · Fri Sep 29, 2017 02:15 PM UTC · #34914
it would worry me too, but when in doubt make a hard reset, it solves most issues that are not bad
buster442 · Fri Sep 29, 2017 02:15 PM UTC · #34915
Same here on main website not connecting, but miners still say they are connected
mycide · Fri Sep 29, 2017 02:16 PM UTC · #34916
well, if machine is already not working not making hard reset might end up not solving the problem, i had to make hard reset on y Titans several times to get dies back up nd running when they failed.
mickeekung · Fri Sep 29, 2017 02:16 PM UTC · #34917
This site can’t be reached prohashing.com refused to connect. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED
mycide · Fri Sep 29, 2017 02:17 PM UTC · #34918
also made a few hard resets on the L3+ when i had a board show up as dead, first day of running. reboot did nothing. hard reset fixed it. havnt happen again since.
mycide · Fri Sep 29, 2017 02:18 PM UTC · #34919
it isnt very good smoking either, or speeding, or sunbathing to long. we still do it ^^
mycide · Fri Sep 29, 2017 02:19 PM UTC · #34920
risk versus reward that’s every moment of your life.
MrHollowPoints · Fri Sep 29, 2017 02:25 PM UTC · #34921
I was wondering about the hard reset. What if you manually assign IPv4 values and you have to move the device to another network. How can you get on it when it’s trying to use an IP that isn’t apart of the network you have moved it to?