[ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay]

[Pool42]

Can someone please help me, which pool is working?

I thank you in advance for your help.

 

For the moment our pool Pool42 is working.

EDIT:

for now
xmg.pool42.com
xmg.minerclaim.net

Ah, ninja'd  

[jcreyesb]

Can someone please help me, which pool is working?

I thank you in advance for your help.

 

For the moment our pool Pool42 is working.

EDIT:

for now
xmg.pool42.com
xmg.minerclaim.net

Ah, ninja'd  

Solo mining is working

[ifyousmell]

why there is even no link for the website, it leads to a slack channel??

[abbeytim]

reported to mods

[My9bot]

why there is even no link for the website, it leads to a slack channel??

http://www.m-core.org/

[malafaya]

now https://chainz.cryptoid.info/xmg/  

They updated their wallet and are resyncing.

[malafaya]

There's something odd.
People are mining with the old rewards scheme already: https://chainz.cryptoid.info/xmg/block.dws?1479159.htm .
This is ahead of schedule. Possibly a cause for forking?

i'm mining solo..
https://chainz.cryptoid.info/xmg/tx.dws?dceea06d62d0683bca93946a5d6e19e7f6fdb25a0d2c92cfe8f6dd810c59c46b.htm    6 XMG

https://chainz.cryptoid.info/xmg/tx.dws?9c41f47343631f0ffd5af84c4e23bd5d170a8e6faa770adc504edf4cb712fcad.htm           5 xmg


last block 1479166
 one node
connect=104.128.225.215

That was a few hours ago. Check the recent blocks.

[My9bot]

now https://chainz.cryptoid.info/xmg/  

They updated their wallet and are resyncing.

aso
thx

[abbeytim]

cool they just fixed the pool i use 

[jcreyesb]

There's something odd.
People are mining with the old rewards scheme already: https://chainz.cryptoid.info/xmg/block.dws?1479159.htm .
This is ahead of schedule. Possibly a cause for forking?

i'm mining solo..
https://chainz.cryptoid.info/xmg/tx.dws?dceea06d62d0683bca93946a5d6e19e7f6fdb25a0d2c92cfe8f6dd810c59c46b.htm    6 XMG

https://chainz.cryptoid.info/xmg/tx.dws?9c41f47343631f0ffd5af84c4e23bd5d170a8e6faa770adc504edf4cb712fcad.htm           5 xmg


last block 1479166
 one node
connect=104.128.225.215

That was a few hours ago. Check the recent blocks.

16:23:46

getinfo


16:23:46

{
"version" : "v1.4.3.1",
"protocolversion" : 71062,
"walletversion" : 60000,
"balance" : 0.00090000,
"newmint" : 12.40329947,
"stake" : 0.00000000,
"blocks" : 1479193,
"timeoffset" : 0,
"moneysupply" : 7340022.00787421,
"connections" : 1,
"proxy" : "",
"ip" : "190.202.x.x",
"ipv4" : "190.202.x.x",
"ipv6" : "0.0.0.0",
"difficulty" : {
"proof-of-work" : 1.24027707,
"proof-of-stake" : 0.00024414
},
"testnet" : false,
"keypoololdest" : 1503492406,
"keypoolsize" : 101,
"mininput" : 0.00000000,
"paytxfee" : 0.00000000,
"errors" : ""
}

[malafaya]

There's something odd.
People are mining with the old rewards scheme already: https://chainz.cryptoid.info/xmg/block.dws?1479159.htm .
This is ahead of schedule. Possibly a cause for forking?

i'm mining solo..
https://chainz.cryptoid.info/xmg/tx.dws?dceea06d62d0683bca93946a5d6e19e7f6fdb25a0d2c92cfe8f6dd810c59c46b.htm    6 XMG

https://chainz.cryptoid.info/xmg/tx.dws?9c41f47343631f0ffd5af84c4e23bd5d170a8e6faa770adc504edf4cb712fcad.htm           5 xmg


last block 1479166
 one node
connect=104.128.225.215

That was a few hours ago. Check the recent blocks.

16:23:46

getinfo


16:23:46

{
"version" : "v1.4.3.1",
"protocolversion" : 71062,
"walletversion" : 60000,
"balance" : 0.00090000,
"newmint" : 12.40329947,
"stake" : 0.00000000,
"blocks" : 1479193,
"timeoffset" : 0,
"moneysupply" : 7340022.00787421,
"connections" : 1,
"proxy" : "",
"ip" : "190.202.x.x",
"ipv4" : "190.202.x.x",
"ipv6" : "0.0.0.0",
"difficulty" : {
"proof-of-work" : 1.24027707,
"proof-of-stake" : 0.00024414
},
"testnet" : false,
"keypoololdest" : 1503492406,
"keypoolsize" : 101,
"mininput" : 0.00000000,
"paytxfee" : 0.00000000,
"errors" : ""
}

Not sure what you're trying to show. Your wallet is still v1.4.3.1. Check the reward in this block: https://chainz.cryptoid.info/xmg/block.dws?1479159.htm
The new v1.4.4 is supposed to return to old rewards tomorrow night, but I can already see new blocks with rewards of 30 XMG, probably because pools already upgraded and there's something wrong with the "time trigger"...

[abbeytim]

There's something odd.
People are mining with the old rewards scheme already: https://chainz.cryptoid.info/xmg/block.dws?1479159.htm .
This is ahead of schedule. Possibly a cause for forking?

i'm mining solo..
https://chainz.cryptoid.info/xmg/tx.dws?dceea06d62d0683bca93946a5d6e19e7f6fdb25a0d2c92cfe8f6dd810c59c46b.htm    6 XMG

https://chainz.cryptoid.info/xmg/tx.dws?9c41f47343631f0ffd5af84c4e23bd5d170a8e6faa770adc504edf4cb712fcad.htm           5 xmg


last block 1479166
 one node
connect=104.128.225.215

That was a few hours ago. Check the recent blocks.

16:23:46

getinfo


16:23:46

{
"version" : "v1.4.3.1",
"protocolversion" : 71062,
"walletversion" : 60000,
"balance" : 0.00090000,
"newmint" : 12.40329947,
"stake" : 0.00000000,
"blocks" : 1479193,
"timeoffset" : 0,
"moneysupply" : 7340022.00787421,
"connections" : 1,
"proxy" : "",
"ip" : "190.202.x.x",
"ipv4" : "190.202.x.x",
"ipv6" : "0.0.0.0",
"difficulty" : {
"proof-of-work" : 1.24027707,
"proof-of-stake" : 0.00024414
},
"testnet" : false,
"keypoololdest" : 1503492406,
"keypoolsize" : 101,
"mininput" : 0.00000000,
"paytxfee" : 0.00000000,
"errors" : ""
}

Not sure what you're trying to show. Your wallet is still v1.4.3.1. Check the reward in this block: https://chainz.cryptoid.info/xmg/block.dws?1479159.htm
The new v1.4.4 is supposed to return to old rewards tomorrow night, but I can already see new blocks with rewards of 30 XMG, probably because pools already upgraded and there's something wrong with the "time trigger"...

as far as i know 1.4.4 is testnet

[malafaya]

as far as i know 1.4.4 is testnet

We have had the updates in place. We are ready to get the fix on the main chain rolling and hence the new wallet.

v1.4.4

Emphasis is mine.
I'm sure most pools already upgraded. Confirmations?

EDIT: Check rewards in https://xmg.minerclaim.net/index.php?page=statistics&action=blocks

[abbeytim]

i see hopefully joe will give us an update

[seeksilence]

Just temporarily disabled payout. Do not know if xmgpool is on the right track now.
Block values are 43.25 now.

No one use 1.4.4, it is for testnet. It will be released Thursday night.

[malafaya]

Just temporarily disabled payout. Do not know if xmgpool is on the right track now.
Block values are 43.25 now.

No one use 1.4.4, it is for testnet. It will be released Thursday night.

It's thursday night for me already .
Binaries will be released tonight. Source code already made available per Joe's post, to those willing to compile.
At least, this is what I understood earliler today.

[My9bot]

Not sure what you're trying to show. Your wallet is still v1.4.3.1. Check the reward in this block: https://chainz.cryptoid.info/xmg/block.dws?1479159.htm
The new v1.4.4 is supposed to return to old rewards tomorrow night, but I can already see new blocks with rewards of 30 XMG, probably because pools already upgraded and there's something wrong with the "time trigger"...

i think you a right there is a bug in 1.4.4

https://github.com/magi-project/magi/blob/10395ede0b3a68e5aa95f524d0f3550ed918fb52/src/main.cpp#L1074

[Pool42]

As large blocks are falling, Pool42 has disabled its payouts temporarily.
Don't worry it shall be back soon enough when we are sure blocks are effectively valid.

[ex33s]

Not sure what you're trying to show. Your wallet is still v1.4.3.1. Check the reward in this block: https://chainz.cryptoid.info/xmg/block.dws?1479159.htm
The new v1.4.4 is supposed to return to old rewards tomorrow night, but I can already see new blocks with rewards of 30 XMG, probably because pools already upgraded and there's something wrong with the "time trigger"...

i think you a right there is a bug in 1.4.4

https://github.com/magi-project/magi/blob/10395ede0b3a68e5aa95f524d0f3550ed918fb52/src/main.cpp#L1074

Could you explain it a bit more why you think there's a bug on that return statement?

[malafaya]

i think you a right there is a bug in 1.4.4

https://github.com/magi-project/magi/blob/10395ede0b3a68e5aa95f524d0f3550ed918fb52/src/main.cpp#L1074

Not sure about that specific line but this https://github.com/magi-project/magi/commit/10395ede0b3a68e5aa95f524d0f3550ed918fb52#diff-7ec3c68a81efff79b6ca22ac1f1eabba postpones some threshold heights up in v1.4.4, so at block 1478500, both 1.4.3.1 and 1.4.4 started having different params (and probably a fork would be likely).