|
@alexcostabrito. Very slight drop of earnings does happen with orphans. Normal orphans do happen regularly but not frequently, just the nature of the mining business. What we don't want to see are large amount of orphans happening due to chain splits.
|
|
|
|
|
Hello everyone,
It's great to see a little discussion going on about algos. Currently all algos are working great! We haven't disabled any algo, but one should tailor their bat file for activated algos based on your GPU types and combination in a rig. Each GPU performs differently on different algo hence there's no set rule on which algo combination works the best for your particular group of cards. Reposting one of our earlier suggestion:
"What I personally do is to have 1 card pointing at all algo and let the algorithms drive that one completely to determine the best algo list, then I point all my other cards at a selection of about 5-6 algos. I do re-select of algo about weekly."
Everything is dynamic and changes as difficulty changes for all coins across all algos. For example, we posted an example single 1080Ti rig that did great on Monday for 24hr, netting around 0.0006BTC for the algo selection. The same machine with the same algos list did only 0.00042 in the past 24hrs. Let's see what it does in the next 24hrs.
|
|
|
|
|
@Max3k The test rig was a very simple one: Old Dell computer with Core2Duo6300, 4G of Generic Ram, 1x EVGA 1080Ti FTW3 at stock clock 65%TDP. Activated Algos were: neoscrypt, xevan, blake2s, phi, x17, sib, lyra2v2, nist5, skein. Of course anytime with data like these, luck plays a factor and 24 hour test is way to short to tell true stories of long running averages.
@JukNi The "cold room" explains the low temp. What's your average x17 hashrate? Should be in the 40-50MH/s for the 2x 1080ti, are you seeing these values?
|
|
|
|
|
@JukNi you have really cold ambient temp for your rig and open frame? Reason I'm asking is those temps looks low if you're not running really high fans for 1080Ti @100% TDP. And from the low returns you got, there's a chance of constant thermal throttling.
|
|
|
|
|
@JukNi. Curious, what are the temps of the GPUs?
|
|
|
|
|
@JukNi. Thank you very much for trying out Blazepool. The return that you got on your account is definitely NOT typical of a 2x1080Ti rig. For example, with a single 1080Ti at stock at 65% TDP, one should get around 0.0005 to 0.0006 in the past 24hrs with some typical selection of algos. Maybe you can post your bat file for troubleshooting here or seek faster response from our Discord.
|
|
|
|
|
@romajc I think i've seen an online app in the mining forum here that makes use of the api and does the tracking for you. Let me try to find it. Will update the post.
Update 1 ... haven't been able to locate that thread so far... keep trying...
|
|
|
|
|
@romajc in that case it sounds like a corrupted data file in the stats folder for that machine only. You may remove the ccminer stats file for neoscrypt and it should bench and run again fine. Not the first time we see this happening. Thanks for using Blazepool.
|
|
|
|
|
@jphope1234. Thanks for trying the pool out. If you are on 13 algos the first 2 hours or so was used by the benchmarking of nemos. You'll find better return once everything settled. In our tests, interval of 300 seconds is a great choice for 6 1080ti rig. I'd further recommend reducing some algo, for 1080ti , I'd remove timetravel, hmq1725, hsr, bitcore, groestl, lbry. This list changes as time goes by. What I personally do is to have 1 card pointing at all algo and let the algorithms drive that one completely to determine the best algo list, then I point all my other cards at a selection of about 5-6 algos. I do re-select of algo about weekly.
|
|
|
|
|
@romajc. That's a multiplier issue that can be fixed by downloading the latest master from our nemosminer fork. We'll update the release to reflect the change shortly. In the meantime, please use the latest files from master. Thanks!
|
|
|
|
|
@Bit2017User. Thank you for trying the pool out. It's really great to see you continue with the trial. Neoscrypt coin weren't particularly strong with our coins line-up until now because of a more balanced approach that we take.
We've just added a few coins to strengthen our lineup: Desire, Shield, Solaris, Tune.
|
|
|
|
|
@Bit2017User. Do you see higher profitability now or did you already quit at only 55 minutes?
@jphope1234. You don't lose shares for algo switching.
|
|
|
|
|
Hello everyone,
Wallet page back online!
Blazepool
|
|
|
|
|
Hello All,
Wallet page is down for a short while, will be right back up. Mining is not disturbed.
Blazepool
|
|
|
|
Hello everyone. Small update here. We released the wallet API for those of you automating your accounting. You may find the API section now on our main page. http://www.blazepool.com/More to come shortly including new coin additions. Blazepool |
|
|
|
|
@tio Immature is when a block hash with high enough difficulty is found by the pool, accepted by the nodes and now waiting for confirmation. Confirmation count depends on the specific coin's setup.
|
|
|
|
@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. |
|
|
|
@MagicSmoker Your description fits a wrong implementation of PPLNS, but not PPLNS itself. Just quoting from the earlier reference: https://bitcointalk.org/index.php?topic=39832"Another incorrect implementation is to pay all shares in a window given in units of time (sometimes called PPLNM or PPLNH)" |
|
|
|
@puch0021 Right! It's PPLNS like many AutoExchange pools. Cheers!  |
|
|
|
|
Show Posts
