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

[tbearhere]

i'm still sure skeincoin should be removed from zpool completely

ax66 why does it drain our profits  like mining DECRED on multi switching?  thx

[scryptr]

i'm still sure skeincoin should be removed from zpool completely

ax66 why does it drain our profits  like mining DECRED on multi switching?  thx

TEN MINUTES AGO IT WAS BEST PRICE--

It needs a high intensity setting.       --scryptr

[JaredKaragen]

This is exactly why you can't take the reject and share rewards at face value.   Its something with the web-frontend display code;  not with the share or exchange percentage coding....

You can see the inconsistencies across the board.

So if you see this sort of thing;  please understand it's not loosing profits, it's the part of the pool that calculates each value to display to you that has an issue.

Hopefully these vales will help getting down to the cause of where the fault(s) are...   And I am wondering if any other pools using this interface/code are seeing the same type of issues....

[Epsylon3]

about reject %, it doesnt affect the percent... all rejected shares are just ignored... the percent of reject is wrong because it assume each reject diff was "1", will try to improve that

to resume the pool share % is all <valid shares> x <stratum diff when submitted>

all users results are then summed (per coin or algo) and the % is the user part

[jkminkov]

i'm still sure skeincoin should be removed from zpool completely

if you don't like it, drop it from your config...

[JaredKaragen]

impossible, it's pool config, not miner, only op can add or remove a coin.
yesterday i "weakened" it by raising diff, coz i needed to mine a bit on skein pool,
but that's boring..

its simple to not mine on an algo.  do not include it in the password string, and/or your miner app config.  The pool has no control over that.

[pallas]

impossible, it's pool config, not miner, only op can add or remove a coin.
yesterday i "weakened" it by raising diff, coz i needed to mine a bit on skein pool,
but that's boring..

its simple to not mine on an algo.  do not include it in the password string, and/or your miner app config.  The pool has no control over that.

I think he's saying he doesn't want to mine a coin, not an algo.

[JaredKaragen]

impossible, it's pool config, not miner, only op can add or remove a coin.
yesterday i "weakened" it by raising diff, coz i needed to mine a bit on skein pool,
but that's boring..

its simple to not mine on an algo.  do not include it in the password string, and/or your miner app config.  The pool has no control over that.

if you mine for some btc profit - maybe, but my goal was different, i needed this very skein pool,
but without low-diff shit like skc

you are not understanding how it all works if you are thinking that way....

To me it's just not a profitable algo for algo-switching at higher freq so I don't use it anymore, same with decred which is too slow of a coin for it as well.

I have noticed that lower hashrate connections get put on higher diff coins;  and that low diff coins are almost strictly mined by lower hashrate connections.... That's the tendency anyways.   The only low diff coins my high hashrate connections have mined have been high diff coins; except for merge-mined coins which are just taking a low diff share from a higher diff coin and submitting it with the lower diff coin.

Market fluctuations in coin prices greatly effect whats profitable as well.  Just cause it was profitable and the miner switched to it;  a dump can cause an odd lack in profit when exchanged.  Then again, there have been some crazy exchange rates in the past with select coins at random events.  People doing pump and dumps.


Point is:  The low diff coins aren't wasting hash.  AFAIK the pool is properly using each miner connection on an as-needed per-miner basis....   It would be wasteful to put a high hash miner on a low diff coin and vice versa.

Maybe crackfoo can clarify if he knows;  but he didn't write the pool code;  he's more on the coinbox config and such side of things.... where it really matters.

[scryptr]

impossible, it's pool config, not miner, only op can add or remove a coin.
yesterday i "weakened" it by raising diff, coz i needed to mine a bit on skein pool,
but that's boring..

its simple to not mine on an algo.  do not include it in the password string, and/or your miner app config.  The pool has no control over that.

if you mine for some btc profit - maybe, but my goal was different, i needed this very skein pool,
but without low-diff shit like skc

you are not understanding how it all works if you are thinking that way....

To me it's just not a profitable algo for algo-switching at higher freq so I don't use it anymore, same with decred which is too slow of a coin for it as well.

I have noticed that lower hashrate connections get put on higher diff coins;  and that low diff coins are almost strictly mined by lower hashrate connections.... That's the tendency anyways.   The only low diff coins my high hashrate connections have mined have been high diff coins; except for merge-mined coins which are just taking a low diff share from a higher diff coin and submitting it with the lower diff coin.

Market fluctuations in coin prices greatly effect whats profitable as well.  Just cause it was profitable and the miner switched to it;  a dump can cause an odd lack in profit when exchanged.  Then again, there have been some crazy exchange rates in the past with select coins at random events.  People doing pump and dumps.


Point is:  The low diff coins aren't wasting hash.  AFAIK the pool is properly using each miner connection on an as-needed per-miner basis....   It would be wasteful to put a high hash miner on a low diff coin and vice versa.

Maybe crackfoo can clarify if he knows;  but he didn't write the pool code;  he's more on the coinbox config and such side of things.... where it really matters.

sorry pal, you'r thinking too much  
i needed this skein pool for balancing some shit, but skc was getting in the way, so i removed it
by mining solo and raising diff enuough for the pool not to mine it.
that's all.
and w/o skc it was pretty good little pool lol, so skc better be removed completely

if u need technical - my miner simply switching with all its power to skc for a short period,
than to aur/dgb for much longer period, then again to skc for short and so on,
so it IS wasting, with all that switching mess, and high hashrate over low diff coin

WERE YOU DYNAMICALLY SWITCHING BETWEEN WALLETS? --

I don't understand, you are talking about solo-mining, and pool mining, at the same time.        --scryptr

[scryptr]

WERE YOU DYNAMICALLY SWITCHING BETWEEN WALLETS? --

I don't understand, you are talking about solo-mining, and pool mining, at the same time.        --scryptr

1) mining on skein pool, observing how skc makes a mess with all that switching and too fast blocks.
.. bloody hell
2) mining solo skc to raise its diff so it becomes fairly unprofitable for the pool for some time.
.. crawl back into your hole, slime
3) skein pool again, now it's mining only aur/myr/dgb.
.. everything is fine

ONE MINER SOLO-MINING SKEINCOIN (SKC) MAKES THAT MUCH DIFFERENCE? --

So, your pressure solo-mining SKC was enough to make "the slime" too high in difficulty for the pool to mine?       --scryptr

[AngryDwarf]

ONE MINER SOLO-MINING SKEINCOIN (SKC) MAKES THAT MUCH DIFFERENCE? --
So, your pressure solo-mining SKC was enough to make "the slime" too high in difficulty for the pool to mine?       --scryptr

Yes. Try it yourself. You can raise the diff and watch how zpool starts to throw even more hash on it! Until it becomes unprofitable and the block chain essentially freezes. Same with Xedos.

[tbearhere]

impossible, it's pool config, not miner, only op can add or remove a coin.
yesterday i "weakened" it by raising diff, coz i needed to mine a bit on skein pool,
but that's boring..

its simple to not mine on an algo.  do not include it in the password string, and/or your miner app config.  The pool has no control over that.

if you mine for some btc profit - maybe, but my goal was different, i needed this very skein pool,
but without low-diff shit like skc

you are not understanding how it all works if you are thinking that way....

To me it's just not a profitable algo for algo-switching at higher freq so I don't use it anymore, same with decred which is too slow of a coin for it as well.

I have noticed that lower hashrate connections get put on higher diff coins;  and that low diff coins are almost strictly mined by lower hashrate connections.... That's the tendency anyways.   The only low diff coins my high hashrate connections have mined have been high diff coins; except for merge-mined coins which are just taking a low diff share from a higher diff coin and submitting it with the lower diff coin.

Market fluctuations in coin prices greatly effect whats profitable as well.  Just cause it was profitable and the miner switched to it;  a dump can cause an odd lack in profit when exchanged.  Then again, there have been some crazy exchange rates in the past with select coins at random events.  People doing pump and dumps.


Point is:  The low diff coins aren't wasting hash.  AFAIK the pool is properly using each miner connection on an as-needed per-miner basis....   It would be wasteful to put a high hash miner on a low diff coin and vice versa.

Maybe crackfoo can clarify if he knows;  but he didn't write the pool code;  he's more on the coinbox config and such side of things.... where it really matters.

That's where one makes profit ..on a low difficulty coin.

[tbearhere]

