[POOL][Scrypt][Scrypt-N][X11] Profit switching pool - wafflepool.com

[UniMatrixZ]

I have set my password to d=4096 for my ~12Mhs Scrypt ASIC rig, but it seems it is stuck at diff 512.
Any ideas?

Sorry, forgot to make a post here.  It was disabled on the restarts yesterday while working on some tweaks, should be re-enabled soon.

Any ETA on re-enable diff setting on scrypt port?

[UniMatrixZ]

What's up with eu scrypt port I'm getting 40% rejects???

[DareC]

Any chance of adding more algorithms? X13 is pretty popular.

[ingrown]

Any chance of adding more algorithms? X13 is pretty popular.

Someone might have mentioned that three posts above yours.

[m0narch]

Any chance of adding more algorithms? X13 is pretty popular.

Someone might have mentioned that three posts above yours.

Hilarious isn't it?

[UniMatrixZ]

Will you be adding more X11 coins?

This week 8 new X11 coins is launched  
https://www.altcoincalendar.info/calendar

And are we mining blucoin on scrypt?

[Starscream]

Update www.wafflepoolmonitor.com



Hi, the website has been updated with seperate stats for scrypt, scrypt-n and x11 and is now using the new api.
Hope you find it useful.

Regards,

Good job.

[vladman]

I don't know if anyone here uses PiMP.... I've set it up to mine X11 on WP, and it seems to be working fine, except for one thing which I'm unsure about.

I'm seeing a huge number under the "Discarded" value on the pool stats screen, and this number is constantly growing.  I don't know what this means, and it's a bit worrying.  I'm confused though, as everything else seems fine, WP is registering my hashrate, my balances on my miner stats page are growing, I got paid this morning, I have no HW errors and my rejects are low.

So what could that number mean, and do I need to worry about it?

Here's the screenshot:

[t00tie]

Is diff broken? My 88mh scrypt asic is very unhappy at d=512, I tried -p d=1024 to test but I only get 512. I should be at 32k according to the faq?

[Badman0316]

Is diff broken? My 88mh scrypt asic is very unhappy at d=512, I tried -p d=1024 to test but I only get 512. I should be at 32k according to the faq?

same

[jasabbm]

Dear wafflepool,

Please stop mining silkcoin for 5 hours plssssssssssssssss

let us with low rigs mining it

you eat all blocks, omg

Thanks

[srSheepdog]

Dear wafflepool,

Please stop mining silkcoin for 5 hours plssssssssssssssss

let us with low rigs mining it

you eat all blocks, omg

Thanks

NOM NOM NOM...SILKCOIN BLOCKS DELICIOUS!!!...NOM NOM NOM

lol

Seriously though, come to the dark side and mine with us.  This is a very well run pool, with a VERY communicative admin and a supportive community as well.  Come join us!

[chadwickx16]

Dear wafflepool,

Please stop mining silkcoin for 5 hours plssssssssssssssss

let us with low rigs mining it

you eat all blocks, omg

Thanks

NOM NOM NOM...SILKCOIN BLOCKS DELICIOUS!!!...NOM NOM NOM

lol

Seriously though, come to the dark side and mine with us.  This is a very well run pool, with a VERY communicative admin and a supportive community as well.  Come join us!

Damn, that was funny!!! 

[poolwaffle]

Is diff broken? My 88mh scrypt asic is very unhappy at d=512, I tried -p d=1024 to test but I only get 512. I should be at 32k according to the faq?

same

Yep, it was disabled for a day or so while working on something (one less variable), but it re-enabled now

[UniMatrixZ]

Is diff broken? My 88mh scrypt asic is very unhappy at d=512, I tried -p d=1024 to test but I only get 512. I should be at 32k according to the faq?

same

Yep, it was disabled for a day or so while working on something (one less variable), but it re-enabled now

Wonderful, now my ASIC is happy again 

[libbyporit]

Hi waffle,

I know the next step for you is X13, as you mentioned. Then combining payouts, got it. But whats your overall vision right now? Multi-algo switching? Keep em separate? Deploy wafflecoin? {/joke}
Any insight would be appreciated.

