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

[crackfoo]

@zpool

you will ad cryptonight algo soon to this pool? maybe moreno?

I can really only add what Epsylon3 develops. I don't have the brain function to understand how to code new algo and such. ^_^

 

but cryptonight isnt a new algo. this algo exist already. but its only a improve from my side

I know this. it's not an aglo that been made for this pool though.

[JaredKaragen]

Thats a fucking scampool lol, mined coins balance was 57.000 sat, after it went unpaid balance 42,000 satoshi.

Mega scam pool, guys go mine on Suprnova, or Multipool.Us

value when mined and value sold for on exchange are two DIFFERENT values.  Do not mistake them.

[teddybeer]

I dont mine BTC, i mine specific coin, and payouts going by this coin.


10-12% total iam loosing on them way to balance, if i got share 70 coins means in my wallet must happen 70 coins not a fucking 62

[mtx_demon]

I dont mine BTC, i mine specific coin, and payouts going by this coin.


10-12% total iam loosing on them way to balance, if i got share 70 coins means in my wallet must happen 70 coins not a fucking 62

If you don't like the rewards just build your own pool or look for something else!!
it is that simple man!!

[sidroast]

I dont mine BTC, i mine specific coin, and payouts going by this coin.


10-12% total iam loosing on them way to balance, if i got share 70 coins means in my wallet must happen 70 coins not a fucking 62

You didn't lose them, the site is pretty clear about how it works:

1. you mine on a given algo
2. you set wallet and payout to the coin output you want
3. the mining happens, coins r mined, then they mature, then site exchanges coins based on rates from the current, live rates from the exchanges listed on the front page
4. you get paid based on the post-exchange

Exchange rates change all the time. Some go up, some go down. Sometimes your balance is gonna go up, sometimes down. If you don't like the # of coins you're returned, try a less-volatile coin.

[JaredKaragen]

I dont mine BTC, i mine specific coin, and payouts going by this coin.


10-12% total iam loosing on them way to balance, if i got share 70 coins means in my wallet must happen 70 coins not a fucking 62

Again, nothing was said about what _algo_ you are mining and what _coin_ you get paid out in.

What you are seeing is exactly what I stated in my comment above this one...... With a slight amount of research you would see this too.

I suggest you do a little research on why your payouts aren't what you expected.  There are many reasons to fall short of an estimate of your earnings.

Remember, all pricing displayed is based on rates when that action took place (pending, confirmed, exchange, etc).

LBRY blocks loose ~1/4 value by the time they are sold on exchange.  And that's 0.001+btc deviance on average.  Which is normal considering the inflating amount of coin reward per block.

[Mudbankkeith]

The other option is to mine the specific coin, get paid out in the same coin, then take your chance on selling on your chosen exchange, or keep the coin in your own wallet.

[sidroast]

I believe I have identified the issue with sha256 miners on this pool.

My sha256 miners have been repeatedly crashing on this pool, obviously I don't want that but I like zpool so I'm hoping I can help fix this if need be   I've been dev'ing since the 80s so if I can lend a hand in that way, please let me know.

Forgive me for stinking at formatting, if there's something I can do to make what's coming more readable, again please let me know.

So first, here is when everyhing looks fine:

[  107.241573] 0x0000: 0x03 0x00 0x00 0x1a 0x86 0x10 0x03 0x13
[  107.249376] send BC data:
[  107.249376] 0x0000: 0x03 0x02 0x00 0x1a 0x86 0x10 0x03 0x13
[  107.257189] send BC data:
[  107.257189] 0x0000: 0x03 0x05 0x00 0x1a 0x86 0x10 0x03 0x13
[  107.265002] send BC data:
[  107.265002] 0x0000: 0x03 0x20 0x00 0x03 0x86 0x10 0x03 0x04

When the log is like that, hashrate stays up, everything is great, blah blah blah...


Next, we come to this, where the extranonce comes in to play:

[  107.333369] Sending open core work
[  107.336931] Send new block cmd
[  107.349539] Timeout {1}
[  107.352107] Snd Time Interval {21}ms
[  107.355850] Set bitmain configure
[  107.359321] clear FPGA nonce buffer
[  107.363058] drv fifo empty
[  108.944829] ch0-as50: dev->task_buffer_wr{0x00000000}rd{0x00000000}ret work_id{0xc36c} don't match task_buffer_match{0x436c}
[  109.315866] drv fifo empty
[  111.268995] drv fifo empty
[  113.222124] drv fifo empty
[  113.376239] get chain0 reg0x0
[  113.379410] send BC data:
[  113.379410] 0x0000: 0x03 0x00 0x00 0x03 0x84 0x00 0x00 0x11
[  113.387640] Change diff to 10
[  113.390795] diff fix to 6
[  113.393538] Change net_diff to 23
[  113.397913] timeout {0x542}
[  113.400852] rev timeout {0x42050080}