WERE YOU DYNAMICALLY SWITCHING BETWEEN WALLETS? --

I don't understand, you are talking about solo-mining, and pool mining, at the same time.        --scryptr

1) mining on skein pool, observing how skc makes a mess with all that switching and too fast blocks.
.. bloody hell
2) mining solo skc to raise its diff so it becomes fairly unprofitable for the pool for some time.
.. crawl back into your hole, slime
3) skein pool again, now it's mining only aur/myr/dgb.
.. everything is fine

Next time will through so hash with you at skc..... get the difficulty way up there.    

[jkminkov]

<BIG SNIP>

To add an unlisted algo I still don't know what you mean.

ON THE MINERCONTROL THREAD OPENING PAGE--

One of the contributors noted that "algos not in this list are not supported".  This refers to the algos in the posted configurration file.  Perhaps it is on KBomba's GitHub page, I'll check later.  I think it refers to algos NOT in the NiceHash API set.  I only added algos to the Zpool set of algos (Zpool is a YAAMP clone) because of this reasoning.  Some of the API information downloading may be hard-coded, so that only NiceHash algos current as of release 1.6.5.1 are completely supported.  I reason that the YAAMP API will allow the addition of algos that are available at Zpool, but not at NiceHash.

Thank you for the hint on the "usewindow" command.  I will try it later.

--scryptr

you can add newer algos on NH, just use for reference https://www.nicehash.com/index.jsp?p=api

example for MC : { "algo": "Blake256r8vnl", "priceid": "18",

can you help me with identifying, are those on zpool, what algo are on ccminer/sgminer?

15 = ScryptJaneNf16
16 = Blake256r8
17 = Blake256r14
18 = Blake256r8vnl

[tbearhere]

Could someone with a gigabyte 970gtx g1 please tell me their core clock frequently at no oc'ing while mining.  thx
Mine says 1413 core no oc'ing while mining when it should be 1117 ghz.

[scryptr]

<BIG SNIP>

To add an unlisted algo I still don't know what you mean.

ON THE MINERCONTROL THREAD OPENING PAGE--

One of the contributors noted that "algos not in this list are not supported".  This refers to the algos in the posted configurration file.  Perhaps it is on KBomba's GitHub page, I'll check later.  I think it refers to algos NOT in the NiceHash API set.  I only added algos to the Zpool set of algos (Zpool is a YAAMP clone) because of this reasoning.  Some of the API information downloading may be hard-coded, so that only NiceHash algos current as of release 1.6.5.1 are completely supported.  I reason that the YAAMP API will allow the addition of algos that are available at Zpool, but not at NiceHash.

Thank you for the hint on the "usewindow" command.  I will try it later.

--scryptr

you can add newer algos on NH, just use for reference https://www.nicehash.com/index.jsp?p=api

example for MC : { "algo": "Blake256r8vnl", "priceid": "18",

can you help me with identifying, are those on zpool, what algo are on ccminer/sgminer?

15 = ScryptJaneNf16
16 = Blake256r8
17 = Blake256r14
18 = Blake256r8vnl

NUMBER 17 MAY BE BLAKECOIN--

NiceHash is AMD-centric, and uses SGminer syntax.  Zpool does not offer the algos numbered 15, 16, or 18 currently.  If you are running SGminer, no problem, if you are running CCminer, try mining number 17 with "-a blakecoin" in the command line and point it at NiceHash.       --scryptr

[JaredKaragen]

digibyte sha256 removed?

[induktor]

Could someone with a gigabyte 970gtx g1 please tell me their core clock frequently at no oc'ing while mining.  thx
Mine says 1413 core no oc'ing while mining when it should be 1117 ghz.

1177 here in all my cards  (Gigabyte 970 G1)
(using driver 352.63, cuda 7.5, lubuntu 14.04)
this is, non-OCed, standard clocks, TPL lowered to 130W

[induktor]

Hello, any ideas why there was no payouts?, last payment received was 24 hours ago, and I am mining ETH at 250MH, I am pretty sure that I should have received something by now.
thanks

[crackfoo]

Hello, any ideas why there was no payouts?, last payment received was 24 hours ago, and I am mining ETH at 250MH, I am pretty sure that I should have received something by now.
thanks

There is no ETH on my pool... so maybe that's why??