Chat archive · 2018-05

Using EWBF miner, and it didn’t switch to next pool in miner.cfg. Any thoughts on set up sticking points?

Perhaps I’m missing something.

Thanks for the update

ok, problem fixed

when the fix for the original issue was released, the release contained the IP address of the development server

so we simply changed it to the correct IP address and everything is working now

still x11 pool issues

Steve Sokolowski wrote:

jwillson wrote: Thanks Steve. Yes I do have a GPU. Can I do equihash with prohashing?

Yes. Just use the password argument "a=equihash"

Steve Sokolowski wrote:

jwillson wrote: Thanks Steve. Yes I do have a GPU. Can I do equihash with prohashing?

Yes. Just use the password argument "a=equihash"

That gives me an auth failed error

Hello The Script pool is Dead my antminer does not mine on your pool http://prohashing.com:3333 basically only SHA-256 pool is active will this be fixed soon or is it the and of prohasing for my antminers?

That gives me an auth failed error

have this issue with my scrypt miner of BW and rig, just use a=equihash and nothing else, if u use any other arg like n=.. or d=.. you will get that error

dempor wrote: Hello The Script pool is Dead my antminer does not mine on your pool http://prohashing.com:3333 basically only SHA-256 pool is active will this be fixed soon or is it the and of prohasing for my antminers?

scrypt pool is working fine, try to restart your miners

n=.. or d=.. you will get that error [/quote] - I get the error, even with just the a= parameter.

It has started just now

CSZiggy wrote: dont think the wamp pricing issue has been resolved yet.

I don’t see that

the number of coins appear to be normal now

Steve, How does the "live balances" now work? Is this real data? Or then again write that there was an error and reduce the balance?

I am using the following command line: cgminer.exe -o startum+tcp://prohashing.com:3333 -u jwillson.miner1 -p "a=equihash". and still get: poll 0 JSON stratum auth failed: (unknown reason) - Also tried without the quotes, and get the same result.

CSZiggy wrote: put in a comma to seperate them

Thanks, have treid with and without the comma, and without the n= parameter, still get auth failed

jwillson wrote:

CSZiggy wrote: put in a comma to seperate them

Thanks, have treid with and without the comma, and without the n= parameter, still get auth failed

- any suggestions Steve?

maybe try stratum instead of startum ... just sayin’

jason.statham+tcp://prohashing.com:3333

no fee’s but a lot of pee in his pool

thnx for getting it back up quickly today

@steve great pool, like to challenge everybody who says it suck name a pool who does the same!

@cloaker nice one whahaha

@me did it 2 typo’s

space after a user name in minera ... took me 2 day 2 figure it out. saw it by acident whit copy paste

S3KshuN8 wrote: maybe try stratum instead of startum ... just sayin’

Tried that and still getting the same problem.

@jwilson - mine say stratum+tcp://prohashing.com:3333 you can try the proxy stratum+tcp://prohashing.com:433

for a scrypt miner like L3 you can use http://prohashing.com:3333/ with easier success if your having issues

if it’s something like sha mining rig -or- you have to use stratum use stratum+tcp://prohashing.com:3333

just know that you should insure the ports your trying are not blobked...you can check those anywhere online

you see different miners can require slightly different variations.....im using whatsminer M3 v2 for sha-mining and none of my previous settings for other miners worked i just had to sit there like a rubics cube

trying different variations and googling the hell out of support forums everywhere til someone got a response that worked for me

someone has already had your issue, as long as you have seen the unit hash you know it works and should continue ona similar course

cuz the answer is out there.....................x-files

Ok I am trying to wrap my head around this. Pool is reporting a 100% in recrease in connected miners. From 5000 to 10,000. Now lets get real.

Increase

i didnt know it was hard coded in there but that’s smart......i didn’t read back far enuff to see if he EVER seen it working for any setting

fundough wrote: Ok I am trying to wrap my head around this. Pool is reporting a 100% in recrease in connected miners. From 5000 to 10,000. Now lets get real.

/yet, the pool hashrate remains the same?? somethings not quite right, hmmmm.......

it could also be the number of miners versus the number of accounts... ie I have had up to 10 miners pointed here...

CSZiggy wrote: Its new users its miners, I’ll bet someone picked up 5000 of those USB miners on the cheap and plugged them into a USB grid and turned on an amazing 100 MH of scrypt or something.

thats funny. Most likely.

Since the reboot, I’m pointing the scrypt ones elsewhere as the reset penalty is reducing my hash rate dramatically

Foxx wrote:

fundough wrote: Ok I am trying to wrap my head around this. Pool is reporting a 100% in recrease in connected miners. From 5000 to 10,000. Now lets get real.

/yet, the pool hashrate remains the same?? somethings not quite right, hmmmm.......

the number of miners is calculated by the number of balance changes during the day, and that was the number of transaction fee credits Chris gave that day

most of the transaction fee credits were very small, to a lot of people

Whatever is happening currently, its fully Pitiful, performance wise in no uncertain terms....

starcat wrote: Whatever is happening currently, its fully Pitiful, performance wise in no uncertain terms....

We’re not aware of any system-wide issues; please submit a support ticket and we’ll be glad to assist you

Steve, what I believe I observed is excessive work restart delays on ASICs - eg 3 seconds plus (in addition to the 1 second restart). I assumed this was a planned feature.

alim wrote: Steve, what I believe I observed is excessive work restart delays on ASICs - eg 3 seconds plus (in addition to the 1 second restart). I assumed this was a planned feature.

there were no changes to the code that handles share acceptance or work restarts, and my testing hasn’t shown any differences, so I think you should investigate your setup to see if something coincidentally occurred during the same time. A pool can't set how long a miner takes to start working.

Hi Steve!

I wanted to let you know the Cypherfunk wallet has been updated

Will you please update your wallet?

soundposition wrote: has started a new topic: The Cypherfunks has updated to 0.15.1!

Thanks for the notice - I’ll submit a support ticket to Chris about this

Thanks Steve you’re the best!!

I just installed recaptcha v2 to the forums, so the spam should no longer pop up.

Chris Sokolowski wrote: I just installed recaptcha v2 to the forums, so the spam should no longer pop up.

spam is back

Spam detected

Chris Sokolowski wrote: I just installed recaptcha v2 to the forums, so the spam should no longer pop up.

Maybe you need a time machine and recaptcha v3 or v4 ?

With the 51% attack on btg, is it going to be disabled per policy? https://bitcointalk.org/index.php?topic ... sg37668133

Blahminer wrote: has started a new topic: L3+ hash rate going up and down

mine too!