█▓▒░-< [ZPOOL.CA][BTC Multipool] The miners multipool >-░▒▓█ Paid 925+ BTC

[unforsaken2k1]

The first value is the the actual profitability in the LAST 24 hours and the other is the estimated profitability in the NEXT 24 hours...

So the website is only listing the actual previous 24, and miner control is pulling the next 24 estimate?

[AngryDwarf]

The first value is the the actual profitability in the LAST 24 hours and the other is the estimated profitability in the NEXT 24 hours...

So the website is only listing the actual previous 24, and miner control is pulling the next 24 estimate?

Sounds like it. Current profitability is a function of current difficulty, block reward and market price. By the time the coin has matured and been exchanged the actual value might be more or less then what was predicted. As some coins have fast difficulty adjustments and fluctuating market prices, 24 hour estimates and the actual earnings may vary considerably.

[crackfoo]

Updates are underway. Servers have all been migrated to bigger and better hardware and now serving from multiple servers.

New algo c11 added and ChainCoin

Added algos myr-gr and groestl back to the mix

New scrypt coins:

CryptoEscudo, Sexcoin, Saffron, Mars, Bitmark, Guarany, Beaver,

New sha coins:

Crown, Saffron, UniversalCurrency, Californium, BitPound, Vcoin

New x11 coins:

Saffron, Adz, Mind, Bantam, Creva

We'll be added the blake algo today as well.

Cheers!

[AngryDwarf]

Thanks for the return of some old algos and the addition of some new ones. Luckily my GTX680/ccminer1.7 combo can take advantage of all but neoscrypt, and the new c11 algo seems rather profitable at the moment. Unfortunately the R7260X/win10 driver/sgminer 5.2.1 combo only likes X11/X13/Lyra2v2, and so is pretty much an X11 only miner. I use an optimised core i7 avx cpu miner which is pretty good at x11 mining. Does any one know of a decent multi algo CPU miner? cpuminer-multi-rel1.2 has extremely poor performance.

[crackfoo]

New algo, Blake is now online with BlakeCoin (BLC) and Saffron (SFR). Still searching for some Dirac (XDQ) nodes then I will merge mine this on the Blake port.

Cheers!

[BlueDragon747]

New algo, Blake is now online with BlakeCoin (BLC) and Saffron (SFR). Still searching for some Dirac (XDQ) nodes then I will merge mine this on the Blake port.

Cheers!

BlakeCoin (BLC) uses 8 round Blake-256

Saffron (SFR) uses 14 round Blake-256

so they will not merge also they have other bits different in the serialization!

you can merge with BlakeCoin (BLC):
Photon (PHO)
BlakeBitcoin (BBTC)
Electron (ELT)
Universalmolecule (UMO)
Lithium (LIT)
Dirac (XDQ) assuming its not DEAD as the "dev" does not support "his" coin with nodes or maintenance!

[crackfoo]

New algo, Blake is now online with BlakeCoin (BLC) and Saffron (SFR). Still searching for some Dirac (XDQ) nodes then I will merge mine this on the Blake port.

Cheers!

BlakeCoin (BLC) uses 8 round Blake-256

Saffron (SFR) uses 14 round Blake-256

so they will not merge also they have other bits different in the serialization!

you can merge with BlakeCoin (BLC):
Photon (PHO)
BlakeBitcoin (BBTC)
Electron (ELT)
Universalmolecule (UMO)
Lithium (LIT)
Dirac (XDQ) assuming its not DEAD as the "dev" does not support "his" coin with nodes or maintenance!

Thanks for the FYI!

[spydud22]

How would you feel about adding Nyancoin to the Scrypt pools? I'd throw an asic or two your way.

[crackfoo]

How would you feel about adding Nyancoin to the Scrypt pools? I'd throw an asic or two your way.

Which exchanges is it on?

[AngryDwarf]

How would you feel about adding Nyancoin to the Scrypt pools? I'd throw an asic or two your way.

Which exchanges is it on?

http://coinmarketcap.com/currencies/nyancoin/#markets

[crackfoo]

How would you feel about adding Nyancoin to the Scrypt pools? I'd throw an asic or two your way.

Which exchanges is it on?

http://coinmarketcap.com/currencies/nyancoin/#markets

ahh yes, we don't use cryptopia. haven't developed the api script to do the trading yet.

[AngryDwarf]

Thanks for adding X15 algo!

On the site multi algo page there is instructions for setting up NVIDIA/ccminer cards. It could do with adding an AMD/sgminer combo. If the conf below looks good, you could use it as an example. Also, there should be instructions for normalising algos to the card, which is worthwhile doing as card algo outputs can vary considerably. I think the way to do this is to determine the hash rate of each algo for the card, and then normalise it to another algo (e.g. scrypt output). If algo output is 1000 kH/s and scrypt output is 100 kH/s, then algo normalisation factor is 1000/100 = 10. (Note: use the hash rate reported by the miner, rather than the 5 min 'luck' based hash rate reported on the site by share submissions. This figure will vary more than the miner hash rate)

The below conf example I have used on sgminer 5.2.1. On default failover, add most used algos to the top of the list, or set up round-robin failover instead. Note intensity, thread-concurrency factors also need to be set appropriate to the card. AMD/sgminer needs quite a lot of fine tuning.