[poolwaffle]

Hi waffle,

I know the next step for you is X13, as you mentioned. Then combining payouts, got it. But whats your overall vision right now? Multi-algo switching? Keep em separate? Deploy wafflecoin? {/joke}
Any insight would be appreciated.

Good question

X13 is the obvious first step.  I'm in the zone with adding the new algorithms, and X13 shouldn't be much work to add from X11.  I'm out of town this weekend, so it probably won't be finished until next week, but should be pretty quick.

After that, like you said, combining payouts has been a major request, and shouldn't be much work.  It should have been done by now, but I like to be extra cautious on things like payouts.  Don't want anything to screw up there

Past that, I like the idea of the algo-switching, but it does require some extra thinking.  The way it is done with NiceHash is really neat (props to them for the idea, and funding the custom version of sgminer), but at this point, the new version of sgminer seems to have some issues.  Ideally by the time I've got the other stuff done, the major kinks will be worked out in the new sgminer version, and we can look into an algo-switching version of WP.  The actual algo-switching part isn't too tough (pretty easy in fact), the bigger issue is figuring out how to do the switching based on user preferences.  For example, if your miner can do 1MHs Scrypt, and 6MHs X11 (normal is 4MHs X11 for a 1MH scrypt), you would need to be treated differently in terms of what is profitable than someone with 1MH/4MH.  There is also the difference of preference of power consumption.  Some people would like to bias their miners towards X11/X13 because of the power savings, some users don't care, and would prefer to mine whatever is the most profitable (regardless of power costs).

Doing algo-switching on a generic level (preset values) is reasonably easy.  Doing algo-switching with user preferences becomes quite a bit more difficult

[utahjohn]

@PW
Please consider algorithm groestl also

[suchmoon]

The way it is done with NiceHash is really neat

I wouldn't call it that, it's a hack really, hopefully temporary until a better solution evolves. It doesn't allow to pick which algorithms to use (along with the complete lack of user preferences as you mentioned), it only works with AMD GPUs, it requires to set up a separate "pool" for each algorithm (times 2 or 3 with backups), and is generally not scalable. It's not hard to imagine that a possible future path for GPU mining might be a growing/changing list of algos to choose from, so there has to be a better way to do the choosing.

[chadwickx16]

Hi waffle,

I know the next step for you is X13, as you mentioned. Then combining payouts, got it. But whats your overall vision right now? Multi-algo switching? Keep em separate? Deploy wafflecoin? {/joke}
Any insight would be appreciated.

Good question

X13 is the obvious first step.  I'm in the zone with adding the new algorithms, and X13 shouldn't be much work to add from X11.  I'm out of town this weekend, so it probably won't be finished until next week, but should be pretty quick.

After that, like you said, combining payouts has been a major request, and shouldn't be much work.  It should have been done by now, but I like to be extra cautious on things like payouts.  Don't want anything to screw up there

Past that, I like the idea of the algo-switching, but it does require some extra thinking.  The way it is done with NiceHash is really neat (props to them for the idea, and funding the custom version of sgminer), but at this point, the new version of sgminer seems to have some issues.  Ideally by the time I've got the other stuff done, the major kinks will be worked out in the new sgminer version, and we can look into an algo-switching version of WP.  The actual algo-switching part isn't too tough (pretty easy in fact), the bigger issue is figuring out how to do the switching based on user preferences.  For example, if your miner can do 1MHs Scrypt, and 6MHs X11 (normal is 4MHs X11 for a 1MH scrypt), you would need to be treated differently in terms of what is profitable than someone with 1MH/4MH.  There is also the difference of preference of power consumption.  Some people would like to bias their miners towards X11/X13 because of the power savings, some users don't care, and would prefer to mine whatever is the most profitable (regardless of power costs).

Doing algo-switching on a generic level (preset values) is reasonably easy.  Doing algo-switching with user preferences becomes quite a bit more difficult

If you do end up implementing an algo switcher, I would like to be able to opt-out of it. I am mining X11 right now due to power constraints, if I switch back to scrypt I'll pop the breaker.