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

[bfons]

As I received many requests of no-rollback and also many posts here, we will take the majority that we will go on with the chain on 104.128.225.215 as is, NO ROLLBACK. However, I strongly believe the PoW reward needs a reset at this mode before fix is released in the near future, and the number I have in mind is maximum 15 XMG / block. This is a temporary solution so that we keep chain / mining going. I temporarily shut the node down until we make release of the wallet. Please be prepare for the mining which can be done through solo mining. Please ask if you have questions of starting up solo mining. In the meantime, we seek pools like NOMP; few people present help on NOMP. I appreciate this.

 

I was working on a NOMP node but am not finding that it supports M7M.  Anybody else here running a NOMP node for MAGI?

can always ask me. I have nomp node running on Magi.

PMs a coming ;-)

[1715427034]

1715427034

[1715427034]

1715427034

[drgauravxmg]

hi all
My wallet stop syncing and says total 931 blocks left about 2 hours.

clearing connect line didn't solve.
Any idea to solve that?
Ver = 1.4.1.1

Update your wallet to 1.4.3.

Check few older posts for the latest link.

[111magic]

Wallet v1.4.3:

Windows: http://coinmagi.org/bin/m-wallet-1.4.3/m-wallet-1.4.3-win.zip
Linux (32 & 64): http://coinmagi.org/bin/m-wallet-1.4.3/m-wallet-1.4.3-linux.tar.gz
OS X: http://coinmagi.org/bin/m-wallet-1.4.3/m-wallet-1.4.3-osx.zip
Github: https://github.com/magi-project/magi

magi.conf:

Code:

rpcuser=rpcuser
rpcpassword=rpcpass

rpcport=8232

rpcallowip=127.0.0.1

listen=0
connect=104.128.225.215

Blockchain download (#1451225):

http://coinmagi.org/bin/block-chain/

Solo mining:

http://m-core.org/solo-mine-magi/


[Edit]

PoW Block reward: 30% of normal value for temporary and back to normal after the fix is fully done
PoS rewards: 20% more also temporarily and back to normal after the fix is fully done

Links again!

[jcreyesb]

Wallet v1.4.3:

Windows: http://coinmagi.org/bin/m-wallet-1.4.3/m-wallet-1.4.3-win.zip
Linux (32 & 64): http://coinmagi.org/bin/m-wallet-1.4.3/m-wallet-1.4.3-linux.tar.gz
OS X: http://coinmagi.org/bin/m-wallet-1.4.3/m-wallet-1.4.3-osx.zip
Github: https://github.com/magi-project/magi

magi.conf:

Code:

rpcuser=rpcuser
rpcpassword=rpcpass

rpcport=8232

rpcallowip=127.0.0.1

listen=0
connect=104.128.225.215

Blockchain download (#1451225):

http://coinmagi.org/bin/block-chain/

Solo mining:

http://m-core.org/solo-mine-magi/


[Edit]

PoW Block reward: 30% of normal value for temporary and back to normal after the fix is fully done
PoS rewards: 20% more also temporarily and back to normal after the fix is fully done

Links again!

Do you recomended solo mining??

[111magic]

I'd mention that the release just posted is a temporary solution to keep the chain and mining going, not a FIX. We'll make efforts on the 2nd step of getting a fix ASAP.

For this reason, I recommend do not ask exchanges to bring up the wallet, and when possible place least tickets regarding the issues. We apologize for the trouble. What I'm saying is that we'd be aware of minimizing exchanges' efforts on this incident, or we end up a high probability of worse situation.

At this point, again I recommend keeping exchange wallet in maintenance mode until a final FIX is out.

Second step will follow!

[maxeprom]

Nah, it's forked again.
Because of those insane debil and retarded people with 5000KH\s.

newbie question: why would a miner with high powerhash could make a fork?

I don't know how to explain it to you, I am not a developer, but if you read the last 20 pages, you see that devs advised not to put insane hashrates.
It's sure that the algo have some kind of bug, but everything went fine, then those 2 debils put 5000 on the pool, and then the coin forked, AGAIN. Also if one pool have 50% of MH +1MH, it's not good, because it controls the network and the transactions then. It's called 50 + 1 attack.

I must call out those 2 with insane hash rates, because it's clear that they are taking block rewards from everyone. It's pure douchebaggery. Nothing else.

It would be nice to have more details on it. I'm quite sure it should be a kind of bug that the magi devs should keep an eye.
Note that minerclaim got *behind* the other 2 pools, yet having almost 70% of the total hashrate.

On other coins already happend that a pool got high power, but won't do a fork so easily.

[erhanzeynel]

Thank you so much amigo for re posting  
I missed that when I was at work.

[111magic]

Thank you so much amigo for re posting 

You are welcome.
Edit: Our dev Joe has almost weekend & will look into it again.

[erhanzeynel]

Thank you so much amigo for re posting  

You are welcome.
Edit: Our dev Joe has almost weekend & will look into it again.

Those thaft days not our first.  

We did and will do again.
Magi will solve that too with that great community

[malafaya]

Nah, it's forked again.
Because of those insane debil and retarded people with 5000KH\s.

newbie question: why would a miner with high powerhash could make a fork?

I don't think it has to do with high hashrate.
Some days ago, while exclusively connected to the dev's peer (104.x.x.x), my wallet forked on its own mining at a rate of just 11 kh/s...

[ex33s]

Guys, is this okay?

That's not ok, working on fixing it...

https://poolinfo.systms.org is in sync again

[malafaya]

https://poolinfo.systms.org is in sync again

Do you connect exclusively to the main peer, and does your wallet mine or stake?
Just trying to figure out some clues to the fork.

[The Frisian]

https://poolinfo.systms.org is in sync again

Nice, well done!
Does this mean there's only something wrong at minerclaim?
At the other pools the reward is getting up.
Please let the big ones stay at minerclaim on the wrong chain.
Am I right?

[nsummy]

I posted earlier this morning that I thought something was wrong at minerclaim.  Their total hashrate is somehow not all going to the network.  I don't know how that is possible but the numbers don't add up.  I wouldn't worry about this coin forking again, if it does, the people mining on the wrong fork have no one to blame but themselves.  Its been decided what node decides the proper chain.

[DisasterFaster]

Noticed the solo mining info on the latest wallet update links and now I'm curious is anybody having any luck mining this coin solo with CPU?

I've only seen a couple of coins that could actually be solo mined with a cpu and would be very interested in mining XMG if it was in fact a decent option!

[coolestcool]

Minerclaim looks like on fork again  

By the way, theres looks like a insane hashrates in solo mining too

[jcreyesb]

Noticed the solo mining info on the latest wallet update links and now I'm curious is anybody having any luck mining this coin solo with CPU?

I've only seen a couple of coins that could actually be solo mined with a cpu and would be very interested in mining XMG if it was in fact a decent option!

I mining solo, but today nothing mined.... i have 4 PC on my local network, but today i don't luck

[DisasterFaster]

Noticed the solo mining info on the latest wallet update links and now I'm curious is anybody having any luck mining this coin solo with CPU?

I've only seen a couple of coins that could actually be solo mined with a cpu and would be very interested in mining XMG if it was in fact a decent option!

I mining solo, but today nothing mined.... i have 4 PC on my local network, but today i don't luck

@jcreyesb thanks for the reply! Are you cpu mining and if so what processor are you using?

[111magic]

I posted earlier this morning that I thought something was wrong at minerclaim.  Their total hashrate is somehow not all going to the network.  I don't know how that is possible but the numbers don't add up.  I wouldn't worry about this coin forking again, if it does, the people mining on the wrong fork have no one to blame but themselves.  Its been decided what node decides the proper chain.

Think you said some right words! Well done

[The Doktor]

Hi, I'm tying to solo mine with a few computers on my local network. How do I know if the wallet is receiving the hashes?