We start getting timeouts, notice we also start getting empty/garbage packets (the fifo empty lines).

After this it's a long line of timeouts, new block commands, and ridiculously low diff:

[  113.451896] Chain0 PLL: {0x13859805}
[  113.463230] asic cmd return 0a988513
[  113.466993] Chain0 PLL: {0x1385980a}
[  113.470736] asic cmd return 0f988513
[  113.474488] Chain0 PLL: {0x1385980f}
[  113.478230] asic cmd return 14988513
[  113.481976] Chain0 PLL: {0x13859814}
[  125.781891] Change diff to 11
[  125.785040] diff fix to 6
[  125.874532] Send new block cmd
[  135.585449] Send new block cmd
[  139.394110] Send new block cmd
[  147.415553] Send new block cmd
[  150.136338] Send new block cmd
[  153.515229] Send new block cmd
[  163.875027] Change diff to 12
[  163.878167] diff fix to 6
[  163.970346] Send new block cmd
[  164.849064] drv fifo empty
[  170.919441] Send new block cmd
[  193.048723] Send new block cmd
[  193.054117] ch0-as33: dev->task_buffer_wr{0x000035c4}rd{0x000035c4}ret work_id{0xb4c6} don't match task_buffer_match{0x34c6}
[  203.431180] Send new block cmd
[  213.729965] Send new block cmd
[  224.325686] Send new block cmd
[  227.108914] Send new block cmd
[  230.558142] Send new block cmd
[  233.835482] Send new block cmd
[  244.489735] Send new block cmd
[  267.679208] Send new block cmd
[  268.894085] Send new block cmd
[  269.155778] Send new block cmd
[  289.927276] Send new block cmd
[  300.980012] Send new block cmd
[  311.985830] Send new block cmd
[  326.124586] Send new block cmd
[  339.222172] Send new block cmd
[  353.317892] Send new block cmd
[  364.382414] Send new block cmd
[  365.339300] drv fifo empty
[  367.737935] Send new block cmd
[  388.552791] Change diff to 13
[  388.555931] diff fix to 6
[  388.622595] Send new block cmd
[  389.558107] Send new block cmd
[  391.466324] Send new block cmd
[  399.640137] Send new block cmd

Notice the very low diff? It hovers around there, along with an endless log of "Send new block cmd" issues.

This happens very consistently on both my Antminers and Spondoolies.

They're all running cgminer4.8.0 so the log output is nearly identical for all of them.

This would account for what some of the posts in this thread are saying about the slowly reducing hashrate reported by the zpool website that results in 0 hash.

What is the problem?

Well I would have to look at the zpool logs to identify the problem as this is expected behavior from cgminer but since that is unlikely I'll take a stab, it's likely:

When the algo switches coins, one or more of the coins is not sending proper (or empty, or headlerless) packets or NULLs to the miners, which the sha256 miners and cgminer read as empty/garbage, leading to the miner eventually dying. The pool software is not switching to a new coin at that point because it is not receiving the expected output from the miners either, leading it to attempt to resend the same packet over and over as the msg the miner is sending is telling the pool that it didn't receive the packet (hence the timeout), leading to an infinite loop or at least a failing one.


My suggestion:

Do a (relatively) quick look at the logs for the sha256 coins and see which ones have not created any blocks on this pool and remove them, or, trim the sha256 coins down to the only ones with a regular hashrate on the site. It's likely one of the non-producing coins that is causing the issue.

If there's anything I can do to help, please let me know- I love using zpool

[Mudbankkeith]

I believe I have identified the issue with sha256 miners on this pool.

My sha256 miners have been repeatedly crashing on this pool, obviously I don't want that but I like zpool so I'm hoping I can help fix this if need be   I've been dev'ing since the 80s so if I can lend a hand in that way, please let me know.

Forgive me for stinking at formatting, if there's something I can do to make what's coming more readable, again please let me know.
                                 "comments shortened"
This happens very consistently on both my Antminers and Spondoolies.

They're all running cgminer4.8.0 so the log output is nearly identical for all of them.