{
    "pools" : [
         {
              "name" : "X11",
              "url" : "stratum+tcp://mine.zpool.ca:3533",
              "user" : "myAddress",
              "pass" : "c=BTC,x11=10.4,x13=5.7,x15=5.1,lyra2v2=8.7",
              "algorithm" : "X11",
              "intensity" : "20",
              "thread-concurrency" : "8000"
         },
         {
              "name" : "X13",
              "url" : "stratum+tcp://mine.zpool.ca:3633",
              "user" : "myAddress",
              "pass" : "c=BTC,x11=10.4,x13=5.7,x15=5.1,lyra2v2=8.7",
              "algorithm" : "X13",
              "intensity" : "20",
              "thread-concurrency" : "8000"
         },
         {
              "name" : "X15",
              "url" : "stratum+tcp://mine.zpool.ca:3733",
              "user" : "myAddress",
              "pass" : "c=BTC,x11=10.4,x13=5.7,x15=5.1,lyra2v2=8.7",
              "algorithm" : "X15",
              "intensity" : "20",
              "thread-concurrency" : "8000"
         },
         {
              "name" : "Lyra2v2",
              "url" : "stratum+tcp://mine.zpool.ca:4533",
              "user" : "myAddress",
              "pass" : "c=BTC,x11=10.4,x13=5.7,x15=5.1,lyra2v2=8.7",
              "algorithm" : "lyra2v2",
              "intensity" : "18",
              "thread-concurrency" : "8000"
         }
    ]
}

[crackfoo]

thanks for this! I have emails all the time asking how best to setup their miners, but I've only ever used ASIC's so this is a big help.

Cheers!

[AngryDwarf]

I'd mined some DASH a few days ago before it went red and had a few payments without txId's which seemed to go missing. So I recently mined some more DASH and thankfully got a second combined payment of the missing DASH with the next DASH payment. Hopefully this is an area that can be improved in the future as it is bewildering to the uninitiated. Feel free to keep adding more algos and coins first though, the new ones are working well.

It makes me wonder if one of the new scrypt coins has an extreme yoyo difficulty adjustment. I've found my GPU' switching to scrypt now which is rather unprofitable if the yoyo coin drops quickly in profitability. I might be best disabling scrypt in my miner configuration. What is the minimum time limit that an algo is mined for before checking for the next best algo? Obviously if it is too low, then hashes are lost whist algo switching. If too high, a yoyo coin might put me on an unprofitable algo for too long.

[AngryDwarf]

Or alternatively, is there a maximum length to the password string that is confusing the switch to scrypt? (which really is ASIC territory)

my password string looks like this.
d=XXXXX,c=BTC,x11=8.7,x13=6.7,x15=6.1,c11=8.7,qubit=15.0,quark=12.3,lyra2v2=3.8,groestl=23.9,blake=624.5,blakecoin=978.7,myr-gr=42.2,scrypt=1

[AngryDwarf]

The other thing I have noticed, is once the GPU has switched to scrypt, it never seems to switch off it. Restarting the script and it chooses another algortihm. I think I will disable it for now.

[JaredKaragen]

The other thing I have noticed, is once the GPU has switched to scrypt, it never seems to switch off it. Restarting the script and it chooses another algortihm. I think I will disable it for now.

for my this happens on Lyra2Re....  So I either choose to run Lyra, or not depending on how well the last half day has been.

[AngryDwarf]

The other thing I have noticed, is once the GPU has switched to scrypt, it never seems to switch off it. Restarting the script and it chooses another algortihm. I think I will disable it for now.

for my this happens on Lyra2Re....  So I either choose to run Lyra, or not depending on how well the last half day has been.

Interesting, is that an NVIDIA card? My NVIDIA card has never auto switched to Lyra2v2 as it is not very good on that algo. The less powerful AMD card I have is quicker at Lyra2v2, and whilst it rarely switches to it, it has switched off it.

[crackfoo]

Or alternatively, is there a maximum length to the password string that is confusing the switch to scrypt? (which really is ASIC territory)

my password string looks like this.
d=XXXXX,c=BTC,x11=8.7,x13=6.7,x15=6.1,c11=8.7,qubit=15.0,quark=12.3,lyra2v2=3.8,groestl=23.9,blake=624.5,blakecoin=978.7,myr-gr=42.2,scrypt=1

AFAIK, it should allow up to 1024... so still a ways to go for this passwd even

[crackfoo]

I'd mined some DASH a few days ago before it went red and had a few payments without txId's which seemed to go missing. So I recently mined some more DASH and thankfully got a second combined payment of the missing DASH with the next DASH payment. Hopefully this is an area that can be improved in the future as it is bewildering to the uninitiated. Feel free to keep adding more algos and coins first though, the new ones are working well.

It makes me wonder if one of the new scrypt coins has an extreme yoyo difficulty adjustment. I've found my GPU' switching to scrypt now which is rather unprofitable if the yoyo coin drops quickly in profitability. I might be best disabling scrypt in my miner configuration. What is the minimum time limit that an algo is mined for before checking for the next best algo? Obviously if it is too low, then hashes are lost whist algo switching. If too high, a yoyo coin might put me on an unprofitable algo for too long.

Yes, the system is designed to double check previous payments to detect ones that have failed and re-do them so this is what you're seeing.

diff is one factor but so is exchange activity. Some day I'll try and get into the code that does that and see if it can be improved.