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

[phzi]

Still the rejectrate is kinda sick low. I've got one GPU that has 2045160 accepted shares and 1920 rejected. That's less than 0,1%... (connected to main server wafflepool.com and living near Amsterdam).

Keep in mind, this is the same for everyone, so your profit won't likely be higher as a result of lower rejects.  Wafflepool accepts shares that are 1 block old (just not two blocks old).  This is unlike middlecoin, that stops accepts shares for the previous block as soon as a new block is found.  This means everyone has the same advantage of lower shares on wafflepool.

All this said, I like wafflepool's stale strategy a lot more, as it seems to decrease variance and makes rejects more meaningful.

[eMiz0r]

Still the rejectrate is kinda sick low. I've got one GPU that has 2045160 accepted shares and 1920 rejected. That's less than 0,1%... (connected to main server wafflepool.com and living near Amsterdam).

Keep in mind, this is the same for everyone, so your profit won't likely be higher as a result of lower rejects.

Absolutely right, didn't think of that. But (newbie question alert), isn't true that whenever the total pool's rejectionrate is lower (and acceptrate higher) we as a pool have more chance of finding blocks because less hashpower is wasted?

[Bigeyeone]

testing EU server have 10 % more hash then on middle coin, very low reject rate

[qsrab]

Still the rejectrate is kinda sick low. I've got one GPU that has 2045160 accepted shares and 1920 rejected. That's less than 0,1%... (connected to main server wafflepool.com and living near Amsterdam).

Keep in mind, this is the same for everyone, so your profit won't likely be higher as a result of lower rejects.

Absolutely right, didn't think of that. But (newbie question alert), isn't true that whenever the total pool's rejectionrate is lower (and acceptrate higher) we as a pool have more chance of finding blocks because less hashpower is wasted?

It's true. We take a chance to orphan someone else's block that other pools don't take. If it works, extra profit

[smooth]

Re: Removing coins I would keep LTC only because it is a good baseline, stable block chain that will always be there. I would argue that a scrypt switching pool should always guarantee to do no worse than LTC by at least including LTC as an option.

The others I see no issue with removing them.

[phzi]

Absolutely right, didn't think of that. But (newbie question alert), isn't true that whenever the total pool's rejectionrate is lower (and acceptrate higher) we as a pool have more chance of finding blocks because less hashpower is wasted?

Nope.  Some hashpower is still be wasted on mining old blocks - you're just getting share credit for them.

It's true. We take a chance to orphan someone else's block that other pools don't take. If it works, extra profit

Yes and no.  Every pool has this chance, presuming they submit blocks to the network even if they are 1 behind the main chain.  Doesn't matter if you get credited for shares 1 up the chain or not.  For us to have a solid chance to orphan someone else's block as the second submitter, we would have to only build on our own chain (which I presume we don't), and that is provably only beneficial with 30%+ of the network hash rate.  (Read about selfish mining)

Re: Removing coins I would keep LTC only because it is a good baseline, stable block chain that will always be there. I would argue that a scrypt switching pool should always guarantee to do no worse than LTC by at least including LTC as an option.

The others I see no issue with removing them.

I would say having LTC on the profitability chart is good... but since difficulty changes so rarely, maybe pull the daemon and  don't have it in the switching rotation.  LTC is probably one of the heavier daemons too, since the spend volume high, so a good one to pull.

[poolwaffle]

The BTC per mhash is lower than if we mined litecoin directly! Looks like a real orphan problem (maybe somethign else too?. Instead of removing coins like fastcoin, just adjust for orphans

I think your math is wrong somewhere.  According to my calcs, mining litecoin directly nets you 0.0074 BTC/day?  And thats at nearly triple the variance of dogecoin...  Did I miss something?

Like the idea of removing worthless coins.

Can you do something about the big exchange problem at the moment?
More then 85% is unexchanged.

Theres something odd with our block processor (might have started sometime last night).  Working on fixing it now, but looks to be something odd with processing casinocoin (keeps processing the same block over and over).

[qsrab]

litecoin difficulty went up between my post and yours. wafflepool profitability also went up.

Did you read my stuff about how you are calculating bitcoin/mhash? I think it might underestimate when the hashrate is going up and overestimate when it is declining

[poolwaffle]

litecoin difficulty went up between my post and yours. wafflepool profitability also went up.

Did you read my stuff about how you are calculating bitcoin/mhash? I think it might underestimate when the hashrate is going up and overestimate when it is declining

Didn't see the LTC difficulty change

As for the overestimate/under, I think its the other way around.  Its actual btc / average hashrate, btc should be correct (actual amount), but if the hashrate at this instant is higher than the average over 24 hours (growing pool), the btc/hashrate would be high (divisor is a bit lower than actual hashrate) = overestimated value.

The issue is, there isn't a great way to display this as far as I can tell (I'm open to suggestions).  Doing it with current hashrate gets stupid skewed when the hashrate jumps around (+-10% every few minutes), and when the pool has an issue (hopefully not again), but if the hashrate drops 30%, the btc/day jumps by 30%.  Average over 24 hours seems like a long enough time to smooth it out, and a short enough time to still be relevant.

[rallasnackbar]

I think your math is wrong somewhere.  According to my calcs, mining litecoin directly nets you 0.0074 BTC/day?  And thats at nearly triple the variance of dogecoin...  Did I miss something?

You are correct, litecoin is SHIT compared to alot of other coins. Its just litecoin fanboys that try to get your hashing power over.



Is it possible to convert the majority of coins before payout? I missed todays pay out limit 0.01 with 0.0005

[phzi]

Theres something odd with our block processor (might have started sometime last night).  Working on fixing it now, but looks to be something odd with processing casinocoin (keeps processing the same block over and over).

I presume that means the casinocoin balances are higher then actually?  Not quite clear what direction this means the balances are going to go for the day.  It did seem a bit crazy when I saw almost .1BTC in unexchanged casinocoins on my account, but I thought we might just be having a good day.

[poolwaffle]

Theres something odd with our block processor (might have started sometime last night).  Working on fixing it now, but looks to be something odd with processing casinocoin (keeps processing the same block over and over).

I presume that means the casinocoin balances are higher then actually?  Not quite clear what direction this means the balances are going to go for the day.  It did seem a bit crazy when I saw almost .1BTC in unexchanged casinocoins on my account, but I thought we might just be having a good day.

Yep, that means casinocoin (99% of it), and alphacoin (1%).  I've got a warning up on the top of the site, and am working on a script to reprocess those blocks and clear out and incorrect earnings.

For some reason, a hash was inserted incorrectly, and caused a casinocoin block to go back and forth between orphan --> confirmed --> orphan --> confirmed --> repeat.  This was caused by a loop in lookups essentially.  Since orphaned transactions don't have associated block hashes, we check our successful shares table to find the hash (for our presentation layer).  For some reason two coinbase transactions got reverse hashes.  So hash1 --> txn2, and hash2 --> txn1.  One was orphaned, one was valid, and they kept swapping their status in the db.  I've added safeguards to prevent this from happening (stops processing that block and alerts for now, so I can see if it ever happens again)

It should be pretty straightforward to go through the earnings log and reprocess that block out, just takes a bit to write the script.  Definitely will be done before payouts though!

[poolwaffle]

On a positive sidenote, I'm pretty confident that the earnings table for BTC/day/MHs is still correct (or at least _extremely_ close) and won't change by more than a few percent when the alpha/casino thing is cleaned up.

Also, has anyone had any trouble with the new stratum endpoints?  I've added them to the homepage so we can get a few more users moved over to them, but I haven't seen anything yet in this thread about problems

[Daltonganger]

Hope to see the actual balances on my page before sleeping (have 1 hour left - It's late in Amsterdam).

EU pool is good, and no problems ! Let's set Vardiff's .

Hope the 3 updates you posted before, are implemented in the coming day !

Have to say again: Love the pool, great job!

Greets,

Daltonganger

[phzi]

Also, has anyone had any trouble with the new stratum endpoints?  I've added them to the homepage so we can get a few more users moved over to them, but I haven't seen anything yet in this thread about problems

uswest has been rock stable for me so far.  Seeing a higher reject rates then before tho - over 3% right now.

[Daltonganger]

Also, has anyone had any trouble with the new stratum endpoints?  I've added them to the homepage so we can get a few more users moved over to them, but I haven't seen anything yet in this thread about problems

uswest has been rock stable for me so far.  Seeing a higher reject rates then before tho - over 3% right now.

Strange, EU is getting me 0,1% only (lower then before).

Maybe it's that I'm on the same network as the server...

[phzi]

Maybe it's that I'm on the same network as the server...

That would definitely help, heh.  My rejects all seem to be because of vardiff switches, and rare cases of 2 blocks found within seconds of each other.

I just dropped intensity a bit and am seem to be getting less rejects now.  But it's weird, because wafflepool used to give me under 0.5% reject rate with these same settings.  Slight config changes I suspect, making lower intensity a better bet.

[jimlite]

Keep litecoin.  There are many times when the whole alt coin market just
goes to crap and mining litecoin IS the most profitable coin.  Switchercoin
mines alts and litecoin (and pays out in litecoin), and I have seen them
mining litecoin on occasion when everything else is going down the tubes.

[LPCobris]

Hi Guys!

I have been reading the posts and the replys of the Operator of the pool.
I might say im impressed with his support on the questions and adding / fixing stuff to the pool.

I have currently a mini-farm pointed to MiddleCoin with a good success rate of earnings.
What can i expect if i move my operation to this pool?

How are the earnings currently?

I like this kind of support, and a much better and fair fee.

Thanks in advance...

LPC

[phzi]

I have currently a mini-farm pointed to MiddleCoin with a good success rate of earnings.
What can i expect if i move my operation to this pool?

How are the earnings currently?

I have consistently had comparable or better earnings from this pool.  Wafflepool has higher variance to some extent (one day a little lower, one day higher), but it has overall been a much better experience then middlecoin for me.  And when I ran side-by-side tests, I was pleased with the earnings here.

I just dropped intensity a bit and am seem to be getting less rejects now.  But it's weird, because wafflepool used to give me under 0.5% reject rate with these same settings.  Slight config changes I suspect, making lower intensity a better bet.

Looks like I spoke too soon.  Poolwaffle: something is borked here.

I just saw basically this scroll by:

Accepted share diff xx/32
Accepted share diff xx/32
Accepted share diff xx/32
Rejected share diff xx/32 ... (Share is above target)
Rejected share diff xx/32 ... (Share is above target)
Accepted share diff xx/32
Accepted share diff xx/32
Rejected share diff xx/32 ... (Share is above target)
Accepted share diff xx/32
Accepted share diff xx/32
Accepted share diff xx/32
Rejected share diff xx/32 ... (Share is above target)
Rejected share diff xx/32 ... (Share is above target)
Rejected share diff xx/32 ... (Share is above target)
Accepted share diff xx/32
Accepted share diff xx/32
Accepted share diff xx/32
Accepted share diff xx/32
Accepted share diff xx/32
Accepted share diff xx/32