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

[Nataly2014]

Erumara

Here is my configuration for ZPOOL on SHA256-algo
in stratum-proxy-nicehash.conf - file
---------------------------
{
   "disableStratum" : true,
  "pools" :
  [
  {
    "name" : "ZPOOL",
    "host" : "mine.zpool.ca:3333",
    "user" : "my wallet BTC",
    "password" : "c=BTC, d=8192",
    "enableExtranonceSubscribe" : true
  }
  ]
}
-------------------------------
Correct me if incorrect
p.s. proxy taked from this link :  nicehash.com/ ?p=asic

[Nataly2014]

Erumara

...I set my reconnect period to 15 seconds and the stability testing to 30.
now set to 300secs and works great....

where you wrote it, please?

[Erumara]

Erumara

...I set my reconnect period to 15 seconds and the stability testing to 30.
now set to 300secs and works great....

where you wrote it, please?

You've definitely got the hang of it, add this to your header, and based on your difficulty I'm *guessing* you don't want to disable stratum, if you're on an old miner with no stratum support you'll be stuck using getwork which I have not messed around with.

  "poolConnectionRetryDelay" : 15,
  "poolReconnectStabilityPeriod" : 30,
  "poolNoNotifyTimeout" : 120,
  "poolSwitchingStrategy": "priorityFailover",
  "rejectReconnectOnDifferentHost" : false,
  "poolHashrateSamplingPeriod" : 300,
  "userHashrateSamplingPeriod" : 300,
  "connectionHashrateSamplingPeriod" : 300,

[Nataly2014]

Erumara

I did not understand in what file put this code:

  "poolConnectionRetryDelay" : 15,
  "poolReconnectStabilityPeriod" : 30,
  "poolNoNotifyTimeout" : 120,
  "poolSwitchingStrategy": "priorityFailover",
  "rejectReconnectOnDifferentHost" : false,
  "poolHashrateSamplingPeriod" : 300,
  "userHashrateSamplingPeriod" : 300,
  "connectionHashrateSamplingPeriod" : 300,

[Erumara]

Just because you're a nice person:

{
  "logDirectory" : "",
  "logLevel" : "INFO",
  "stratumListenPort" : 3333,
  "stratumListenAddress" : "0.0.0.0",
  "getworkListenPort" : 8332,
  "getworkListenAddress" : "0.0.0.0",
  "apiListenPort" : 8888,
  "apiListenAddress" : "0.0.0.0",
  "poolConnectionRetryDelay" : 15,
  "poolReconnectStabilityPeriod" : 30,
  "poolNoNotifyTimeout" : 120,
  "poolSwitchingStrategy": "priorityFailover",
  "rejectReconnectOnDifferentHost" : false,
  "poolHashrateSamplingPeriod" : 300,
  "userHashrateSamplingPeriod" : 300,
  "connectionHashrateSamplingPeriod" : 300,
  "isScrypt" : false,
  "databaseDirectory": "",
  "hashrateDatabaseSamplingPeriod": 300,
  "hashrateDatabaseHistoryDepth": 7,
  "pools" :
  [
  {
    "name" : "ZPOOL",
    "host" : "mine.zpool.ca:3333",
    "user" : "my wallet BTC",
    "password" : "c=BTC,sha256,d=8192",
    "enableExtranonceSubscribe" : true,
    "appendWorkerNames" : false
  }
  ]
}

Give that a try, let me know!

[meatslurpee]

I'm getting pretty high reject rate displayed on zpool but not seeing any rejects in my miners. They are near 100%. Is this something to worry about? I've never even noticed an actual reject value projection until the last couple days.

[JaredKaragen]

I'm afraid I need some help with profitability normalization.  I'm running several 750ti cards.  Since the normalization rates at zpool are based on AMD, it doesn't make sense for me to use them.  What nVidia miners out there use for factors, based on the hashrate for the various algorithms?  I can't seem to figure out how to calculate these values.

Simple.  look a few pages back for my posted batch.  You will see the normalization factors I created.  They directly correlate to hashrate at the level of profitability that the particular algo is paid at.  You find the details in the profitability preview at the upper right of zpool:  *** values in mBTC/Mh/day (mBTC/Gh/day for sha256 and blake algos)


So:

If your machine does 500Kh of SCRYPT;  and since scrypt is measured in Mh, then its going to be 0.5Mh or scrypt=0.5
If your machine does 1.5Gh of DECRED;  and since decred is measured in Gh;  then its going to be 1.5Gh or decred=1.5
If your machine does 11.5Mh if LYRA2V2; and since lyra2v2 is measured in Mh;  then its going to be 11.5Mh or lyra2v2=11.5
If your machine does 110Kh of ARGON2; and since  argon2 is measured in Mh; then its going to be 0.110 or argon2=0.110

This way they are all balanced to the scale they are paid on;  and thus;  balanced to each other.

We normalized a machine with 2x 750Ti's in SF recently;  Ill try and post that batch when I head back to the City again.  But its worth notice a 750Ti is about half the computing power of a GTX980.

[Nataly2014]

Just because you're a nice person:

{
  "logDirectory" : "",
  "logLevel" : "INFO",
 ......

Give that a try, let me know!

I can connect to my proxy from cpuminer
my conf cpuminer:
cpuminer_x64_SSE2 -o http://127.0.0.1:8332 -u x -p x
but sgminer -not connected - and from scrypt and from sha256
my conf sgminer:
sgminer.exe -o http://127.0.0.1:8332 -u x -p x
pause
------------------------------
my video R9 290x
use sgminer-5-1-0
What do you recommend miner programm
Thanks!

[tbearhere]

bug to c11 algo maximum shares 79.3800%

Even more scary is the 5% sha256 fee and whopping 20% scrypt fee!!! Surely a development system to production system rollout error.

Whoops, didn't notice that! I forked the pool software to the next version and missed the example where you can set per algo fees.


https://github.com/tpruvot/yiimp/blob/next/web/serverconfig.sample.php#L73

And sometimes no accepts at the pool, takes 4 minutes before my full hashrate shows... what a waste of hash. The stratum is 34 secs into the future too.

[AngryDwarf]

And sometimes no accepts at the pool, takes 4 minutes before my full hashrate shows... what a waste of hash. The stratum is 34 secs into the future too.

The pool displayed hash rate is a 5 min average, so yes it will take time to show full hash rate.

[tbearhere]

Crackfoo why not switch, on the WALLET page, the wallet with the miners readout...that way we can see the most commonly looked at at one glance.    Thx
This shrunk to show you.. its to small to read. 

[citronick]

Just because you're a nice person:

{
  "logDirectory" : "",
  "logLevel" : "INFO",
  "stratumListenPort" : 3333,
  "stratumListenAddress" : "0.0.0.0",
  "getworkListenPort" : 8332,
  "getworkListenAddress" : "0.0.0.0",
  "apiListenPort" : 8888,
  "apiListenAddress" : "0.0.0.0",
  "poolConnectionRetryDelay" : 15,
  "poolReconnectStabilityPeriod" : 30,
  "poolNoNotifyTimeout" : 120,
  "poolSwitchingStrategy": "priorityFailover",
  "rejectReconnectOnDifferentHost" : false,
  "poolHashrateSamplingPeriod" : 300,
  "userHashrateSamplingPeriod" : 300,
  "connectionHashrateSamplingPeriod" : 300,
  "isScrypt" : false,
  "databaseDirectory": "",
  "hashrateDatabaseSamplingPeriod": 300,
  "hashrateDatabaseHistoryDepth": 7,
  "pools" :
  [
  {
    "name" : "ZPOOL",
    "host" : "mine.zpool.ca:3333",
    "user" : "my wallet BTC",
    "password" : "c=BTC,sha256,d=8192",
    "enableExtranonceSubscribe" : true,
    "appendWorkerNames" : false
  }
  ]
}

Give that a try, let me know!

spread the love 

in some other groups - members are just plain rude and nasty - unlike here in zpool (so far  ), where members help each other, especially from senior members, and our op is also very transparent and cool dude. Many thanks to all again. I first came here from CM and learnt the finer things in multi-algo mining thanks to all of you.

[Nataly2014]

Crackfoo why not switch, on the WALLET page, the wallet with the miners readout...that way we can see the most commonly looked at at one glance.    Thx
This shrunk to show you.. its to small to read. 

On the WALLET page - on the right side at the bottom of the window we can see how much income for each coin and in parentheses it algo
Is not that what you need?

[Nataly2014]

Just because you're a nice person:

{
  "logDirectory" : "",
......
Give that a try, let me know!

spread the love 

in some other groups - members are just plain rude and nasty - unlike here in zpool (so far  ), where members help each other, especially from senior members, and our op is also very transparent and cool dude. Many thanks to all again. I first came here from CM and learnt the finer things in multi-algo mining thanks to all of you.

I subscribe to your words - here I found a lot of useful information and helpful members of the community  !!!

[tbearhere]

Crackfoo why not switch, on the WALLET page, the wallet with the miners readout...that way we can see the most commonly looked at at one glance.    Thx
This shrunk to show you.. its to small to read.

On the WALLET page - on the right side at the bottom of the window we can see how much income for each coin and in parentheses it algo
Is not that what you need?

No, I need to see my miners are online. Thx
Really It would be nice , on the wallet page, to see miners upper left...right below them last 24 hour balance ..right below that last 24 hrs payout..then advertisement...then wallet . and to lock the algo's in alphabetical order.  

Crackfoo needs the advertisements I think.

[tbearhere]

And sometimes no accepts at the pool, takes 4 minutes before my full hashrate shows... what a waste of hash. The stratum is 34 secs into the future too.

The pool displayed hash rate is a 5 min average, so yes it will take time to show full hash rate.

Yes thank you. I think it should reach that in 2 minutes but. I wish they would wright into code 1 minute. Sometimes my miner is ready to switch before it reaches its max.. need to change settings in my conf file to mine that algo longer.

[tbearhere]

No accepts ?
EDIT: 5 minutes and still none. I think I'll lower the difficulties or take them out.

[crackfoo]

Yup, I've tried manipulating those even up to the 600, it then just hangs that much longer.  There were a few other timeouts I tried manipulating as well with little improvement. If only it was smart enough to identify which wallet it was that was causing the issues, and simply disconnect it... it would be so much better. To reset stratum, seems like a big hammer and IMO, was a big shortcut by the orig dev.

I doubt you could narrow it down to any particular coins wallet, as it seems it can be any wallet at any time that might either respond immediately or take a long time to return. I assume the wallet must be doing something that prevents it from processing rpc calls at the time.

Calling GBT with no parameters can return a massive amount of data on the BTC wallet. Do you know if it is making a GBT call on BTC? Since this is not being mined directly, it might be possible to put an exclusion in for the BTC wallet.

Yeah I can't really. I tried reducing them all to just main stream, higher diff coins and it would still happen. Stratum has to be always calling GBT on all coins all the time after each block notify. BTC isn't enabled in stratum so those calls don't get made but yes, BTC GBT spits out a lot of crap. Early on it was enabled and saw errors all the time but isn't the source of the on going issue unfortunately.

[Nataly2014]

Yup, I've tried manipulating those even up to the 600, it then just hangs that much longer.  There were a few other timeouts I tried

I doubt you could narrow it down to any particular coins wallet

...I tried reducing them all to just main stream, higher diff coins and it would still happen. Stratum has to be always calling GBT on all coins all the time after each block notify. BTC isn't enabled in stratum so those calls don't get made but yes, BTC GBT spits out a lot of crap. Early on it was enabled and saw errors all the time but isn't the source of the on going issue unfortunately.

Let me know when the  defeat dead hashes (my dead hash 15-30%)
We all have an interest in your site!!!
Just let me know if i am can than help in the test your pool
We are with you!
Do not worry so!
  Let me know on my help to you!

[tbearhere]

No accepts ?
EDIT: 5 minutes and still none. I think I'll lower the difficulties or take them out.

My difficulty was set to high... now it not only reads it but the time to reach its hashrate takes only a minute.. but it looks like the pool was accepting it.