Topic: ▂▃▅▆▇⫷[ 🆉🅿🅾🅾🅻.🅲🅰 ]⫸⫷[!KAWPOW!]⫸⫷[ the miners multipool ]⫸ ▇▆▅▃▂ - page 191. (Read 279614 times)
August 16, 2017, 05:44:44 PM
What is going on with SHA256? Payouts seem to have been cut down to 10% of normal ever since the math was changed to calculate GH to PH. Are we going to get back our lost mining profits when the math is fixed?
August 16, 2017, 10:17:25 AM
??yes, the xmg blockchain is still quite messed up. check their thread for more info. Doing the best I can to keep it on the right chain.
All day everything went well. But in the evening everything collapsed. And all the blocks became an orphan.
m7m is having a problem again. Just started happening a few minutes ago. Was fine all morning though.
Yes, I fell again
yup again. looks like they again done some updates to their repo. rebuilding again.
August 16, 2017, 09:40:02 AM
yes, the xmg blockchain is still quite messed up. check their thread for more info. Doing the best I can to keep it on the right chain.
All day everything went well. But in the evening everything collapsed. And all the blocks became an orphan.
m7m is having a problem again. Just started happening a few minutes ago. Was fine all morning though.
Yes, I fell again
August 16, 2017, 09:36:02 AM
yes, the xmg blockchain is still quite messed up. check their thread for more info. Doing the best I can to keep it on the right chain.
All day everything went well. But in the evening everything collapsed. And all the blocks became an orphan.
m7m is having a problem again. Just started happening a few minutes ago. Was fine all morning though.
August 16, 2017, 08:44:43 AM
Hello, love the pool!!!
Changing to GH for x11, qubit & quark to stay inline with NH?
Home Page Says:
* values in mBTC/MH/day, per GH for sha256 & blake algos, kSol. for equihash
Pool pages say:
* 24h estimation from net difficulty in mBTC/MH/day (in TH for sha256 & GH for blake, decred, x11, quark, qubit, kS for equihash)
Changing to GH for x11, qubit & quark to stay inline with NH?
Home Page Says:
* values in mBTC/MH/day, per GH for sha256 & blake algos, kSol. for equihash
Pool pages say:
* 24h estimation from net difficulty in mBTC/MH/day (in TH for sha256 & GH for blake, decred, x11, quark, qubit, kS for equihash)
August 16, 2017, 05:51:54 AM
Is there a way to see all "Hashtap" earnings?
If no, I think it'd be great to show it as maybe Hashtapped BTC or something like this.
If no, I think it'd be great to show it as maybe Hashtapped BTC or something like this.
August 15, 2017, 12:21:50 PM
yes, the xmg blockchain is still quite messed up. check their thread for more info. Doing the best I can to keep it on the right chain.
All day everything went well. But in the evening everything collapsed. And all the blocks became an orphan.
August 15, 2017, 11:54:20 AM
yes, the xmg blockchain is still quite messed up. check their thread for more info. Doing the best I can to keep it on the right chain.
August 15, 2017, 11:21:57 AM
August 15, 2017, 10:16:47 AM
For those curious how the iBeLink DM11G performs here is the wallet running that miner:
www.zpool.ca/?address=1CrovZGgLioTsGXmT8ZfKoNmJ2Nd3EGiRH
Cheers
www.zpool.ca/?address=1CrovZGgLioTsGXmT8ZfKoNmJ2Nd3EGiRH
Cheers
August 15, 2017, 06:01:59 AM
Something is wrong with Skien.
http://imgur.com/a/ElcTk
It is detecting alexis1.0. I have never used that miner before. And it detecting 7 workers. While I do technically have 7 cards they have all been detected per rig before as only three. ALso my hash rate shows as 800 but it should be around 5000.
I tried yiimp seems ok there.
http://imgur.com/a/ElcTk
It is detecting alexis1.0. I have never used that miner before. And it detecting 7 workers. While I do technically have 7 cards they have all been detected per rig before as only three. ALso my hash rate shows as 800 but it should be around 5000.
I tried yiimp seems ok there.
Appears to be fixed after posting this. Pretty much 24 hours and 8 cards worth of has wasted ug.
August 15, 2017, 05:39:47 AM
Something is wrong with Skien.
http://imgur.com/a/ElcTk
It is detecting alexis1.0. I have never used that miner before. And it detecting 7 workers. While I do technically have 7 cards they have all been detected per rig before as only three. ALso my hash rate shows as 800 but it should be around 5000.
I tried yiimp seems ok there.
http://imgur.com/a/ElcTk
It is detecting alexis1.0. I have never used that miner before. And it detecting 7 workers. While I do technically have 7 cards they have all been detected per rig before as only three. ALso my hash rate shows as 800 but it should be around 5000.
I tried yiimp seems ok there.
August 14, 2017, 02:51:19 PM
Yes!!!
first block is started
first block is started
Quote
Magi (m7m) 0.05925466 XMG 2.421 1 444 629 14m ago Immature (16/120)
Magi (m7m) 0.00000000 XMG 4.503 1 444 582 79m ago Orphan
Magi (m7m) 0.00000000 XMG 4.503 1 444 582 79m ago Orphan
Yes welll the 2nd now. The first one was orphaned when there was some sort of re-org on the chain. Smells a bit fishy if you ask me like bitmark type behaviour
August 14, 2017, 02:47:30 PM
Yes!!!
first block is started
first block is started
Quote
Magi (m7m) 0.05925466 XMG 2.421 1 444 629 14m ago Immature (16/120)
Magi (m7m) 0.00000000 XMG 4.503 1 444 582 79m ago Orphan
Magi (m7m) 0.00000000 XMG 4.503 1 444 582 79m ago Orphan
August 14, 2017, 02:38:49 PM
just had to suck it up and continue mining.
very, very old russian joke (anekdot):- What can you do?
- I can mine
-and what else?
- I can't mine
August 14, 2017, 01:15:26 PM
yeah. better to go to the XMG thread and ask for some compensation. it was their chain problems.
pardon for my BAD English... This is where and how?Here?
I was being facetious.
chain problems, happen. just had to suck it up and continue mining. the xmg wallet has been fixed and is working properly again.
August 14, 2017, 01:12:08 PM
yeah. better to go to the XMG thread and ask for some compensation. it was their chain problems.
pardon for my BAD English... This is where and how?Here?
August 14, 2017, 01:03:37 PM
m7m...
but
I'm a wasted miner?
Code:
[2017-08-14 20:51:26] CPU #0: 31.28 kH, 8512.45 H/s
[2017-08-14 20:51:28] CPU #0: 21.67 kH, 8164.51 H/s
[2017-08-14 20:51:28] Accepted 288/288 (100%), 793.37 kH, 33.23 kH/s, 79C
[2017-08-14 20:51:43] CPU #2: 148.89 kH, 8436.02 H/s
[2017-08-14 20:51:43] Accepted 289/289 (100%), 869.87 kH, 33.08 kH/s, 78C
[2017-08-14 20:52:23] m7m block 1444546, diff 3.578
[2017-08-14 20:52:23] CPU #1: 477.37 kH, 8233.56 H/s
[2017-08-14 20:52:23] CPU #0: 441.66 kH, 7982.94 H/s
[2017-08-14 20:52:23] CPU #2: 336.32 kH, 8339.34 H/s
[2017-08-14 20:52:23] CPU #3: 488.30 kH, 8422.02 H/s
[2017-08-14 20:52:58] m7m block 1444547, diff 3.578
[2017-08-14 20:52:58] CPU #0: 279.74 kH, 8139.55 H/s
[2017-08-14 20:52:58] CPU #2: 285.26 kH, 8300.29 H/s
[2017-08-14 20:52:58] CPU #3: 286.25 kH, 8329.07 H/s
[2017-08-14 20:52:58] CPU #1: 282.42 kH, 8217.63 H/s
[2017-08-14 20:53:05] CPU #3: 55.68 kH, 7737.88 H/s
[2017-08-14 20:53:05] Accepted 290/290 (100%), 903.10 kH, 32.40 kH/s, 77C
[2017-08-14 20:53:09] CPU #0: 86.61 kH, 8107.08 H/s
[2017-08-14 20:53:09] Accepted 291/291 (100%), 709.98 kH, 32.36 kH/s, 77C
[2017-08-14 20:53:32] CPU #2: 270.66 kH, 7985.43 H/s
[2017-08-14 20:53:32] CPU #1: 274.04 kH, 8085.33 H/s
[2017-08-14 20:53:32] CPU #3: 216.21 kH, 8098.50 H/s
[2017-08-14 20:53:32] CPU #0: 179.69 kH, 7741.20 H/s
[2017-08-14 20:53:38] CPU #2: 52.31 kH, 8537.09 H/s
[2017-08-14 20:53:38] Accepted 292/292 (100%), 722.25 kH, 32.
[2017-08-14 20:51:28] CPU #0: 21.67 kH, 8164.51 H/s
[2017-08-14 20:51:28] Accepted 288/288 (100%), 793.37 kH, 33.23 kH/s, 79C
[2017-08-14 20:51:43] CPU #2: 148.89 kH, 8436.02 H/s
[2017-08-14 20:51:43] Accepted 289/289 (100%), 869.87 kH, 33.08 kH/s, 78C
[2017-08-14 20:52:23] m7m block 1444546, diff 3.578
[2017-08-14 20:52:23] CPU #1: 477.37 kH, 8233.56 H/s
[2017-08-14 20:52:23] CPU #0: 441.66 kH, 7982.94 H/s
[2017-08-14 20:52:23] CPU #2: 336.32 kH, 8339.34 H/s
[2017-08-14 20:52:23] CPU #3: 488.30 kH, 8422.02 H/s
[2017-08-14 20:52:58] m7m block 1444547, diff 3.578
[2017-08-14 20:52:58] CPU #0: 279.74 kH, 8139.55 H/s
[2017-08-14 20:52:58] CPU #2: 285.26 kH, 8300.29 H/s
[2017-08-14 20:52:58] CPU #3: 286.25 kH, 8329.07 H/s
[2017-08-14 20:52:58] CPU #1: 282.42 kH, 8217.63 H/s
[2017-08-14 20:53:05] CPU #3: 55.68 kH, 7737.88 H/s
[2017-08-14 20:53:05] Accepted 290/290 (100%), 903.10 kH, 32.40 kH/s, 77C
[2017-08-14 20:53:09] CPU #0: 86.61 kH, 8107.08 H/s
[2017-08-14 20:53:09] Accepted 291/291 (100%), 709.98 kH, 32.36 kH/s, 77C
[2017-08-14 20:53:32] CPU #2: 270.66 kH, 7985.43 H/s
[2017-08-14 20:53:32] CPU #1: 274.04 kH, 8085.33 H/s
[2017-08-14 20:53:32] CPU #3: 216.21 kH, 8098.50 H/s
[2017-08-14 20:53:32] CPU #0: 179.69 kH, 7741.20 H/s
[2017-08-14 20:53:38] CPU #2: 52.31 kH, 8537.09 H/s
[2017-08-14 20:53:38] Accepted 292/292 (100%), 722.25 kH, 32.
but
Code:
Last 50 Blocks (m7m)
Name Amount Difficulty Block Time Status
Magi (m7m) 0.00000000 XMG 0.5 1 444 129 2d ago Orphan
Magi (m7m) 0.00000000 XMG 0.527 1 444 128 2d ago Orphan
Magi (m7m) 0.00000000 XMG 0.588 1 444 127 2d ago Orphan
Magi (m7m) 0.00000000 XMG 0.616 1 444 126 2d ago Orphan
Magi (m7m) 0.00000000 XMG 0.611 1 444 125 2d ago Orphan
Name Amount Difficulty Block Time Status
Magi (m7m) 0.00000000 XMG 0.5 1 444 129 2d ago Orphan
Magi (m7m) 0.00000000 XMG 0.527 1 444 128 2d ago Orphan
Magi (m7m) 0.00000000 XMG 0.588 1 444 127 2d ago Orphan
Magi (m7m) 0.00000000 XMG 0.616 1 444 126 2d ago Orphan
Magi (m7m) 0.00000000 XMG 0.611 1 444 125 2d ago Orphan
I'm a wasted miner?
yeah. better to go to the XMG thread and ask for some compensation. it was their chain problems.
August 14, 2017, 01:02:23 PM
I've mentioned this before. Please do some research on electron.
You'll find it is auxpow and no market for it so it is essentially worthless.. Aux coins are not wasting your hash.
I've looked through the forums and couldn't find a previous post from you mentioning Electron. I've investigated AuxPoW, is there any way for the site to display what us earned on these? Even if electron itself is worthless, the work done must be worth something.
[/quote]
https://bitcointalksearch.org/topic/m.20099865
there is no market, so nothing is earned and the work done, is not for electron, it's for the only PoW coin, BLC. All the other coins are aux, so work submitted for BLC is simply copied and tried on the the aux coins to see if it makes a valid block.
August 14, 2017, 01:00:26 PM
m7m...
but
I'm a wasted miner?
Code:
[2017-08-14 20:51:26] CPU #0: 31.28 kH, 8512.45 H/s
[2017-08-14 20:51:28] CPU #0: 21.67 kH, 8164.51 H/s
[2017-08-14 20:51:28] Accepted 288/288 (100%), 793.37 kH, 33.23 kH/s, 79C
[2017-08-14 20:51:43] CPU #2: 148.89 kH, 8436.02 H/s
[2017-08-14 20:51:43] Accepted 289/289 (100%), 869.87 kH, 33.08 kH/s, 78C
[2017-08-14 20:52:23] m7m block 1444546, diff 3.578
[2017-08-14 20:52:23] CPU #1: 477.37 kH, 8233.56 H/s
[2017-08-14 20:52:23] CPU #0: 441.66 kH, 7982.94 H/s
[2017-08-14 20:52:23] CPU #2: 336.32 kH, 8339.34 H/s
[2017-08-14 20:52:23] CPU #3: 488.30 kH, 8422.02 H/s
[2017-08-14 20:52:58] m7m block 1444547, diff 3.578
[2017-08-14 20:52:58] CPU #0: 279.74 kH, 8139.55 H/s
[2017-08-14 20:52:58] CPU #2: 285.26 kH, 8300.29 H/s
[2017-08-14 20:52:58] CPU #3: 286.25 kH, 8329.07 H/s
[2017-08-14 20:52:58] CPU #1: 282.42 kH, 8217.63 H/s
[2017-08-14 20:53:05] CPU #3: 55.68 kH, 7737.88 H/s
[2017-08-14 20:53:05] Accepted 290/290 (100%), 903.10 kH, 32.40 kH/s, 77C
[2017-08-14 20:53:09] CPU #0: 86.61 kH, 8107.08 H/s
[2017-08-14 20:53:09] Accepted 291/291 (100%), 709.98 kH, 32.36 kH/s, 77C
[2017-08-14 20:53:32] CPU #2: 270.66 kH, 7985.43 H/s
[2017-08-14 20:53:32] CPU #1: 274.04 kH, 8085.33 H/s
[2017-08-14 20:53:32] CPU #3: 216.21 kH, 8098.50 H/s
[2017-08-14 20:53:32] CPU #0: 179.69 kH, 7741.20 H/s
[2017-08-14 20:53:38] CPU #2: 52.31 kH, 8537.09 H/s
[2017-08-14 20:53:38] Accepted 292/292 (100%), 722.25 kH, 32.
[2017-08-14 20:51:28] CPU #0: 21.67 kH, 8164.51 H/s
[2017-08-14 20:51:28] Accepted 288/288 (100%), 793.37 kH, 33.23 kH/s, 79C
[2017-08-14 20:51:43] CPU #2: 148.89 kH, 8436.02 H/s
[2017-08-14 20:51:43] Accepted 289/289 (100%), 869.87 kH, 33.08 kH/s, 78C
[2017-08-14 20:52:23] m7m block 1444546, diff 3.578
[2017-08-14 20:52:23] CPU #1: 477.37 kH, 8233.56 H/s
[2017-08-14 20:52:23] CPU #0: 441.66 kH, 7982.94 H/s
[2017-08-14 20:52:23] CPU #2: 336.32 kH, 8339.34 H/s
[2017-08-14 20:52:23] CPU #3: 488.30 kH, 8422.02 H/s
[2017-08-14 20:52:58] m7m block 1444547, diff 3.578
[2017-08-14 20:52:58] CPU #0: 279.74 kH, 8139.55 H/s
[2017-08-14 20:52:58] CPU #2: 285.26 kH, 8300.29 H/s
[2017-08-14 20:52:58] CPU #3: 286.25 kH, 8329.07 H/s
[2017-08-14 20:52:58] CPU #1: 282.42 kH, 8217.63 H/s
[2017-08-14 20:53:05] CPU #3: 55.68 kH, 7737.88 H/s
[2017-08-14 20:53:05] Accepted 290/290 (100%), 903.10 kH, 32.40 kH/s, 77C
[2017-08-14 20:53:09] CPU #0: 86.61 kH, 8107.08 H/s
[2017-08-14 20:53:09] Accepted 291/291 (100%), 709.98 kH, 32.36 kH/s, 77C
[2017-08-14 20:53:32] CPU #2: 270.66 kH, 7985.43 H/s
[2017-08-14 20:53:32] CPU #1: 274.04 kH, 8085.33 H/s
[2017-08-14 20:53:32] CPU #3: 216.21 kH, 8098.50 H/s
[2017-08-14 20:53:32] CPU #0: 179.69 kH, 7741.20 H/s
[2017-08-14 20:53:38] CPU #2: 52.31 kH, 8537.09 H/s
[2017-08-14 20:53:38] Accepted 292/292 (100%), 722.25 kH, 32.
but
Code:
Last 50 Blocks (m7m)
Name Amount Difficulty Block Time Status
Magi (m7m) 0.00000000 XMG 0.5 1 444 129 2d ago Orphan
Magi (m7m) 0.00000000 XMG 0.527 1 444 128 2d ago Orphan
Magi (m7m) 0.00000000 XMG 0.588 1 444 127 2d ago Orphan
Magi (m7m) 0.00000000 XMG 0.616 1 444 126 2d ago Orphan
Magi (m7m) 0.00000000 XMG 0.611 1 444 125 2d ago Orphan
Name Amount Difficulty Block Time Status
Magi (m7m) 0.00000000 XMG 0.5 1 444 129 2d ago Orphan
Magi (m7m) 0.00000000 XMG 0.527 1 444 128 2d ago Orphan
Magi (m7m) 0.00000000 XMG 0.588 1 444 127 2d ago Orphan
Magi (m7m) 0.00000000 XMG 0.616 1 444 126 2d ago Orphan
Magi (m7m) 0.00000000 XMG 0.611 1 444 125 2d ago Orphan
I'm a wasted miner?
Jump to: