Yeah. In other words on a pool that may or may not only have 300 workers it means that with auto-switching the pool is making extra hashing power by throwing out the oldest shares.
Think I will pull my workers after a payout and wait for you guys to actually have a couple K of miners.... as I think you are faking the stats. Your api shows a couple hundred workers but your front end shows 1.3K.
Topic: 🔥🔥🔥Blazepool on FIRE🔥180+ coins🔥well established🔥multi-algo switching pool - page 18. (Read 20749 times)
February 11, 2018, 09:52:06 PM
February 11, 2018, 08:20:13 PM
@MagicSmoker You're absolutely right! For "any given miner" should include all of our loyal fans as well! Because no users would want to have some other users leave the pool prematurely and still rip the benefit of their hashrates. 
And yes there are a little bit of fluctuations based on "some" luck too, but in the medium term everything evens out.
And yes there are a little bit of fluctuations based on "some" luck too, but in the medium term everything evens out. 
February 11, 2018, 08:11:04 PM
@MagicSmoker Your description fits a wrong implementation of PPLNS, but not PPLNS itself.
Just quoting from the earlier reference: https://bitcointalksearch.org/topic/pplns-39832
"Another incorrect implementation is to pay all shares in a window given in units of time (sometimes called PPLNM or PPLNH)"
Just quoting from the earlier reference: https://bitcointalksearch.org/topic/pplns-39832
"Another incorrect implementation is to pay all shares in a window given in units of time (sometimes called PPLNM or PPLNH)"
Not quite... If pool hashrate is fairly constant but pool luck is not - ie, the time to find each block varies quite a bit - then any given miner will submit way more than n shares for a block that took much longer than average to find; ergo, the oldest shares end up get tossed out because they were outside of the n-wide window.
February 11, 2018, 07:28:59 PM
@MagicSmoker Your description fits a wrong implementation of PPLNS, but not PPLNS itself.
Just quoting from the earlier reference: https://bitcointalksearch.org/topic/pplns-39832
"Another incorrect implementation is to pay all shares in a window given in units of time (sometimes called PPLNM or PPLNH)"
Just quoting from the earlier reference: https://bitcointalksearch.org/topic/pplns-39832
"Another incorrect implementation is to pay all shares in a window given in units of time (sometimes called PPLNM or PPLNH)"
February 11, 2018, 06:58:51 PM
@puch0021 Right! It's PPLNS like many AutoExchange pools. Cheers! 
Uh-huh, so what happens if the time to find each block varies wildly and routinely exceeds several hours? Doesn't that result in the oldest shares submitted by the miners getting tossed out as worthless?
February 11, 2018, 06:43:32 PM
@puch0021 Right! It's PPLNS like many AutoExchange pools. Cheers!
February 11, 2018, 06:34:02 PM
@gak_45 It seems like you might have some misunderstanding of how a pool works and how different kind of share counting system works. We're happy to provide some reference materials for you.
https://bitcointalksearch.org/topic/pplns-39832
https://en.bitcoin.it/wiki/Comparison_of_mining_pools
https://bitcointalksearch.org/topic/pplns-39832
https://en.bitcoin.it/wiki/Comparison_of_mining_pools
So what is the payout system used at blazepool?
February 11, 2018, 05:52:21 PM
@gak_45 It seems like you might have some misunderstanding of how a pool works and how different kind of share counting system works. We're happy to provide some reference materials for you.
https://bitcointalksearch.org/topic/pplns-39832
https://en.bitcoin.it/wiki/Comparison_of_mining_pools
https://bitcointalksearch.org/topic/pplns-39832
https://en.bitcoin.it/wiki/Comparison_of_mining_pools
February 11, 2018, 05:34:25 PM
Is the pool PPLNS, PPLNS+, or pay per valid share? Hope it is the latter as PPLNS is IMHO a scam to rob hashs by pool owners.
February 11, 2018, 08:15:14 AM
It's great to let everyone know that Blazepool is running at 100% uptime since launch and we do everything to stay as close to that as possible.
February 11, 2018, 07:55:18 AM
February 11, 2018, 07:14:05 AM
Pool again down ...
February 10, 2018, 05:31:14 PM
@gak_45 Thanks for sticking around to see this pool grow. In fact, we've had a little better luck overall these couple of days compared to the first day we launched.
February 10, 2018, 04:12:50 PM
I am currently running one of my small rigs on the pool... and when you take your 1K worth of rigs off line the profits tank - about 25% less than Ahash. Will you be doing more 'maintenance' in the near future... or are they now online for good? I ask because either you were doing maint on 1K worth of GPUs or you are faking your stats - badly. Willing to stick around and see which way it IS, but only if you guys guarantee to keep the pool at BARE MINIMUM miner levels needed to win blocks.
February 10, 2018, 02:39:15 PM
@newgameos thanks for your continuous support! Payment scheduled in under 12 hours from now.
February 10, 2018, 11:53:34 AM
Another 24h of testing - profitability went down a little (5%) - so it might be just pool luck. Staying for another day (should make payment threshold - so will see if payments are fine)
February 10, 2018, 11:21:00 AM
Good job guy! Awaiting Litecoin integration
February 10, 2018, 10:59:29 AM
@robl450 Our designer: Done.
February 10, 2018, 10:15:23 AM
Could you please change the wallet page so that the balances are copy and paste-able? I put them in excel every day and this is the only pool that I can't copy the balance.
February 10, 2018, 10:10:34 AM
@Max3k Thank you for supporting us and spending time with our front end! Good eyes on catching maintenance for our own rig farms causing rig numbers to fluctuate! We are already quite pleased with the 200+ sign up in the first 2 days of the pool. As for your balance not growing, please send us your btc address in PM and we'll figure it out for you. A typical single 1080Ti card made about 0.0005 per day over the last 2 days.
For the 1's and 2's you see on the screenshot, it is intended to avoid a sniffdog check when NOT API hashrate > 0, sniffdog totally stops mining a particular algo.
For the 1's and 2's you see on the screenshot, it is intended to avoid a sniffdog check when NOT API hashrate > 0, sniffdog totally stops mining a particular algo.
Jump to: