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

[buckets420]

yep it seems to be working now thanks alot  !

[citronick]

You call yourself a professional administrator, and understand elementary problem can not !!!

With this conduct;  I personally suggest you find a new pool.....  You can only cook an omelette if you are given eggs to make it with.

edit:
 @crackfoo:  sorry; I tried... I'm not going to try helping this guy anymore.  After reading his 5 replies below this one;  Its plain and clear that he can't be dealt with sanely.

I saw his rants and posts in MRR thread too - he seems to be renting a lot of small multiple X11 rigs - I am speechless.

[citronick]

Hi Guys, I am trying to get my old AMD GPUs to start working on DCR, is the syntax below correct? I am getting no respond from port 5744

cgminer.exe --blake256 -o http://mine.zpool.ca:5744 -u 1JqDhwuxgwCaQ1PZksYCDMgxAuMevzrzPH -p c=BTC --no-submit-stale --scan-time 2 --queue 0

Appreciate any help

[crackfoo]

Hi Guys, I am trying to get my old AMD GPUs to start working on DCR, is the syntax below correct? I am getting no respond from port 5744

cgminer.exe --blake256 -o http://mine.zpool.ca:5744 -u 1JqDhwuxgwCaQ1PZksYCDMgxAuMevzrzPH -p c=BTC --no-submit-stale --scan-time 2 --queue 0

Appreciate any help

You have to use the algo called decred and a miner that supports it.

https://github.com/tpruvot/ccminer

or

https://github.com/tpruvot/sgminer

Not sure which would work with your card...

[citronick]

Hi Guys, I am trying to get my old AMD GPUs to start working on DCR, is the syntax below correct? I am getting no respond from port 5744

cgminer.exe --blake256 -o http://mine.zpool.ca:5744 -u 1JqDhwuxgwCaQ1PZksYCDMgxAuMevzrzPH -p c=BTC --no-submit-stale --scan-time 2 --queue 0

Appreciate any help

You have to use the algo called decred and a miner that supports it.

https://github.com/tpruvot/ccminer

or

https://github.com/tpruvot/sgminer

Not sure which would work with your card...

Thanks cf for the links, got it working now for AMD GPU.

For others who are interested in DCR, see primer below. GPU used: R9 390 giving about 1.6 Gh/s single GPU

Get SGMINER 5.3.1 here -> http://cryptomining-blog.com/wp-content/download/sgminer-5-3-1-tpruvot-decred.zip
Supports both AMD and Nvidia cards

My working syntax:
sgminer.exe -k decred -o stratum+tcp://mine.zpool.ca:5744 -u 1JqDhwuxgwCaQ1PZksYCDMgxAuMevzrzPH -p c=BTC -I 25

POSTNOTES:
I ran DCR and ETH mining at the same time in two separate windows and got 800mh/s and 15mh/s, for DCR and ETH respectively.
Otherwise, ETH mining will run 26-28MH/s on a single R9-390 GPU on its own.
The SGMINER 5.3.1. was able to push the R9-390 to 1.6-1.8 Gh/s with Diff level = 4, running on its own.

[AngryDwarf]

Hi, Mining Quark on zpookl why does the hashrate fluctuate so much? One minute it will be 26 MH/s and next minute 10 MH/s why such drastic swings? Diff is constant at 0.12 it seems.

Because the reported hash rate is a 5 min average, which really will fluctuate based on actual submissions. Hour long averages tend to be more accurate and fluctuate less, but not really appropriate for an algo switching pool.

[AngryDwarf]

Get SGMINER 5.3.1 here -> http://cryptomining-blog.com/wp-content/download/sgminer-5-3-1-tpruvot-decred.zip
Supports both AMD and Nvidia cards

sgminer supports both AMD and nvidia cards because it uses OpenCL. However, NVIDIA cards perform poorly at OpenCL in comparison to AMD cards, so for an NVIDIA card people should use a CUDA supported miner, such as ccminer, as it will make a massive difference in hash rate. There is a decred supporting ccminer 1.7.4 in tpruvot's github repository. The CUDA 7.5 seems to be the better CUDA version for decred, CUDA 6.5 for other algos.

[joblo]

Hi, Mining Quark on zpookl why does the hashrate fluctuate so much? One minute it will be 26 MH/s and next minute 10 MH/s why such drastic swings? Diff is constant at 0.12 it seems.

Because the reported hash rate is a 5 min average, which really will fluctuate based on actual submissions. Hour long averages tend to be more accurate and fluctuate less, but not really appropriate for an algo switching pool.

It depends on the frequency of accepts. The hashrate reported at the pool is based on the number of accepts multiplied by
the time since the previous accept multiplied by the hashrate. If the accept rate is irregular the pool receives fewer larger
shares making the reported hashrate more volatile.

When CPU mining with a slow CPU you can go over 5 minutes without a share submission in which case the pool will report
0 hashrate for that 5 minutes. But when the next share is submitted it's longer than 5 minutes so the 5 minutes average
is reported as higher than the actual hashrate.

Theoretically it doesn't make a difference.

[jkminkov]

I just got a transaction from an unknown payer:

https://btc.blockr.io/tx/info/331abc248a35382abdc22901ad4efd9e9501ec82960a7879b3d4e6c9fddb5d00

anyone else get one on this payment?   I am kind of baffled;  especially since I dont give my address out for donation or anything....

once a week you get dust 10K-99K satoshi

