▂▃▅▆▇⫷[ 🆉🅿🅾🅾🅻.🅲🅰 ]⫸⫷[!10 FLUX PA's!]⫸⫷[ the miners multipool ]⫸ ▇▆▅▃▂

[cryptominer420]

Very strange, it's not doing it now. wish I had a screenshot of when it had them set low.

[1715287808]

1715287808

[1715287808]

1715287808

[cryptominer420]

zPoolMiner update:
Auto correcting API V2 is now live using a quad failover method. Please let me know if zpoolminer V1.9.0.0 has issues with random stops or reporting 0 profit.
No update required on your end.

[MrMaxwell]

Crackhead, your pool says:

We are short of this currency (7.67989501 LTC). Please STOP your miners and switch to BTC until we find more LTC blocks.
YOU are responsible if you continue to mine for LTC despite this warning.

Are you going to do anything about this? I don't want any shitty BTC with the huge fees and days long transaction times!

Can we get payouts consistently in BCH, LTC or DASH?

[variable42]

When using Sniffdog miner (CPU only), it would constantly say Yescrypt is the most profitable by a huge margin.   However, using the batch file method of mining, it would always mine m7m instead.  Basically the pool/site is saying m7m is more profitable.  If you look at the pool status table, it does indeed list m7m on top of Yescrypt.

So who's right?  And why the discrepancy?

PS: I only have m7m and yescrypt in the password, no other algos.  (-p c=BTC, yescrypt, m7m)

I'm guessing Sniffdog is actually taking your hash rates into account. Whereas your .bat file isn't. You should change your password to reflect your hash rates. Also, don't use spaces in your password.

Code:

-p c=BTC,m7m=X,yescrypt=Y

Where X is your m7m hash rate in MH/s, and Y is your yescrypt hash rate in kH/s.

See the bottom of http://www.zpool.ca/site/multialgo for a concrete example.

[variable42]

Crackhead, your pool says:

We are short of this currency (7.67989501 LTC). Please STOP your miners and switch to BTC until we find more LTC blocks.
YOU are responsible if you continue to mine for LTC despite this warning.

Are you going to do anything about this? I don't want any shitty BTC with the huge fees and days long transaction times!

Can we get payouts consistently in BCH, LTC or DASH?

BTC is the only guaranteed payout. Anything else is dependent upon the pool mining sufficient quantities of that coin. LTC is a special case where crackfoo manually buys coins for payouts. But if he's busy sometime you won't get a payout for a day or two. Ultimately though, unless notified otherwise, BTC is the only sure thing.

[guytechie]

When using Sniffdog miner (CPU only), it would constantly say Yescrypt is the most profitable by a huge margin.   However, using the batch file method of mining, it would always mine m7m instead.  Basically the pool/site is saying m7m is more profitable.  If you look at the pool status table, it does indeed list m7m on top of Yescrypt.

So who's right?  And why the discrepancy?

PS: I only have m7m and yescrypt in the password, no other algos.  (-p c=BTC, yescrypt, m7m)

I'm guessing Sniffdog is actually taking your hash rates into account. Whereas your .bat file isn't. You should change your password to reflect your hash rates. Also, don't use spaces in your password.

Code:

-p c=BTC,m7m=X,yescrypt=Y

Where X is your m7m hash rate in MH/s, and Y is your yescrypt hash rate in kH/s.

See the bottom of http://www.zpool.ca/site/multialgo for a concrete example.

Yeah, I read about the profitability factors, but I didn't know what denominations they were using.  I though  both were in kH/s since cpuminer would report both as kH/s.  Then I once though they both were in MH/s, since both are reported MH/s on zpool's pool status table.

We need something to let us know which algo is using which metric.

Even a simple line like the Pool Status chart:   * values in mBTC/MH/day, per PH for sha256 & GH for scrypt, blake, decred, x11, quark, qubit, kS for equihash

[CapeTownMinter]

when trying to get paid in DigitalCoin DGC ....your site changes it DigiBye DGB with DGC  address.... tried two different DGC addresses and the some thing happened.

strange thing is Ive been paid DGC with  the same address  last week

 my DGC address is DKVSjRpp8dmGLQahf9P7zmmkadFkSJByvX

I hope this gets fixed soon so that i can use your pool again

thanx

[variable42]

Yeah, I read about the profitability factors, but I didn't know what denominations they were using.  I though  both were in kH/s since cpuminer would report both as kH/s.  Then I once though they both were in MH/s, since both are reported MH/s on zpool's pool status table.

We need something to let us know which algo is using which metric.

Even a simple line like the Pool Status chart:   * values in mBTC/MH/day, per PH for sha256 & GH for scrypt, blake, decred, x11, quark, qubit, kS for equihash

The way I do it is to navigate to Pool, select an algo, and look at the graph for "Last 24 Hours Estimate (mBTC/XXX/day)." Whatever it lists for XXX is usually the metric you need to specify in your password. If you're really unsure about a particular algo, you can verify simply by doing the multiplication yourself (estimate * hash rate), and checking to see that the mBTC amount is reasonable for a day of mining.

[cryptominer420]

@ crackfoo

Vardiff bug happened again phi diff under minimum but I got a screenshot this time

https://www.awesomescreenshot.com/image/3102596/215f980f9a25c9d00002c07735ffe8c9

[CapeTownMinter]

when trying to get paid in DigitalCoin DGC ....your site changes it DigiBye DGB with DGC  address.... tried two different DGC addresses and the some thing happened.

strange thing is Ive been paid DGC with  the same address  last week

 my DGC address is DKVSjRpp8dmGLQahf9P7zmmkadFkSJByvX

I hope this gets fixed soon so that i can use your pool again

thanx

same address is now stating its UNO same address changed to 3 different coins??

[WitWolfy]

Been mining Equihash for almost the whole day now seeing it was the highest profit pool and all just to notice that my current unpaid balance hasnt increased at all In like 10 hours! Is this normal, or is Equihash like LBRY when it comes to payments, next to non existent.

Edit: screw this, I stopped mining. Basically nothing made the whole day. Nobody is paying due to the whole Asia closing shop story.

Plus the whole Zpool page isnt loading 80% of the time.

[cryptominer420]

Been mining Equihash for almost the whole day now seeing it was the highest profit pool and all just to notice that my current unpaid balance hasnt increased at all In like 10 hours! Is this normal, or is Equihash like LBRY when it comes to payments, next to non existent.

Edit: screw this, I stopped mining. Basically nothing made the whole day. Nobody is paying due to the whole Asia closing shop story.

Plus the whole Zpool page isnt loading 80% of the time.

Not sure what cards your mining with but the most profitable algo's to mine have for the most part been
Nvidia
Phi, Nist5, Skein
AMD
Neoscrypt

[Rodderman]

Yea nothing changes scrypt still under paid and drops out constantly, all other algo's too fix the damn pool Foo!

[guytechie]

Yeah, I read about the profitability factors, but I didn't know what denominations they were using.  I though  both were in kH/s since cpuminer would report both as kH/s.  Then I once though they both were in MH/s, since both are reported MH/s on zpool's pool status table.

We need something to let us know which algo is using which metric.

Even a simple line like the Pool Status chart:   * values in mBTC/MH/day, per PH for sha256 & GH for scrypt, blake, decred, x11, quark, qubit, kS for equihash

The way I do it is to navigate to Pool, select an algo, and look at the graph for "Last 24 Hours Estimate (mBTC/XXX/day)." Whatever it lists for XXX is usually the metric you need to specify in your password. If you're really unsure about a particular algo, you can verify simply by doing the multiplication yourself (estimate * hash rate), and checking to see that the mBTC amount is reasonable for a day of mining.

Using that method, both m7m and yescrypt should be in MH/s.

[malthrax]

Yeah, I read about the profitability factors, but I didn't know what denominations they were using.  I though  both were in kH/s since cpuminer would report both as kH/s.  Then I once though they both were in MH/s, since both are reported MH/s on zpool's pool status table.

We need something to let us know which algo is using which metric.

Even a simple line like the Pool Status chart:   * values in mBTC/MH/day, per PH for sha256 & GH for scrypt, blake, decred, x11, quark, qubit, kS for equihash

The way I do it is to navigate to Pool, select an algo, and look at the graph for "Last 24 Hours Estimate (mBTC/XXX/day)." Whatever it lists for XXX is usually the metric you need to specify in your password. If you're really unsure about a particular algo, you can verify simply by doing the multiplication yourself (estimate * hash rate), and checking to see that the mBTC amount is reasonable for a day of mining.

Using that method, both m7m and yescrypt should be in MH/s.

it doesn't matter, as long as you're consistent - the profitability factors are relative to each other.  you could do m7m=5,yescrypt=7  or you could do m7m=5000,yescrypt=7000  and the results would be identical

[variable42]

Using that method, both m7m and yescrypt should be in MH/s.

The yescrypt chart shows kH/s. Check the caption for the chart on the left, not the table on the right.


Anyway, if you do the math, MH/s doesn't make sense. The pool hash rate for yescrypt is only 6.1MH/s right now. If the profitability calculation was in fact using MH/s and not kH/s, that means that the entire pool of 21,000 miners would only generate $0.91 combined per day at the current rate. That's not right.

[variable42]

it doesn't matter, as long as you're consistent - the profitability factors are relative to each other.  you could do m7m=5,yescrypt=7  or you could do m7m=5000,yescrypt=7000  and the results would be identical

You're not wrong in saying that m7m=5,yescrypt=7 and m7m=5000,yescrypt=7000 will provide identical results. However, if your intention is for the stratum servers to ensure that you're always mining the most profitable algo for your equipment, then the profitability factors you provide in your password need to be the same denomination as the current estimate for the algo.

Here are the "current" profitability estimates for m7m and yescrypt:

m7m, 0.0733
yescrypt, 0.01403

Let's say you have an Intel Core i5-6600K. Your hash rates are as follows:

m7m, 69kH/s
yescrypt, 2.4kH/s

If you specify your password as m7m=69,yescrypt=2.4, this is the math that the stratum server does:

m7m, 0.0733 * 69 = 5.0577
yescrypt, 0.01403 * 2.4 = 0.033672

Well, m7m should be way more profitable for you than yescrypt, right? According to these calculations, you'd be making $0.38/day with yescrypt, but $56.57/day with m7m. Thus, the stratum server will keep you mining m7m all day long.

Except m7m is measured in MH/s, while yescrypt is measured in kH/s. So, you won't be making $56/day in reality. Thus, the correct password would be m7m=0.069,yescrypt=2.4. This give us:

m7m, 0.0733 * 0.069 = 0.0050577
yescrypt, 0.01403 * 2.4 = 0.033672

In reality, m7m is only going to bring you $0.06/day at that rate. Not $56. Then, yescrypt is more profitable at this point in time. And that's why right now, you see 21,000 miners on yescrypt, and only 634 on m7m.

This can be confusing because if you look at the chart on the website, m7m is listed higher in the table than yescrypt, because it's "current" estimate is a bigger number. But because they're measured using different denominations, yescrypt is currently far more profitable.

[guytechie]

it doesn't matter, as long as you're consistent - the profitability factors are relative to each other.  you could do m7m=5,yescrypt=7  or you could do m7m=5000,yescrypt=7000  and the results would be identical

You're not wrong in saying that m7m=5,yescrypt=7 and m7m=5000,yescrypt=7000 will provide identical results. However, if your intention is for the stratum servers to ensure that you're always mining the most profitable algo for your equipment, then the profitability factors you provide in your password need to be the same denomination as the current estimate for the algo.

Here are the "current" profitability estimates for m7m and yescrypt:

m7m, 0.0733
yescrypt, 0.01403

Let's say you have an Intel Core i5-6600K. Your hash rates are as follows:

m7m, 69kH/s
yescrypt, 2.4kH/s

If you specify your password as m7m=69,yescrypt=2.4, this is the math that the stratum server does:

m7m, 0.0733 * 69 = 5.0577
yescrypt, 0.01403 * 2.4 = 0.033672

Well, m7m should be way more profitable for you than yescrypt, right? According to these calculations, you'd be making $0.38/day with yescrypt, but $56.57/day with m7m. Thus, the stratum server will keep you mining m7m all day long.

Except m7m is measured in MH/s, while yescrypt is measured in kH/s. So, you won't be making $56/day in reality. Thus, the correct password would be m7m=0.069,yescrypt=2.4. This give us:

m7m, 0.0733 * 0.069 = 0.0050577
yescrypt, 0.01403 * 2.4 = 0.033672

In reality, m7m is only going to bring you $0.06/day at that rate. Not $56. Then, yescrypt is more profitable at this point in time. And that's why right now, you see 21,000 miners on yescrypt, and only 634 on m7m.

This can be confusing because if you look at the chart on the website, m7m is listed higher in the table than yescrypt, because it's "current" estimate is a bigger number. But because they're measured using different denominations, yescrypt is currently far more profitable.

Thanks for the detailed explanation.  This is on point.  No dick stuck in fan.

[RedRoverZA]

I have noticed that when a new solution is found for an algo the shares are only allocated at the percentage share you are sitting at when the solution switches from new to immature. if you mining this algo 24/7 this has no affect on you.

But, if you are using algo switching this has a potentially big affect. For example if I am mining x17 and during a hour long period 10 solutions are found but they are all still sitting at new when my miner now decides to switch to something else. When the x17 sols start changing to immature I only receive a share of the 1st solution and get nothing from the next 9 even although I was hashing x17 at the time the sol was found.

This also works in reverse if you start mining an algo after a new sol is found but before it changes from new to immature you will get a share even if you where not actually hashing that algo when the sol was found.

I am assuming the delay in switching from new to immature was to counteract the questions that keep popping up caused by orphans and this is an unintended side affect?

[bttalkdim2]

On x17 - last 3 hours all blocks are Orphan..
Is all ok ?