This would account for what some of the posts in this thread are saying about the slowly reducing hashrate reported by the zpool website that results in 0 hash.

What is the problem?

Well I would have to look at the zpool logs to identify the problem as this is expected behavior from cgminer but since that is unlikely I'll take a stab, it's likely:

When the algo switches coins, one or more of the coins is not sending proper (or empty, or headlerless) packets or NULLs to the miners, which the sha256 miners and cgminer read as empty/garbage, leading to the miner eventually dying. The pool software is not switching to a new coin at that point because it is not receiving the expected output from the miners either, leading it to attempt to resend the same packet over and over as the msg the miner is sending is telling the pool that it didn't receive the packet (hence the timeout), leading to an infinite loop or at least a failing one.


My suggestion:

Do a (relatively) quick look at the logs for the sha256 coins and see which ones have not created any blocks on this pool and remove them, or, trim the sha256 coins down to the only ones with a regular hashrate on the site. It's likely one of the non-producing coins that is causing the issue.

If there's anything I can do to help, please let me know- I love using zpool

Maybe splitting the sha256 coins into two sections would help in this?

First section for the "dinosaurs" I mean "Large" Miners needing large steady difficulty.

The second section that could possibly respond quicker to difficulty changes and lower settings.

[sidroast]

Maybe splitting the sha256 coins into two sections would help in this?

First section for the "dinosaurs" I mean "Large" Miners needing large steady difficulty.

The second section that could possibly respond quicker to difficulty changes and lower settings.

I would like to do a git clone of the repo on github but the challenge is I do not know what differences there are between that & what's on zpool, or if there are any at all. If there aren't and crackfoo can confirm, I'll get the code from github and see if I can find an answer to the issue.

[Aplayer]

password field: c=<SYMBOL>

Is it the same currency with the wallet address in username?
or
Is it one of the symbol of currency in the algo?

[crackfoo]

password field: c=<SYMBOL>

Is it the same currency with the wallet address in username?
or
Is it one of the symbol of currency in the algo?

the same as the address you want to get paid in.

[crackfoo]

Maybe splitting the sha256 coins into two sections would help in this?

First section for the "dinosaurs" I mean "Large" Miners needing large steady difficulty.

The second section that could possibly respond quicker to difficulty changes and lower settings.

I would like to do a git clone of the repo on github but the challenge is I do not know what differences there are between that & what's on zpool, or if there are any at all. If there aren't and crackfoo can confirm, I'll get the code from github and see if I can find an answer to the issue.

it's the same as the yiimp repo.

[crackfoo]

My suggestion:

Do a (relatively) quick look at the logs for the sha256 coins and see which ones have not created any blocks on this pool and remove them, or, trim the sha256 coins down to the only ones with a regular hashrate on the site. It's likely one of the non-producing coins that is causing the issue.

If there's anything I can do to help, please let me know- I love using zpool

I'll go through them and cull the none performers.

[crackfoo]

My suggestion:

Do a (relatively) quick look at the logs for the sha256 coins and see which ones have not created any blocks on this pool and remove them, or, trim the sha256 coins down to the only ones with a regular hashrate on the site. It's likely one of the non-producing coins that is causing the issue.

If there's anything I can do to help, please let me know- I love using zpool

I'll go through them and cull the none performers.

I just trimmed a bunch on sha/scrypt and x11.

[sidroast]

I just trimmed a bunch on sha/scrypt and x11.

Thanks, bud. Out doing an airport run, I'll test tonight.

[crackfoo]

I just trimmed a bunch on sha/scrypt and x11.

Thanks, bud. Out doing an airport run, I'll test tonight.

Any better/worse?

[crackfoo]

crackfoo, FYI looks like Epsylon3 made some changes to his yiimp frontend
so now if you have wallet page open (top Wallet tab is active),
and click on an algo in Pool Status - everything goes to that algo page (top Pool tab activates itself).
for me that's long awaited fix, maybe you could implement the same behavior
thx

hrmm I'll see. I did just merge his recent changes but I've been busy with my 9-5 last week and must have missed one.

Should be ok now.

[adsactly]

Can you Add GameCredits to the List of Coins that can be mined with zpool.ca?

http://gamecredits.org

http://gamecredits.net

[crackfoo]

Can you Add GameCredits to the List of Coins that can be mined with zpool.ca?

http://gamecredits.org

http://gamecredits.net

If you look here: http://www.zpool.ca/site/gomining?algo=scrypt

You can see we have it added already.

Cheers