Was it from Nicehash perhaps? We only pay out the smaller balances on Sunday afternoon/evening.

true, but you don't exclude those who are being paid on regular basis.

[AngryDwarf]

@sibnia - What are you on about? Could you be clear please.

[AngryDwarf]

Hi, Mining Quark on zpookl why does the hashrate fluctuate so much? One minute it will be 26 MH/s and next minute 10 MH/s why such drastic swings? Diff is constant at 0.12 it seems.

Because the reported hash rate is a 5 min average, which really will fluctuate based on actual submissions. Hour long averages tend to be more accurate and fluctuate less, but not really appropriate for an algo switching pool.

But if the hashrate is reasonably constant at my end, why would the shares I submit fluctuate? Shouldn't they be constant as well?

Your miner hashrate will generate hashes at a reasonably consistent rate. However, only hashes that are greater than your stratum difficulty will be submitted. This really is a luck based random process, you may submit several hashes in one second, then none for several seconds. The pool is calculating your hashrate based on the actual above difficulty hashes submitted to the pool.

[crackfoo]

I'm in the process of bringing up another server in hopes it will eliminate the ongoing issues with stratum disconnects which are mostly affecting sha256 and scrypt. It is 4x as big and powerful as the other 3 so it should handle quite a bit of expansion.

I'll post Annoncements when downtime is expected etc.. But as the last upgrade went, it should be  mostly unnoticeable.

Cheers

Sweet!

Eagerly awaiting =)

of course after I spend 4k on a new server... SHA decides to run perfectly fine... for the last 24 hours anyway. Albeit, the inventory was reduced.  Setup still in progress and have found some stratum code that can be changed as well.  Lots of room for expansion anyway.

Cheers

[Megaquake]

What happened to the decred algo not finding blocks?

I know that sha256 is vulnerable to a block withholding attack, what about decred it was doing great then nothing the last few days.

[pallas]

What happened to the decred algo not finding blocks?

I know that sha256 is vulnerable to a block withholding attack, what about decred it was doing great then nothing the last few days.

Well need more Hashrate.

[Megaquake]

What happened to the decred algo not finding blocks?

I know that sha256 is vulnerable to a block withholding attack, what about decred it was doing great then nothing the last few days.

Well need more Hashrate.

I understand that but we had a quite a bit of hash rate during the time of loss, and it remained until it became unprofitable.

[gambadamba]

hi

start

ccminer.exe -a lyra2v2 -o stratum+tcp://mine.zpool.ca:4533 -u 1Pj67qVZLfQewr47k1wCHgt2mzaSQ7rvU2 -p lyra2v2

not mining / pool blocked? ip
 

everything worked.
and then the pool is not responding.
and still I can not connect ?

[crackfoo]

What happened to the decred algo not finding blocks?

I know that sha256 is vulnerable to a block withholding attack, what about decred it was doing great then nothing the last few days.

Well need more Hashrate.

I understand that but we had a quite a bit of hash rate during the time of loss, and it remained until it became unprofitable.

It's just a string of poor luck. Some other pools with a lot of hashrate had long bouts of no blocks as well.

Frustrating I know, but seems blocks come bunched together and make up for it eventually.

[Walker-D-Plank]

Is there any plans on adding Eth as a payout coin on Zpool?

[AngryDwarf]

Hi, Mining Quark on zpookl why does the hashrate fluctuate so much? One minute it will be 26 MH/s and next minute 10 MH/s why such drastic swings? Diff is constant at 0.12 it seems.

Because the reported hash rate is a 5 min average, which really will fluctuate based on actual submissions. Hour long averages tend to be more accurate and fluctuate less, but not really appropriate for an algo switching pool.

But if the hashrate is reasonably constant at my end, why would the shares I submit fluctuate? Shouldn't they be constant as well?

Your miner hashrate will generate hashes at a reasonably consistent rate. However, only hashes that are greater than your stratum difficulty will be submitted. This really is a luck based random process, you may submit several hashes in one second, then none for several seconds. The pool is calculating your hashrate based on the actual above difficulty hashes submitted to the pool.

ok I see, I was seeing similar with ETH at nano pool as well so yea that makes sense. Thanks. Would that mean it is more beneficial to set a lower difficulty to submit more shares and have a higher hashrate? Or is the a scaling multiplyer added to the shares so if I return 10 shares in 5 mins at diff = 0.5 and 5 shares in 5 mins at diff = 1 would the payput be the same?

It makes no difference. Your share contribution is based on the stratum difficulty, not the difficulty of the actual share submitted. In pooled mining, there are two difficulties, the pool stratum difficulty, and the coin difficulty. Most hashes will be below the pool stratum difficulty and so not submitted. Rarely, you get a hash which is above the coin difficulty - congratulations you have solved a block on behalf of the pool. Most of the submitted shares though will be below the coin difficulty. This does nothing towards solving a block, it just proves to the pool that your miner is doing work and so you are contributed a share towards the eventual reward at the stratum difficulty. Effectively each hash is a lottery ticket that may win the block reward. The higher the hash rate, the more lottery tickets you are getting.
It is worth setting the difficulty of the miner to do an average of 10 submits a second if you are multi algo mining and the initial stratum difficulty is not appropriate for your miner hash rate, as the stratum processes used are rather slow to change difficulty.

[tbearhere]

I have been paid regularly for weeks.

Me too pallas.