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

[gaalx]

Yeah, but I am using an X11 multipool (waiting for Waffle!) which pays the rates you say about .003, but
i use half the electricity, so that is a big plus in profits.

at what multipool x11 you work?

[1715330395]

1715330395

[1715330395]

1715330395

[phzi]

Later today we'll be switching the way shifts are ended, basically no one should really notice any change, just figured I'd mention it before getting emails/posts
<snip>

Awesome!  Variable shift length is nice feature addition.

Yeah, but I am using an X11 multipool (waiting for Waffle!) which pays the rates you say about .003, but
i use half the electricity, so that is a big plus in profits.

I'm averaging .006BTC/MH/day (scrypt equivalent) with nscrypt(n=11) these days (~.0125BTC/MH/day in nscrypt MH).

[Jynger]

where are you averaging .006BTC/MH/day (scrypt equivalent)?

[phzi]

where are you averaging .006BTC/MH/day (scrypt equivalent)?

Mostly Nscrypt coins + manual trading.  Some leasing.

[pj40]

Hoping to see scrypt-n added to the pool.  That would be a great option for those of us who are still on gpu's and want to keep the dream alive once asic's completely overtake scrypt.

[poolwaffle]

Without further delay, I'm happy to announce Wafflepool now supports multiple algorithms.

Before you read anything more about this, please know that this is in BETA and will be in BETA for another few days.  It has been tested by me, and me alone.  Using personal rigs and rented rigs, everything looks fine.  But there may be problems, and there may be downtime.  If everything goes well in the beta, I'll make a post here, and it will be posted on the WP homepage as well.  Until then, this is a "try at your own risk" type of thing (I don't think the risk is very high, but better safe than sorry).  All stats are currently tracked separately, this means for the time-being at least, if you participate in the beta, you may be paid twice (once per algorithm) per payout.

For the beta, profits will be lower than they will be when we fully launch, this is because we are actively minimizing variables for debugging purposes.  Each of these things will be removed one at a time, to make sure everything works properly:
- We are only supporting USEast during the beta
- We are limiting the number of coins on Scrypt-N (low difficulty - so we can find a larger number of blocks for testing).
- Hashrate will be pretty low (or at least sporadic) as its only in beta, leading to more spikes in block finding.

Once everything looks good, we'll be expanding this to more algorithms (X11, possibly more), expanding it to the rest of the servers (geo-located endpoints), and adding more coins to maximize profitability.


If you'd like to participate in the BETA, you can go here: http://wafflepool.com/newalgos

[pj40]

Without further delay, I'm happy to announce Wafflepool now supports multiple algorithms.

Before you read anything more about this, please know that this is in BETA and will be in BETA for another few days.  It has been tested by me, and me alone.  Using personal rigs and rented rigs, everything looks fine.  But there may be problems, and there may be downtime.  If everything goes well in the beta, I'll make a post here, and it will be posted on the WP homepage as well.  Until then, this is a "try at your own risk" type of thing (I don't think the risk is very high, but better safe than sorry).  All stats are currently tracked separately, this means for the time-being at least, if you participate in the beta, you may be paid twice (once per algorithm) per payout.

For the beta, profits will be lower than they will be when we fully launch, this is because we are actively minimizing variables for debugging purposes.  Each of these things will be removed one at a time, to make sure everything works properly:
- We are only supporting USEast during the beta
- We are limiting the number of coins on Scrypt-N (low difficulty - so we can find a larger number of blocks for testing).
- Hashrate will be pretty low (or at least sporadic) as its only in beta, leading to more spikes in block finding.

Once everything looks good, we'll be expanding this to more algorithms (X11, possibly more), expanding it to the rest of the servers (geo-located endpoints), and adding more coins to maximize profitability.


If you'd like to participate in the BETA, you can go here: http://wafflepool.com/newalgos

Sweet!  I'll be testing out some Scrypt-N tonight when I get home.

[phzi]

[snip]
If you'd like to participate in the BETA, you can go here: http://wafflepool.com/newalgos

Awesome!  Congratulations on the huge milestone in WafflePool's history, PoolWaffle.

Looks like we've already got a bit of nscrypt hashing power going, and the blocks are rolling in.

I'll move at least one of my rigs here to help test the system in a few hours (everything is leased out right now, heh).

---

Do you think you'll have 'hold-back' coins available anytime soon?  I would definitely be interested in holding at least a coin or two with these new algos.

[phzi]

@PoolWaffle: with nscrypt, is the vs LTC rate calculated against nscrypt(n=11) MH rates?
On average nscrypt(n=11) is half the speed of nscrypt(n=10), so I presume from the small test window so far, we're actually closer to 108% LTC profitability, rather then the displayed 54%?
(Or are you doubling the value already?)

[suchmoon]

Miners: 6

So who's the other 5?

Thank you poolwaffle, looking forward to X11 too.

[poolwaffle]

@PoolWaffle: with nscrypt, is the vs LTC rate calculated against nscrypt(n=11) MH rates?
On average nscrypt(n=11) is half the speed of nscrypt(n=10), so I presume from the small test window so far, we're actually closer to 108% LTC profitability, rather then the displayed 54%?
(Or are you doubling the value already?)

Currently the "vs LTC" rate is raw nscrypt.  So ideally that will be showing "200%" when things are up to speed.  The reason it is rediculously low today is because it didn't go live until like 3/4 of the way through the day (about 2pm EST, day ends at 8pm EST), and is calculating based on a full 24hr of LTC mining

Tomorrow (an hour from now) we'll have new stats, and should be much closer to actual.  My admin graph shows the last 3 hours (the only 3 hours) were at roughly 130%, 300%, 160% (which looks about right, and spikey due to very low hashrate)

[phzi]

@PoolWaffle: with nscrypt, is the vs LTC rate calculated against nscrypt(n=11) MH rates?
On average nscrypt(n=11) is half the speed of nscrypt(n=10), so I presume from the small test window so far, we're actually closer to 108% LTC profitability, rather then the displayed 54%?
(Or are you doubling the value already?)

Currently the "vs LTC" rate is raw nscrypt.  So ideally that will be showing "200%" when things are up to speed.  The reason it is rediculously low today is because it didn't go live until like 3/4 of the way through the day (about 2pm EST, day ends at 8pm EST), and is calculating based on a full 24hr of LTC mining

Tomorrow (an hour from now) we'll have new stats, and should be much closer to actual.  My admin graph shows the last 3 hours (the only 3 hours) were at roughly 130%, 300%, 160% (which looks about right, and spikey due to very low hashrate)

Ahhhh... oops right, got my math backwards for a second there, heh.  That makes much more sense tho.

Going to be interesting watching the EXECoin price over the next few days.

[edonkey]

A couple of quick questions regarding the Scrypt-N beta.

Can we append worker names to the end of our BTC address, like we can with the scrypt pool? Sorry, but this wasn't clear from the beta notes.

I have only have a pathetic amount of hash to point at the beta currently. I've got around 40 KH/s now, and can bring that up to around 90 KH/s later tonight. What difficulty should I use? Looks like 8 is the lowest.

[edonkey]

Can we append worker names to the end of our BTC address, like we can with the scrypt pool? Sorry, but this wasn't clear from the beta notes.

Never mind. I just tried it and the answer of course is yes. I can see my worker name under the "nscrypt" stats.

I still don't know what difficulty to use for such a small amount of hash, so I'm using 8 for now.

[edonkey]

Miners: 6

So who's the other 5?

Thank you poolwaffle, looking forward to X11 too.

I guess I'm number 7 now ;-)

Yeah, what suchmoon said. Thanks for this. It's very cool.

Poolwaffle, where should we provide beta feedback? Should it be here in the public forum, or would you prefer PMs?

[zneww]

Miners: 6

So who's the other 5?

Thank you poolwaffle, looking forward to X11 too.

I guess I'm number 7 now ;-)

Yeah, what suchmoon said. Thanks for this. It's very cool.

Poolwaffle, where should we provide beta feedback? Should it be here in the public forum, or would you prefer PMs?

Congrats on being the third pool out with it. Maybe it will bring some other people to Scrypt-N

TMB and Coinsolver have had Scrypt-N pools for some time now.

[ericlfg]

Great work PW!  I'm definitely one of the few mining.  

What's everyone using for miner?  I'm currently using vertminer 0.5.3

As for diff, I coded 16 into the password field, but the cmd window is showing 4.

[m0narch]

I'll be switching my GPU rigs over to the new pool as soon as information is available for those of us who haven't done scrypt-n before. Appreciate the hard work in getting this project going PW.

[phzi]

Great work PW!  I'm definitely one of the few mining.  

What's everyone using for miner?  I'm currently using vertminer 0.5.3

As for diff, I coded 16 into the password field, but the cmd window is showing 4.

I use the latest sgminer compiled from git. I ran into annoying bugs with vertminer a few times (crashes, declining hashrate, etc). Plus, sgminer let's you hot swap between scrypt and nscrypt pools without restarting the miner.

https://github.com/sgminer-dev/sgminer

Looks like there is even some new auto-tuning functionality that was committed recently.

[ericlfg]

<-- noob.  I've read that scypt-n produces lower hashes, but wanted to make sure I'm drinking the right koolaid.