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

[Vasyanich]

Has anyone problems like this?

Code:

[2017-08-22 17:26:26] Stratum connection failed: Failed to connect to xmg.maxminers.net port 7127: Connection refused
[2017-08-22 17:26:26] ...retry after 30 seconds

[1714701367]

1714701367

[1714701367]

1714701367

[1714701367]

1714701367

[edward0181]

Has anyone problems like this?

Code:

[2017-08-22 17:26:26] Stratum connection failed: Failed to connect to xmg.maxminers.net port 7127: Connection refused
[2017-08-22 17:26:26] ...retry after 30 seconds

Yes, all main pools are ofline.

[bishs]

why is this coin dropping so much?

[The Frisian]

why is this coin dropping so much?

Price around 5000 sat now, a week ago around 3500 sat!
Only a few pumps inbetween....

[bishs]

As much as I want to support the coin.. I lost too much.

[nsummy]

My 2 cents:  There should only be a rollback if its necessary to fix a technical problem that caused this.  You can talk about fairness until you are blue in the face but I think some of the blame here is misguided;  If you mined for 2 days on the wrong fork, the pool is the one at fault, not the Magi developer.  It was obvious on Sunday at Zpool that something was not right when it was finding almost every block.  If it sounds too good to be true, it probably is.  Same goes with Suprnova.  When you mine through a pool you are taking a risk that you won't get paid, your hashrate isn't correct, etc.  Zpool and Suprnova continued to have high hashrates all day yesterday when it was completely obvious they were on the wrong chain.  Unfortunately I think the human nature of greed took over and everyone starting mining there because the returns were insane.  It seems like a lot of other complaints on here are dealing with payments from those pools.

I'm not an expert but it seemed pretty obvious what to do yesterday if you wanted to mine:  Use a pool that was on the correct fork, and make sure your wallet is on the correct fork.  https://poolinfo.systms.org/ pretty much showed that PoM was the only pool operating on the correct fork.  It was no surprise that I was able to mine on it all yesterday and receive my earnings with zero issues.  My wallet wasn't syncing past a certain block so I followed the simple solution that was posted here numerous times to put the connect command into my conf file. Problem solved. It also blows my mind that people were trying to send coins to Bittrex when they were having known problems.  In my humble opinion, most people mining to these pools with extreme returns were either burying their heads in the sand or were engaging in pure speculation.

The main issue though with a rollback though is what happens if this happens again?  Another rollback?  Its a slippery slope to go down, especially when you try to determine what is "fair."

[penambang]

I see XMG extracted by P2Pool on chainz block explorer, but can't find any p2pool source for magi. Anyone know?

[edward0181]

That is the reason why I've send all my miners to my own wallet and created my own small pool to just keep mining. Don't care if it's going to be roll back or not. My wallets are on same chain as https://chainz.cryptoid.info/xmg/ and https://poolinfo.systms.org/ and I can see found blocks confirmed and created.

Will see what will happen.
Either way, feel free to use mine as long as it will keep running...
http://h2701744.stratoserver.net:85/

[ex33s]

My 2 cents:  There should only be a rollback if its necessary to fix a technical problem that caused this.  You can talk about fairness until you are blue in the face but I think some of the blame here is misguided;  If you mined for 2 days on the wrong fork, the pool is the one at fault, not the Magi developer.  It was obvious on Sunday at Suprnova that something was not right when it was finding almost every block.  If it sounds too good to be true, it probably is.  Same goes with Suprnova.  When you mine through a pool you are taking a risk that you won't get paid, your hashrate isn't correct, etc.  Zpool and Suprnova continued to have high hashrates all day yesterday when it was completely obvious they were on the wrong chain.  Unfortunately I think the human nature of greed took over and everyone starting mining there because the returns were insane.  It seems like a lot of other complaints on here are dealing with payments from those pools.

I'm not an expert but it seemed pretty obvious what to do yesterday if you wanted to mine:  Use a pool that was on the correct fork, and make sure your wallet is on the correct fork.  https://poolinfo.systms.org/ pretty much showed that PoM was the only pool operating on the correct fork.  It was no surprise that I was able to mine on it all yesterday and receive my earnings with zero issues.  My wallet wasn't syncing past a certain block so I followed the simple solution that was posted here numerous times to put the connect command into my conf file. Problem solved. It also blows my mind that people were trying to send coins to Bittrex when they were having known problems.  In my humble opinion, most people mining to these pools with extreme returns were either burying their heads in the sand or were engaging in pure speculation.

The main issue though with a rollback though is what happens if this happens again?  Another rollback?  Its a slippery slope to go down, especially when you try to determine what is "fair."

And my 2 cents on rollback, it dosen't matter if we do a rollback if the cause of the forks is unknown. A rollback won't do anything good since the problem will present itself again.

[Vitalik_Pedik]

I can provide 3 static ip for nodes with up to 5000 connections, and can link each with other. After hardcoding those ip in new version of wallet we can forget about splitting.
Chain will work correct and dev can calmly solve problem with splitting.
Hardcoding need to avoid connect to potential wrong nodes.
Simple rollover back is not solve anything.

[Lightsplasher]

My 2 cents:  There should only be a rollback if its necessary to fix a technical problem that caused this.  You can talk about fairness until you are blue in the face but I think some of the blame here is misguided;  If you mined for 2 days on the wrong fork, the pool is the one at fault, not the Magi developer.  It was obvious on Sunday at Suprnova that something was not right when it was finding almost every block.  If it sounds too good to be true, it probably is.  Same goes with Suprnova.  When you mine through a pool you are taking a risk that you won't get paid, your hashrate isn't correct, etc.  Zpool and Suprnova continued to have high hashrates all day yesterday when it was completely obvious they were on the wrong chain.  Unfortunately I think the human nature of greed took over and everyone starting mining there because the returns were insane.  It seems like a lot of other complaints on here are dealing with payments from those pools.

I'm not an expert but it seemed pretty obvious what to do yesterday if you wanted to mine:  Use a pool that was on the correct fork, and make sure your wallet is on the correct fork.  https://poolinfo.systms.org/ pretty much showed that PoM was the only pool operating on the correct fork.  It was no surprise that I was able to mine on it all yesterday and receive my earnings with zero issues.  My wallet wasn't syncing past a certain block so I followed the simple solution that was posted here numerous times to put the connect command into my conf file. Problem solved. It also blows my mind that people were trying to send coins to Bittrex when they were having known problems.  In my humble opinion, most people mining to these pools with extreme returns were either burying their heads in the sand or were engaging in pure speculation.

The main issue though with a rollback though is what happens if this happens again?  Another rollback?  Its a slippery slope to go down, especially when you try to determine what is "fair."

And my 2 cents on rollback, it dosen't matter if we do a rollback if the cause of the forks is unknown. A rollback won't do anything good since the problem will present itself again.

And my 2 cents on rollback: We have already tried a rollback previously and things forked again.  As I recall there were some grumpy solo miners at that point.  I would not keep doing the same thing.  Proof of work mining is fubar and needs to be fixed.  The block chain needs to get stabilized without a rollback and we should not continue with this much longer.  I would try going to PoS only for a time until a more permanent solution can be found.  I don't know if it will work but it is better than having the issues we have at this point imho.

[Vasyanich]

Has anyone problems like this?

Code:

[2017-08-22 17:26:26] Stratum connection failed: Failed to connect to xmg.maxminers.net port 7127: Connection refused
[2017-08-22 17:26:26] ...retry after 30 seconds

Yes, all main pools are ofline.

When will it work? Have anyone some info on that subject?

[oxothuk]

When will it work? Have anyone some info on that subject?

not in near future..

[ex33s]

My 2 cents:  There should only be a rollback if its necessary to fix a technical problem that caused this.  You can talk about fairness until you are blue in the face but I think some of the blame here is misguided;  If you mined for 2 days on the wrong fork, the pool is the one at fault, not the Magi developer.  It was obvious on Sunday at Suprnova that something was not right when it was finding almost every block.  If it sounds too good to be true, it probably is.  Same goes with Suprnova.  When you mine through a pool you are taking a risk that you won't get paid, your hashrate isn't correct, etc.  Zpool and Suprnova continued to have high hashrates all day yesterday when it was completely obvious they were on the wrong chain.  Unfortunately I think the human nature of greed took over and everyone starting mining there because the returns were insane.  It seems like a lot of other complaints on here are dealing with payments from those pools.

I'm not an expert but it seemed pretty obvious what to do yesterday if you wanted to mine:  Use a pool that was on the correct fork, and make sure your wallet is on the correct fork.  https://poolinfo.systms.org/ pretty much showed that PoM was the only pool operating on the correct fork.  It was no surprise that I was able to mine on it all yesterday and receive my earnings with zero issues.  My wallet wasn't syncing past a certain block so I followed the simple solution that was posted here numerous times to put the connect command into my conf file. Problem solved. It also blows my mind that people were trying to send coins to Bittrex when they were having known problems.  In my humble opinion, most people mining to these pools with extreme returns were either burying their heads in the sand or were engaging in pure speculation.

The main issue though with a rollback though is what happens if this happens again?  Another rollback?  Its a slippery slope to go down, especially when you try to determine what is "fair."

And my 2 cents on rollback, it dosen't matter if we do a rollback if the cause of the forks is unknown. A rollback won't do anything good since the problem will present itself again.

And my 2 cents on rollback: We have already tried a rollback previously and things forked again.  As I recall there were some grumpy solo miners at that point.  I would not keep doing the same thing.  Proof of work mining is fubar and needs to be fixed.  The block chain needs to get stabilized without a rollback and we should not continue with this much longer.  I would try going to PoS only for a time until a more permanent solution can be found.  I don't know if it will work but it is better than having the issues we have at this point imho.

I agree with you that the chain needs to be stable first without rollback

[Vasyanich]

When will it work? Have anyone some info on that subject?

not in near future..

What happened to them??

[oxothuk]

When will it work? Have anyone some info on that subject?

not in near future..

What happened to them??

Read last 10-20 pages... forks forks. forks.

[Vitalik_Pedik]

I can provide 3 static ip for nodes with up to 5000 connections, and can link each with other. After hardcoding those ip in new version of wallet we can forget about splitting.
Chain will work correct and dev can calmly solve problem with splitting.
Hardcoding need to avoid connect to potential wrong nodes.
Simple rollover back is not solve anything.

Or we can simple buy VPS hosting for nodes, it costs 4$ month for 1 mounth for each.
C'mon, it is simpliest and 100% working solution to stabilize chain.

[Vasyanich]

When will it work? Have anyone some info on that subject?

not in near future..

What happened to them??

Read last 10-20 pages... forks forks. forks.

Is there a way to mine magi now or there's no any way?

[Vitalik_Pedik]

Is there a way to mine magi now or there's no any way?

NO WAY

[Windozxpert]

It's a shame that one of the few alt coins that are worth more than $.10 is having so many problems.