zpool does not support the use of workername. Simply supply the BTC address you want to get paid in.
So, can I use just one BTC address for all (three) rigs?
Topic: █▓▒░-< [ZPOOL.CA][BTC Multipool] The miners multipool >-░▒▓█ Paid 925+ BTC - page 108. (Read 217687 times)
April 17, 2016, 09:46:35 AM
zpool does not support the use of workername. Simply supply the BTC address you want to get paid in.
So, can I use just one BTC address for all (three) rigs?
April 17, 2016, 01:37:12 AM
why CORG NO PAYOUT. 2 DAYS STILL NO PAYOUT.
Corg is a coin highlighted in red, which means the pool is not mining enough coins to support payouts. If you hover over the coin in the pool section, it looks like CORG is 180 blocks short. When a coin goes red, payouts do not occur until enough coins have been mined. So stop mining that coin and choose another until the pool has caught up. This may take a long time if the coin is not high up the profitability charts.
April 17, 2016, 12:17:46 AM
I added in that algorithm line and:
Ran at diff = 16000 for a couple hours, finally connection dropped and when it restarted I had lost 3/12 blades, 1 unit needed a reboot 2 units needed a power cycle.
Ran at diff = 18000 for a couple hours, connection drops, 1 unit recovered, 3 units locked up and needed power cycles, 1 unit needed a second power cycle and a soft reboot.
Now testing at diff = 20000, I hope something friggin works this profitability today is bonkers!
20000 had one machine lock up, had a failover at 22000 diff that they *almost* recovered from, only 1 blade dropped on one unit. So I have set them at 24000 diff and hopefully they stay up while I'm at my buddy's BBQ.
Is your profile BTC address valid citronik? I think you have some karma headed your way
the S7s, depending on which batch, are temperamental lot.
I use a safe 16000 most of the time, and use 22k-24k when solo mining PPC.
Well yeah, my BTC address is valid
Sorry to say that even at 24k diff I still came home to one unit locked up, and two needing reboots.
Just a nudge to crackfoo to see if there's a solution to this issue.
Still sent some karma your way citronik, cheers!
April 16, 2016, 10:54:47 PM
I added in that algorithm line and:
Ran at diff = 16000 for a couple hours, finally connection dropped and when it restarted I had lost 3/12 blades, 1 unit needed a reboot 2 units needed a power cycle.
Ran at diff = 18000 for a couple hours, connection drops, 1 unit recovered, 3 units locked up and needed power cycles, 1 unit needed a second power cycle and a soft reboot.
Now testing at diff = 20000, I hope something friggin works this profitability today is bonkers!
20000 had one machine lock up, had a failover at 22000 diff that they *almost* recovered from, only 1 blade dropped on one unit. So I have set them at 24000 diff and hopefully they stay up while I'm at my buddy's BBQ.
Is your profile BTC address valid citronik? I think you have some karma headed your way
the S7s, depending on which batch, are temperamental lot.
I use a safe 16000 most of the time, and use 22k-24k when solo mining PPC.
Well yeah, my BTC address is valid
April 16, 2016, 10:30:09 PM
hi crackfoo - i am testing this dual miner (ETH and DCR) by claymore - I have asked claymore about zpool support but he/she has not responded yet.
Stratum is supported so I think it should be ok, however my testing gives me error connecting to zpool. Any thoughts?
https://bitcointalksearch.org/topic/m.14501372
Stratum is supported so I think it should be ok, however my testing gives me error connecting to zpool. Any thoughts?
https://bitcointalksearch.org/topic/m.14501372
Seems for decred it is only HTTP (getwork)
"-dpool Decred pool address. Only HTTP protocol is supported currently."
ok, you are right.
i saw the to do list and includes stratum support for DCR
UPDATE:
v2 just released and supports stratum.
Works ok but DCR having 8-9% rejects on zpool.
One of my more powerful rigs is mining ETH and DCR (4 x R9-390), and CPU mining for Argon2 and Yescrypt at zpool, all at the same time.
ETH and DCR is now using just the Claymore Dual miner.
https://bitcointalksearch.org/topic/m.14566543
April 16, 2016, 05:43:25 PM
why CORG NO PAYOUT. 2 DAYS STILL NO PAYOUT.
April 16, 2016, 05:26:50 PM
I added in that algorithm line and:
Ran at diff = 16000 for a couple hours, finally connection dropped and when it restarted I had lost 3/12 blades, 1 unit needed a reboot 2 units needed a power cycle.
Ran at diff = 18000 for a couple hours, connection drops, 1 unit recovered, 3 units locked up and needed power cycles, 1 unit needed a second power cycle and a soft reboot.
Now testing at diff = 20000, I hope something friggin works this profitability today is bonkers!
20000 had one machine lock up, had a failover at 22000 diff that they *almost* recovered from, only 1 blade dropped on one unit. So I have set them at 24000 diff and hopefully they stay up while I'm at my buddy's BBQ.
Is your profile BTC address valid citronik? I think you have some karma headed your way
April 16, 2016, 04:49:25 PM
something is off on the pool stats for DECRED.
When we seem to be generating a lot of blocks in good amounts of time (good luck);
On the page it shows decred profitability next to the coin itself on the left. Should be between 4.xxx and 5.xxx when it's 2.xxx
It seems to read lower the better the pool luck is..... am I the only one seeing this?
When we seem to be generating a lot of blocks in good amounts of time (good luck);
On the page it shows decred profitability next to the coin itself on the left. Should be between 4.xxx and 5.xxx when it's 2.xxx
It seems to read lower the better the pool luck is..... am I the only one seeing this?
I think cause the diff jumped and the price dropped...
legendary
Activity: 1848
Merit: 1166
My AR-15 ID's itself as a toaster. Want breakfast?
April 16, 2016, 04:15:34 PM
something is off on the pool stats for DECRED.
When we seem to be generating a lot of blocks in good amounts of time (good luck);
On the page it shows decred profitability next to the coin itself on the left. Should be between 4.xxx and 5.xxx when it's 2.xxx
It seems to read lower the better the pool luck is..... am I the only one seeing this?
When we seem to be generating a lot of blocks in good amounts of time (good luck);
On the page it shows decred profitability next to the coin itself on the left. Should be between 4.xxx and 5.xxx when it's 2.xxx
It seems to read lower the better the pool luck is..... am I the only one seeing this?
April 16, 2016, 03:29:53 PM
Any updates on the sha256 stratums? Been testing my s7's on and off, and no matter how I adjust the difficulty within a few hours the connection has dropped and for whatever reason it will most often boot back up with a blade or two not working, really pointless to have to power cycle the unit just to use a pool; even if the profitability is nice.
difficulty level of 16000 to 22000, works for me.
Have tried everything from 9000 to 26000 with the same results, anything else I can try?
1. have you set a backup pool?
2. how do you set the difficulty level?
Backup pool is nicehash, password: c=BTC, d=22000, failover works fine but as soon as they reconnect to zpool the hashrate drops by 1/3-2/3 while the asics all show up as working, and 1 or 2 blades will drop in temp. Sometimes the miner will soft reset itself but that rarely fixes the problem.
try:
c=BTC, SHA256, d=16000
I added in that algorithm line and:
Ran at diff = 16000 for a couple hours, finally connection dropped and when it restarted I had lost 3/12 blades, 1 unit needed a reboot 2 units needed a power cycle.
Ran at diff = 18000 for a couple hours, connection drops, 1 unit recovered, 3 units locked up and needed power cycles, 1 unit needed a second power cycle and a soft reboot.
Now testing at diff = 20000, I hope something friggin works this profitability today is bonkers!
April 16, 2016, 11:38:44 AM
had 500+ DGB sitting for 3 days no payot addr: DSzAZij4WtfxhwLTMwwaXRgPxoGQvirHiH Can support take a look at this for me. Thanks for all the work you do!
I think the problem is that for multi algo coins, such as DGB and MYR, the sha256 wallet acts as a distribution wallet, and these aren't running at the moment. In fact, even the DGB qubit coin is not running at the moment, which really hurts profitability on that algo.
I would like to see DGB and MYR up and running again as these where great coins for sending to Polo or Bittrex for exchange to another coin.
I understand crackfoo has been trying to get to the bottom of stratum disconnects with the sha256 port in particular, but all this messing about has really hurt sha256 profitability and knocked confidence in alt coin mining.
Okay, with all DGB wallets up and running, I don't seem to be getting a payout either, so perhaps there is an issue. Have you got your payment yet? Also, not had a VRC payment for a while but not sure if the POS coin wallets are manually or automatically topped up. When mining MZC, some 3 hourly payments seemed to be missed (defo above 0.0025 min payout at the time on that coin!)
April 16, 2016, 09:30:24 AM
Any updates on the sha256 stratums? Been testing my s7's on and off, and no matter how I adjust the difficulty within a few hours the connection has dropped and for whatever reason it will most often boot back up with a blade or two not working, really pointless to have to power cycle the unit just to use a pool; even if the profitability is nice.
difficulty level of 16000 to 22000, works for me.
Have tried everything from 9000 to 26000 with the same results, anything else I can try?
1. have you set a backup pool?
2. how do you set the difficulty level?
Backup pool is nicehash, password: c=BTC, d=22000, failover works fine but as soon as they reconnect to zpool the hashrate drops by 1/3-2/3 while the asics all show up as working, and 1 or 2 blades will drop in temp. Sometimes the miner will soft reset itself but that rarely fixes the problem.
try:
c=BTC, SHA256, d=16000
April 16, 2016, 09:13:11 AM
Any updates on the sha256 stratums? Been testing my s7's on and off, and no matter how I adjust the difficulty within a few hours the connection has dropped and for whatever reason it will most often boot back up with a blade or two not working, really pointless to have to power cycle the unit just to use a pool; even if the profitability is nice.
difficulty level of 16000 to 22000, works for me.
Have tried everything from 9000 to 26000 with the same results, anything else I can try?
1. have you set a backup pool?
2. how do you set the difficulty level?
Backup pool is nicehash, password: c=BTC, d=22000, failover works fine but as soon as they reconnect to zpool the hashrate drops by 1/3-2/3 while the asics all show up as working, and 1 or 2 blades will drop in temp. Sometimes the miner will soft reset itself but that rarely fixes the problem.
April 16, 2016, 03:47:59 AM
Any updates on the sha256 stratums? Been testing my s7's on and off, and no matter how I adjust the difficulty within a few hours the connection has dropped and for whatever reason it will most often boot back up with a blade or two not working, really pointless to have to power cycle the unit just to use a pool; even if the profitability is nice.
difficulty level of 16000 to 22000, works for me.
Have tried everything from 9000 to 26000 with the same results, anything else I can try?
1. have you set a backup pool?
2. how do you set the difficulty level?
April 16, 2016, 01:57:41 AM
Any updates on the sha256 stratums? Been testing my s7's on and off, and no matter how I adjust the difficulty within a few hours the connection has dropped and for whatever reason it will most often boot back up with a blade or two not working, really pointless to have to power cycle the unit just to use a pool; even if the profitability is nice.
difficulty level of 16000 to 22000, works for me.
Have tried everything from 9000 to 26000 with the same results, anything else I can try?
April 16, 2016, 01:20:45 AM
Any updates on the sha256 stratums? Been testing my s7's on and off, and no matter how I adjust the difficulty within a few hours the connection has dropped and for whatever reason it will most often boot back up with a blade or two not working, really pointless to have to power cycle the unit just to use a pool; even if the profitability is nice.
difficulty level of 16000 to 22000, works for me.
April 16, 2016, 12:40:25 AM
Any updates on the sha256 stratums? Been testing my s7's on and off, and no matter how I adjust the difficulty within a few hours the connection has dropped and for whatever reason it will most often boot back up with a blade or two not working, really pointless to have to power cycle the unit just to use a pool; even if the profitability is nice.
April 15, 2016, 02:21:17 PM
Just tried mining some DGB on a previously used DGB address. The wallet has now changed to UNO. c=DGB in password. Is this because the qubit wallet is not running?
EDIT: It initially said DGB-sha, whereas before it just said DGB.
EDIT: It initially said DGB-sha, whereas before it just said DGB.
Oh shoot, perhaps. Qubit now up again.
Yep, that's sorted it, thankfully before too many lost hashes.
April 15, 2016, 02:11:18 PM
Just tried mining some DGB on a previously used DGB address. The wallet has now changed to UNO. c=DGB in password. Is this because the qubit wallet is not running?
EDIT: It initially said DGB-sha, whereas before it just said DGB.
EDIT: It initially said DGB-sha, whereas before it just said DGB.
Oh shoot, perhaps. Qubit now up again.
April 15, 2016, 12:54:03 PM
Just tried mining some DGB on a previously used DGB address. The wallet has now changed to UNO. c=DGB in password. Is this because the qubit wallet is not running?
EDIT: It initially said DGB-sha, whereas before it just said DGB.
EDIT: It initially said DGB-sha, whereas before it just said DGB.
Jump to: