Pages:
Author

Topic: [ANN][NEOSCRYPT MULTIPOOL] LightSpeedMining.com - ⛏️Blockfinder Rewards - page 3. (Read 523 times)

member
Activity: 531
Merit: 29
Good news everyone Cool

Excavator should now work as expected on our pool. Need some more peeps to hop on and try it out to fully confirm.

Nicehash ports have been added for the pool

FTC port = 3343
ORB port = 3345
PXC port = 3344


Thanks again guys and see ya at the pool!

Thanks! Will checkout shortly.
newbie
Activity: 98
Merit: 0
Still chugging along. Bounties still available, easy coin just for helping us find a block  Grin
newbie
Activity: 98
Merit: 0
Good news everyone Cool

Excavator should now work as expected on our pool. Need some more peeps to hop on and try it out to fully confirm.

Nicehash ports have been added for the pool

FTC port = 3343
ORB port = 3345
PXC port = 3344


Thanks again guys and see ya at the pool!
newbie
Activity: 98
Merit: 0
I dont blame you at all. If you get better hashrates than why not use the software. Its definitely not our goal to support some miners and not others, right now were developing our own stratum fork to hopefully put this issue to rest. Once everything gets sorted out with excavator I hope to see ya back in the pool Smiley
newbie
Activity: 67
Merit: 0
Thanks for the tests.

The thing is Excavator is by far the fastest while doing Neoscrypt, so I can't use anything but that. And I have no issues with Excavator on AHashpool, Altmier, Zpool and MPH.

So there is something to be sorted out between the the communications between your Server and Excavator.

Same here. Excavator gives me a 20%+ increase in actual hashrate on other pools (Zerg, AHashpool, Zpool, unimining.net, MPH and many others), so they must have done something to make their stratum "compatible", perhaps specific to NiceHash (since that is what excavator is designed for).

Not sure if the 1.4.4a release changed anything, but I can't afford to use the slower clients you mentioned.
newbie
Activity: 98
Merit: 0
still cruising come check us out  Cool
newbie
Activity: 98
Merit: 0
Bounties still available. Free extra coin for helping us find some blocks Smiley
newbie
Activity: 98
Merit: 0
Modulo zero errors fixed if you had any. Doing quick restart of of the pools to apply changes. Should only be 5 minute downtime.
member
Activity: 531
Merit: 29
We also tried excavator on blocksfactory just to make sure and got alot of errors as well so I know our pool isnt exclusive with this issue. Honestly its very weird i agree but other miners (specifically the ones by ghostlander) seem to run fine.  Huh

Yep, Blocksfactory has the same issues.
newbie
Activity: 98
Merit: 0
We also tried excavator on blocksfactory just to make sure and got alot of errors as well so I know our pool isnt exclusive with this issue. Honestly its very weird i agree but other miners (specifically the ones by ghostlander) seem to run fine.  Huh
member
Activity: 531
Merit: 29
Thanks for the tests.

The thing is Excavator is by far the fastest while doing Neoscrypt, so I can't use anything but that. And I have no issues with Excavator on AHashpool, Altmier, Zpool and MPH.

So there is something to be sorted out between the the communications between your Server and Excavator.
newbie
Activity: 98
Merit: 0
Ok so weve spent the better half of our weekend testing things on the server and checking back end code to make sure we do not have any issues on our side. Weve tweaked a couple things here and there but the pool is definitely running as it should. We are 100% sure of this.

Now on to the miners.

Excavator:

Excavator seems to run fine for the first few hundred shares than it gets stuck submitting the same work repeatably until it clears cache or something. This work obviously gets rejected as it is old, this is not a fault of the server.


Palgin-Neoscrypt:

Palgin seems to run fine. We have run the software on 3 different machines all today and we average 1 reject an hour which is perfectly fine. As for the "long division or modulo by zero" error you recieved. We did get it one time but after restarting it, it continued mining for several hours. Overall the miner seems fine but has some small stability problems, it has crashed randomly twice. Just closed the window and went away lol.


Personally id recommend using one of the software downloads from our help page. I know id mined with the software for weeks and they work fine, also no 1% fee built in.
newbie
Activity: 67
Merit: 0
Tried with Palgin-Neoscrypt on PXC and just hit a wall of "long division or modulo by zero" errors after about 15 minutes that I've never seen before, so still something funky going on.

I'm back to KlausT for now, as that seems the most resilient/compatible (though slowest of the 3).
newbie
Activity: 98
Merit: 0
Ive ran through some config settings and adjusted them to update work sent to miners more frequently. Currently running nsgminer of one rig and ccminer on another with 0 rejects so far. Although im running feathercoin right now. Gonna let it run for a couple thousand shares to confirm the problem is fixed. Ill plug up to PXC server to test it after

Please test with Excavator. I stopped because of issues with it.

Its next on my list ill update when i get some data to play with
member
Activity: 531
Merit: 29
Ive ran through some config settings and adjusted them to update work sent to miners more frequently. Currently running nsgminer of one rig and ccminer on another with 0 rejects so far. Although im running feathercoin right now. Gonna let it run for a couple thousand shares to confirm the problem is fixed. Ill plug up to PXC server to test it after

Please test with Excavator. I stopped because of issues with it.
member
Activity: 531
Merit: 29
Having some challenges getting Excavator (nicehash) Neoscrypt client to run against either the PXC or ORB stratum...it begins to fail about around 1000 shares in endlessly complaining about an "invalid job id". I've had to downgrade to Palgin/KlausT Neoscrypt client for now, but I haven't had a similar problem mining PXC/ORB elsewhere with Excavator. No OC involved; vanilla settings on all GPUs and this is a well-tested rig.

Anything "special" about the stratum that could be causing this? I do notice the starting vardiff is quite low and slow to adjust, causing a large volume of shares to be submitted for the first 10 minutes or so of mining.

Had the same issue with Excavator and FTC.
newbie
Activity: 98
Merit: 0
Ive ran through some config settings and adjusted them to update work sent to miners more frequently. Currently running nsgminer of one rig and ccminer on another with 0 rejects so far. Although im running feathercoin right now. Gonna let it run for a couple thousand shares to confirm the problem is fixed. Ill plug up to PXC server to test it after
newbie
Activity: 67
Merit: 0
Having some challenges getting Excavator (nicehash) Neoscrypt client to run against either the PXC or ORB stratum...it begins to fail about around 1000 shares in endlessly complaining about an "invalid job id". I've had to downgrade to Palgin/KlausT Neoscrypt client for now, but I haven't had a similar problem mining PXC/ORB elsewhere with Excavator. No OC involved; vanilla settings on all GPUs and this is a well-tested rig.

Anything "special" about the stratum that could be causing this? I do notice the starting vardiff is quite low and slow to adjust, causing a large volume of shares to be submitted for the first 10 minutes or so of mining.
newbie
Activity: 98
Merit: 0
Our sincerest apologies for the downtime on the feathercoin pool. The new feathercoin wallet did not play well with the stratum software at all as some of you probably noticed with all high percentage of stale shares. We have adjusted backend code accordingly so that feathercoin and stratum play nice together again so the problem should be resolved. The pool has been moved to 0% fees for the next 2 days with block bounties still available. Our apologies again and thank you for mining with us   Smiley
newbie
Activity: 98
Merit: 0
*bump* pools running great  Smiley
Pages:
Jump to: