Topic: ▂▃▅▆▇⫷[ 🆉🅿🅾🅾🅻.🅲🅰 ]⫸⫷[!KAWPOW!]⫸⫷[ the miners multipool ]⫸ ▇▆▅▃▂ - page 51. (Read 279601 times)

You probably won't lose all of your earnings by switching before a block is found, but you'll likely lose some if the time to find the next block takes a lot longer than average and the pool uses "PPLNS" scheme. I wrote a fairly long post about the potential downsides to PPLNS in another thread: https://bitcointalksearch.org/topic/m.30133809 which hasn't been commented on so beware of any potential errors on my part.

EDIT - Zpool uses the Proportional payout scheme, not PPLNS, so the above comment is irrelevant.

Guys i have a question and ill be happy if someone answer it.

Right now im mining Bitcore but the block find time is very big ( like 1-2 hours).

So lets say my rigs are mining bitcore and then before the block is found they move to another coin that is more profitable by the program my whole progress is lost with the time mining on Bitcore right ?

Or im missing something.?

Yes, I already show my bat.
use address DNR with option C=DNR, mining DNR, but got paid in DGB so I think something wrong.
No problem in other pool.

https://23.imgtrue.com/DNRDGBe60793f44f09de45.png

Yes, just to reiterate what JaredKaragen wrote, you can pick the algo to mine and you can pick the coin to get paid in, but you can't pick a specific coin to mine. It's a subtle, but important, distinction.

You mine on an algo.  Stratum picks the coin.

You only pick what you get paid in; via the c=XXX flag and the username being the wallet of that type...

if your password is trying to get paid in DNR, and you are getting DGB;  have crackfoo fix it for you.... but it sounds like you are trying to pick what coin you mine;  which this is not how the pool works.

Could you please answer me ?
Can I mine DNR here, or just only BTC ?
(Latest status : DGB paided ... to ...)

Regards

take a look at the main page of zpool.ca and the algo switching section.

its by means of the password;  and setting your miner app to not retry any connections;  and looping them in a batch file to keep trying as the connections get dropped.  Also;  don't forget to normalize or you won't mine what's most profitable for your card.  Instructions to normalize are in the same link mentioned below; it will be in one of the older batch threads.


I also have a series of batch files linked in my sig for controlling the profit switching/algo manually, or automatically.

It's back to correct estimates now

Ah... Well it would be fun if there's a counter for that too ..... ;-)

"Hi need a little help with multi Algo mining setup. I use zpool the template setup below is for windows . I just want to switch between blake2s and lyra2v2 whichever is most profitable. I have 2 commands in been using to switch manually
./ccminer -x64 -a lyra2v2 -o stratum+tcp://lyra2v2.mine.zpool.ca:4533 -u walletaddress -p c=XSH
./ccminer -x64 -a blake2s -o stratum+tcp://blake2s.mine.zpool.ca:5766 -u walletaddress -p c=XSH

how could i merge these two into choosing between the 2 algos? scratching my head a little im using ubuntu and ccminer"

The timer isn't for BTC payouts. BTC payouts I run at different times, manually.

Hello Zpool/Crackfoo ,

Just had my balance past at 0.01 btc, and didnt get a payment, after i watched the countdown...
http://www.zpool.ca/?address=1Ev698UrUTL52wyrdRfRK25BfjXaA7YDWd

Will wait trough though next payout schedule 3:53  remaining ...

Regards,

DS-M/Sander o7

No to ahashpool because the 0.01 BTC minimum payout is too high when all you got to test it is a single GTX 1080 (about 30 days to reach 0.01 BTC). Also, I am in the US and ahashpool is in Asia so probably not the best ping times (don't know because ahashpool.com is not pingable).

I already did a comparison of NemosMiner/MiningPoolHub vs. NiceHash and NH won that round by about 10%: https://bitcointalksearch.org/topic/m.29417942

Since Zpool is on the same track as MPH and BTC price isn't plummeting every day like it was when I tested MPH, I am leaning heavily towards blaming the auto-switching algo and/or how profitability is estimated. For example, during the current test of Zpool the top algo - whatever it may be - is always projected to earn at least 0.450 mBTC per day, whereas NH is holding fairly steady at around 0.300 mBTC per day.

It was because I was expecting this type of result that I wanted to mine a single algo and convert to a coin on Zpool first so I could get a good feel for any "slippage" that might be occurring, and as I already reported there wasn't any (not that my testing was exhaustive, but still, some testing is better than none at all).

Thanks. Can you do the same at ahashpool and miningpoolhub please?

Yes, NiceHash and NemosMiner/Zpool are running concurrently on separate rigs that have been matched very closely on one particular algo (Equihash). I didn't check every algo exhaustively, but I can tell you that Neoscrypt runs at the same speed on both cards as well.

How is it even possible to measure, unless you have two identical cards at identical speeds? running at the same time?

Anything up with X17 I am not seeing hash rate on the site but my miners are still working?  It also not paid out for over 5 hours?

Awesomeminer also shows me $152/day.
Must be a bug, because I'm mining on zpool from 3 hrs and the results are not as I would get $152/day.

A quick update after the first 24 hours of running - NiceHash is currently ahead with 0.33331 mBTC earned vs. 0.29274 mBTC immature + earned at Zpool.

The two rigs I have set up for doing these kinds of tests consist of a single GTX 1080 that I have tuned to deliver the same  Sols/s (+/0 0.5) in Equihash. The algos I have selected in NemosMiner for Zpool are:

poly,hsr,keccak,xevan,skunk,tribus,phi,skein,equihash,groestl,sib,bitcore,x17,blakecoin,Nist5,MyriadGroestl,Lyra2RE2,neoscrypt,blake2s,lyra2z

Other settings in the NemosMiner bat file are to check profitability every 60 seconds (-interval 60) and switch algos at 5% difference in profitability (-ActiveMinerGainPct 5).

For NiceHash I have all of the single algos selected except for a few that I know have been ASIC'ed: keccak, nist5, neoscrypt, Lyra2rev2, DaggerHashimoto, Cryptonight, Equihash, Pascal, Blake2s. Oops, looks like I left Pascal enabled, even though it has been ASIC'ed... Oh well, can't change it now without invalidating the test.

One other update - I got credited for 1.5 more XVG in my earlier test so that brought the total up to 52.5 actual vs. 53 predicted; again, not the most scientific of tests, since one is mining multiple coins with a single algo, then converting everything mined to one of those coins, but you really can't complain if you get exactly the amount of coin your hashrate and average difficulty predict.*


* - I am well aware that this is not a terribly accurate means of evaluating the performance of a pool or miner, but there simply isn't any other way to do it when switching coins, much less switching algos.

Perhaps then we should take a look, for a SQL-replica server? Had to build those as well in my time as systems-engineer.
Anyway thanks for updating !