Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 434. (Read 2375995 times)

Mac Mini late 2013, 29khs each, i think is the first i5 generation

Okay, can you list the hashrate on each mac model? would be nice thanks

In fact I have 8 old Mac mining

what cpu do you use to get those speeds?

Just publish a post on my blog, https://www.minandoando.com/como-minar-magi-xmg/, is for spanish talking miners... hope help you to start mining.

http://104.207.149.217/

Another pool on a forked chain. Right now just PoM M-Hash is on the right chain.

https://poolinfo.systms.org/ is back now.

@Yate, I understand now  65.58 Mh/s was the net hashrate :-)

By the way, from where is coming all this hash power? only two pools report activities:

xmgpool
xmgpool
Hashrate   2.20 Mh/s
Workers   52
Efficiency   99.69%
 
Last found block   1449781
Network block   1449900

 PoM Pool
PoM Pool
Hashrate   25.36 Mh/s
Workers   487
Efficiency   99.56%
 
Last found block   1449897
Network block   1449900

that is far from the total

Coin of Magi
Version   v1.4.2.0
Money supply   7,227,927.68
Hashrate   65.39 Mh/s
Last Block   1449902
Peers   75
Download blockchain @ Block 1448324
Zip - Tar.gz

Just for the record, I have the feeling it's PoS that causes the fork... I've seen more hybrid/PoS coins having this kind of unexplained problems than pure PoWs. And seeing the printscreen that someone recently posted [EDIT: https://bitcointalksearch.org/topic/m.21041520 ], with tens of stakes in a couple of minutes makes my belief stronger.


---

I think you are right.  I think the reason its hard to track down is because the dev is searching the proof of mining side and its probably the staking that is causing the issue.  Why not put staking on pause for now and see what happens?  I bet the chain will stabalize....

You can then run a private staking until the forking stops when you figure out what its problem is while mining continues.  That way everyone is for the most part happy with the outcome.  I do not agree to ceasing mining at all.  I enjoy the fact that the paranoia has cleared the pools so now I can get a decent cut of the payouts, before this I did not feel like i was, I am enjoying the outcome....so I don't feel at all like stopping the pools and stopping POM. 

I suggest pausing the staking, backing up the age of all the coins, and then updating the age when its time to reintegrate it with the staking database to update it and pay out profits on the wallets that are due them for the time staking was shut down when it goes back online once bug-hunting is done.

Enoch

Trying to resolve it with google public dns, I get this:

213.32.21.37

Tryning to connect to this ip in https get me to a page about Zimbra asking for a logging:

"Zimbra

Username:   
Password:   
     Stay signed in Sign In
Version:   
 What's This?
Zimbra :: the leader in open source messaging and collaboration :: Blog - Wiki - Forums
Copyright © 2005-2016 Synacor, Inc. All rights reserved. "Zimbra" is a registered trademark of Synacor, Inc."

At the same time, net hashrate just doubled!

@Yate, how to you get 65.58 Mh/s?

Is working fine

Version   v1.4.2.0
Money supply   7,227,572.97
Hashrate   65.58 Mh/s
Last Block   1449884
Peers   72

The wallet doesn't get much easier.  It has the same look and feel as almost every other wallet.  Download the latest version here:  http://coinmagi.org/bin/m-wallet-1.4.2/m-wallet-1.4.2-win.zip  

zpool also down and XMG missing from their website.


all the last few hours mining there is gone.......

Is https://poolinfo.systms.org/ down?

dns cannot resolve it anymore on my side.

As many of the community is having issues with the blockchain and mining... i'm assuming my basic level of computing won't be enough to set up the wallet the correct way.

Is there a realistic timeframe when a more user friendly wallet will be implemented?

I had sent a few coins from bittrex to test the wallet and realized the chain is way behind in syncing.  I'm assuming my coins are gone, that's okay it's only a few. The future of this coin still excites me... i just feel like I'm over my head when reading "simple" code changes to update the wallet files on my own.  There doesn't seem to be a concrete place to find answers.

I had posted the following a few days back, but the overall community is having many issues themselves and new hodlers like myself have issues that are just basic compared to the mining issues others are having.

"Hello Magi community!

I love the community behind this coin... although most of this "basic" coding is above my head I have been trying to sync the wallet.

As I'm reading, its obvious updates are coming out often.  I tested out the Magi Core version v1.3.1.0 (64-bit) and it is not synced, as i've been reading we should do some changes with the coding?  I put that on the back burner for a few days after I sent a few coins to the wallet from bittrex to test the wallet.  Of course they haven't shown up because its far behind on the chain.

Will downloading the newest wallet help me with this matter?

Should a noob such as me wait for some time until the wallet becomes better suited for someone as remedial as myself?  Cheesy

Kind regards!"

Try it!

1.4.2 not synching

any additional nodes?

Some one can help me to fix the wallet sync on macOS?

4.1.1

what version? mine is not synching

...and POM hashrate doubled...