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

So once again we will be performing some routine maintenance to keep the machines running clean and to also add some changes to the site. Downtime is expected to be 15 minutes.

We have bumped up our block finder reward for Guncoin from 1 gun to 2 gun per block.

We have also added 1k more block finder rewards to the Phoenixcoin pool as that seems to be a popular pool.

We will be bringing the pools down for maintenance. Downtime is expected to be 15-25 minutes.

Still chugging along. Could use some more miners, plenty of bounties still available

1) Sigil looks like an interesting concept, crowdfunding with crypto is something I personally believe we need. Adding it to the pool is a possibility dependings on thoughts with the rest of the dev team.

2) Manual difficulty is not an option currently but can be if people really wanted it. No issue adding it just havent had anyone ask yet.

3) Guncoin pool seems to be working fine, I just connected to make sure. Double check that you created a worker and added a payout address. Also what program are you using to mine and what does your conf file look like?

Just tried to get onto the GunCoin pool, no avail. Timed out. Checked, rechecked. Pretty sure I have everything right on 3337.

And I actually have a question too..... can we manually set difficulty? I tried a number of options but it didn't seem to work according to the dashboard. According to my miner it seemed to work though.

Also glad you're sticking to neoscrypt. Wondering if you'd be interested in adding Sigil.

http://sigilplatform.com/
https://bitcointalksearch.org/topic/annsgl-sigil-decentralized-0-fee-crowdfunding-2710157

Also, I think Orbit Coin developers have left the game. While you can still mine, there is no wallet available online.

I would almost perma-mine Sigil on your platform should it turn up

Trying this out.... not too many people in there at the moment making things take a while. But rewards are good

Would love it if a few more people would join

We can only do so much when it comes to attracting miners. Increasing blockfinder rewards has been discussed alot over the last couple weeks within the dev team and will most likely be implemented on a couple pools.

looks like your pools are dead. guncoin seems to be at a stall . what gives.

Another quick maintenance today to apply some security fixes. Downtime expected 10 minutes.

Pool will be going down within the next hour for routine maintenance. Downtime is expected to be 10-20 mins. Thanks everyone.

My apologies but our pool is only focused on neoscrypt algorithm coins currently. We may add more algos in the future though so feel free to ask at a later date and good luck

Hi!
Could you add LitecoinZ (LTZ) to your pool, please?
https://bitcointalksearch.org/topic/annltz-litecoinz-designed-for-the-future-2767102
https://litecoinz.info/
https://discord.gg/9ftFxhF
Thank you

Still Hashing along! Plenty of block rewards still available, come check us out

We will be taking down the pools for maintenance in the next half hour. Expected downtime is 10-20 mins.

Fees have been reduced to 0.25% for the next 2 weeks. Happy mining everyone!   

were slowly growing cheers everyone

All pools are back up and running smoothly. Thanks guys!

We will be taking to pools down for maintenance. Downtime is expected to be 30 mins

we will be adding nice hash ports to our newer coins soon. Stay tuned!

free coin just for mining with us!

block bounties have been added for gobyte and halcyon

Pools running fine! Come check us out 

More neo coins soon!

Halcyon coin has been added.

Fee have been moved to 0.5% across all pools. Blockfinder rewards still available. Cheers!

Guncoin has been added to the pool. Guncoin bounty has been moved to 1 GUN per block for the next 1000 blocks

We are currently in the process of adding more coins to the pool. We are digging through all the neoscrypt coins to see which ones are still active. Stay tuned!

Maintenance is over and all pools should be back up and running as normal. Thanks for your patience guys.

We will be taking the pool down for routine maintenance. Downtime is expected to be roughly 20mins.

We would like to remind all miners not to leave coins on the pool. Please be sure to setup Automatic payouts as to make sure you get your coins. We are a pool and not a bank, we dont want your coins just your hashes 

How about Onex (ONEX), Sigil (SGL) or Halcyon (HAL)? These are all relatively low diff coins that have reasonable profitability.

I can confirm Excavator 1.4.4.a works for me now on LSM...vardiff is bit slow to kick in (1300+ shares submitted before the default was replaced with a higher one), but it eventually settled in nicely. 30 mins of mining now (and a few blocks found!) and still ticking away.

Nice work! I'll add you guys back into rotation for my rig.

Thank you, criticism and compliments mean the world to us. Well be looking into adding more coins soon. If anyone has specific coins they would like to see on the pool please hit us up with a PM or just post here.

Thanks guys and see ya at the pool!

good design. I hope you will add more neoscypt pools. TUN, DSR etc...

if you wanted to make 2 miners into one than you could so something like this.

 {"time":3,"commands":[
      {"id":1,"method":"worker.add","params":["0","0"]},
      {"id":1,"method":"worker.add","params":["0","0"]},
      {"id":1,"method":"worker.add","params":["0","1"]},
      {"id":1,"method":"worker.add","params":["0","1"]},
      {"id":1,"method":"worker.add","params":["0","2"]},
      {"id":1,"method":"worker.add","params":["0","2"]}
   ]},

If you wanna overclock you can try something like this

 {"time":5,"commands":[
      {"id":1,"method":"device.set.power_limit","params":["0","90"]},
      {"id":1,"method":"device.set.core_delta","params":["0","160"]},
      {"id":1,"method":"device.set.memory_delta","params":["0","600"]},

I wanna say if your going for a backup pool than your gonna wanna change the ID. Kinda like this.

[
   {"time":0,"commands":[
      {"id":1,"method":"algorithm.add","params":["neoscrypt","ftc.lightspeedmining.com:3333","myname.myrig:x"]},
   {"time":0,"commands":[
      {"id":2,"method":"algorithm.add","params":["neoscrypt","pxc.lightspeedmining.com:3334","myname.myrig:x"]}
   ]},
   {"time":3,"commands":[
      {"id":1,"method":"worker.add","params":["0","0"]},
      {"id":1,"method":"worker.add","params":["0","1"]},
      {"id":1,"method":"worker.add","params":["0","2"]},
      {"id":1,"method":"worker.add","params":["0","3"]},
      {"id":1,"method":"worker.add","params":["0","4"]},
      {"id":1,"method":"worker.add","params":["0","5"]},
      {"id":2,"method":"worker.add","params":["0","0"]},
      {"id":2,"method":"worker.add","params":["0","1"]},
      {"id":2,"method":"worker.add","params":["0","2"]},
      {"id":2,"method":"worker.add","params":["0","3"]},
      {"id":2,"method":"worker.add","params":["0","4"]},
      {"id":2,"method":"worker.add","params":["0","5"]}
   ]},
   {"time":10,"loop":10,"commands":[
      {"id":1,"method":"worker.print.speed","params":["0"]},
      {"id":1,"method":"worker.print.speed","params":["1"]},
      {"id":1,"method":"worker.print.speed","params":["2"]},
      {"id":1,"method":"worker.print.speed","params":["3"]},
      {"id":1,"method":"worker.print.speed","params":["4"]},
      {"id":1,"method":"worker.print.speed","params":["5"]},
      {"id":1,"method":"algorithm.print.speeds","params":["1"]},
      {"id":2,"method":"worker.print.speed","params":["0"]},
      {"id":2,"method":"worker.print.speed","params":["1"]},
      {"id":2,"method":"worker.print.speed","params":["2"]},
      {"id":2,"method":"worker.print.speed","params":["3"]},
      {"id":2,"method":"worker.print.speed","params":["4"]},
      {"id":2,"method":"worker.print.speed","params":["5"]},
      {"id":2,"method":"algorithm.print.speeds","params":["2"]}
   ]}
]

Excavator seems rather endless is config options but the basis seems pretty simple.

Try this it should work fine. From what i understand with excavator, you add more workers by changing far right parameter. The ID should stay 1.


[
   {"time":0,"commands":[
      {"id":1,"method":"algorithm.add","params":["neoscrypt","ftc.lightspeedmining.com:3333","myname.myrig:x"]}
   ]},
   {"time":3,"commands":[
      {"id":1,"method":"worker.add","params":["0","0"]},
      {"id":1,"method":"worker.add","params":["0","1"]},
      {"id":1,"method":"worker.add","params":["0","2"]},
      {"id":1,"method":"worker.add","params":["0","3"]},
      {"id":1,"method":"worker.add","params":["0","4"]},
      {"id":1,"method":"worker.add","params":["0","5"]}
   ]},
   {"time":10,"loop":10,"commands":[
      {"id":1,"method":"worker.print.speed","params":["0"]},
      {"id":1,"method":"worker.print.speed","params":["1"]},
      {"id":1,"method":"worker.print.speed","params":["2"]},
      {"id":1,"method":"worker.print.speed","params":["3"]},
      {"id":1,"method":"worker.print.speed","params":["4"]},
      {"id":1,"method":"worker.print.speed","params":["5"]},
      {"id":1,"method":"algorithm.print.speeds","params":["1"]}
   ]}
]

This is what I have:
[
   {"time":0,"commands":[
      {"id":1,"method":"algorithm.add","params":["neoscrypt","ftc.lightspeedmining.com:3333","myname.myrig:x"]}
   ]},
   {"time":3,"commands":[
      {"id":1,"method":"worker.add","params":["0","0"]},
      {"id":2,"method":"worker.add","params":["0","1"]},
      {"id":3,"method":"worker.add","params":["0","2"]},
      {"id":4,"method":"worker.add","params":["0","3"]},
      {"id":5,"method":"worker.add","params":["0","4"]},
      {"id":6,"method":"worker.add","params":["0","5"]}
   ]},
   {"time":10,"loop":10,"commands":[
      {"id":1,"method":"worker.print.speed","params":["0"]},
      {"id":2,"method":"worker.print.speed","params":["1"]},
      {"id":3,"method":"worker.print.speed","params":["2"]},
      {"id":4,"method":"worker.print.speed","params":["3"]},
      {"id":5,"method":"worker.print.speed","params":["4"]},
      {"id":6,"method":"worker.print.speed","params":["5"]},
      {"id":1,"method":"algorithm.print.speeds","params":["0"]}
   ]}
]

is your miner name correct? Seems to be failing on worker authenticate

i run these settings and it works fine

[
   {"time":0,"commands":[
      {"id":1,"method":"algorithm.add","params":["neoscrypt","ftc.lightspeedmining.com:3333","worker.1:password1234"]}
   ]},
   {"time":3,"commands":[
      {"id":0,"method":"worker.add","params":["0","0"]},
      {"id":0,"method":"worker.add","params":["0","1"]}
   ]},
   {"time":10,"loop":10,"commands":[
      {"id":1,"method":"worker.print.speed","params":["0"]},
      {"id":1,"method":"algorithm.print.speeds","params":["1"]}
   ]},
   {"time":10,"commands":[
      {"id":1,"method":"worker.reset","params":["0"]},
      {"id":1,"method":"worker.reset","params":["1"]},
      {"id":1,"method":"worker.reset","params":["2"]}
   ]}
]

Now its completely broken:

[14:51:22][0x00004848][info] core | Initialized!
[14:51:22][0x000056dc][info] net | Connecting to 192.223.28.224:3333 (ftc.lightspeedmining.com)
[14:51:22][0x000056dc][info] net | Connected!
[14:51:22][0x00005f6c][warning] net | Net error: JSON member "error" not expected type: Array
[14:51:22][0x000056dc][info] algo-neoscrypt | New job_0 '1cdc', diff=0.000488281
[14:51:24][0x000056dc][info] algo-neoscrypt | New job_0 '1cdd', diff=0.000488281
[14:51:26][0x0000297c][info] wrkr1-1 | Algorithm: CUDA-neoscrypt parameters: B=1792
[14:51:26][0x000021cc][info] wrkr0-0 | Algorithm: CUDA-neoscrypt parameters: B=1792

There is an error as you can see above, then hashrate is reported but no submits and the miner also does not show up on dashboard.

Thanks! Will checkout shortly.

Still chugging along. Bounties still available, easy coin just for helping us find a block 

Good news everyone

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!

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

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.

still cruising come check us out 

Bounties still available. Free extra coin for helping us find some blocks

Modulo zero errors fixed if you had any. Doing quick restart of of the pools to apply changes. Should only be 5 minute downtime.

Yep, Blocksfactory has the same issues.

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. 

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.

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.

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).

Its next on my list ill update when i get some data to play with

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

Had the same issue with Excavator and FTC.

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

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.

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  

*bump* pools running great