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

[111magic]

xmg.suprnova.cc DEAD?!

Too much forking going on currently, I've lost a lot of coins. I'll reopen once the forking is fixed

Thanks for the info Ocminer. Magi will keep you informed about this & futher developments/improvements

[111magic]

To ALL,

The fork takes place from one pool to another, and that I believe something fundamental needs a clarification as we haven't seen this before. This has messed around the mining. I suggest stop mining at this time until we firstly 1) get a keep-it-going solution, and 2) root cause finding and a solution to the fork. The mining just going on, unfortunately, doesn't make sense to me, and I would propose a rollover back to a fair point. Let me know if rollover sounds good to you, and where you want to startover.

I think many would agree that our goal is to get Magi back to stable coin. If rollover back is necessary, so let's perform this. About point - if rollover purpose is to remove some unfair block(s) so let's choose the last fair block before first unfair one in straight chain in order to minimize the loss.

I agree with those words!

Do not forget coins have been rolling out to exchanges and being sold. If you rollback ("edit") the blockchain hard enough, exchanges will get back on Magi, as they will lose those funds already sold, and eventually delist XMG... I've seen this happen at Cryptopia for another coin.

At one point - delist, at the other one - re-delist. Looks like we should choose between bad option (rollback) and very bad option (fair chain absence at all). Or maybe I'm wrong and situation not so bad? If no, I think I have no doubts which one to choose.

Hmm its not a easy desicion.
We have look at different consequences for Magi, miners, holders, exchanges etc.
Rollback or new XMG with coinswap there are many different options.
The whole idea about Magi is very good. If we work together we can make a difference in cryptoworld.

Think we us about the options & share ideas!

[Boocha466]

It is necessary to do a rollback and kill all the blocks that hung in the astral. If even 1 block remains, we will return to this problem! Since a drop of fuel oil will ruin the barrel of honey.

I think that all who want a coin to live will understand the consequences. But just as sure that if everything goes smoothly we can catch up with this moment and become even stronger.

Sorry for my english! 

[eogr-s]

To ALL,

The fork takes place from one pool to another, and that I believe something fundamental needs a clarification as we haven't seen this before. This has messed around the mining. I suggest stop mining at this time until we firstly 1) get a keep-it-going solution, and 2) root cause finding and a solution to the fork. The mining just going on, unfortunately, doesn't make sense to me, and I would propose a rollover back to a fair point. Let me know if rollover sounds good to you, and where you want to startover.

I think many would agree that our goal is to get Magi back to stable coin. If rollover back is necessary, so let's perform this. About point - if rollover purpose is to remove some unfair block(s) so let's choose the last fair block before first unfair one in straight chain in order to minimize the loss.

I agree with those words!

Do not forget coins have been rolling out to exchanges and being sold. If you rollback ("edit") the blockchain hard enough, exchanges will get back on Magi, as they will lose those funds already sold, and eventually delist XMG... I've seen this happen at Cryptopia for another coin.

At one point - delist, at the other one - re-delist. Looks like we should choose between bad option (rollback) and very bad option (fair chain absence at all). Or maybe I'm wrong and situation not so bad? If no, I think I have no doubts which one to choose.

Hmm its not a easy desicion.
We have look at different consequences for Magi, miners, holders, exchanges etc.
Rollback or new XMG with coinswap there are many different options.
The whole idea about Magi is very good. If we work together we can make a difference in cryptoworld.

Think we us about the options & share ideas!

So let me express you my support
To you, to Joe and to other Magi developers.
I hope Magi will keep growing and I believe we overcome this point

[oxothuk]

To developer:

Don`t try made agreement with everyone of forum,  do as u think be better and done it.
You never agree to stop mining, because 99 will agree and one will start mining while difficulty so low and revenue so big.

Just do what u want and don`t listen us

[111magic]

To ALL,

The fork takes place from one pool to another, and that I believe something fundamental needs a clarification as we haven't seen this before. This has messed around the mining. I suggest stop mining at this time until we firstly 1) get a keep-it-going solution, and 2) root cause finding and a solution to the fork. The mining just going on, unfortunately, doesn't make sense to me, and I would propose a rollover back to a fair point. Let me know if rollover sounds good to you, and where you want to startover.

I think many would agree that our goal is to get Magi back to stable coin. If rollover back is necessary, so let's perform this. About point - if rollover purpose is to remove some unfair block(s) so let's choose the last fair block before first unfair one in straight chain in order to minimize the loss.

I agree with those words!

Do not forget coins have been rolling out to exchanges and being sold. If you rollback ("edit") the blockchain hard enough, exchanges will get back on Magi, as they will lose those funds already sold, and eventually delist XMG... I've seen this happen at Cryptopia for another coin.

At one point - delist, at the other one - re-delist. Looks like we should choose between bad option (rollback) and very bad option (fair chain absence at all). Or maybe I'm wrong and situation not so bad? If no, I think I have no doubts which one to choose.

Hmm its not a easy desicion.
We have look at different consequences for Magi, miners, holders, exchanges etc.
Rollback or new XMG with coinswap there are many different options.
The whole idea about Magi is very good. If we work together we can make a difference in cryptoworld.

Think we us about the options & share ideas!

So let me express you my support
To you, to Joe and to other Magi developers.
I hope Magi will keep growing and I believe we overcome this point

Thanks we appriciate those words!

[Vitalik_Pedik]

https://poolinfo.systms.org/#magi
2MH pow)
new day - new split)

[ex33s]

To ALL,

The fork takes place from one pool to another, and that I believe something fundamental needs a clarification as we haven't seen this before. This has messed around the mining. I suggest stop mining at this time until we firstly 1) get a keep-it-going solution, and 2) root cause finding and a solution to the fork. The mining just going on, unfortunately, doesn't make sense to me, and I would propose a rollover back to a fair point. Let me know if rollover sounds good to you, and where you want to startover.

https://poolinfo.systms.org/#magi
2MH pow)
new day - new split)

Don't think so - most have stopped mining. Read the quote above yours

[Vitalik_Pedik]

To ALL,

The fork takes place from one pool to another, and that I believe something fundamental needs a clarification as we haven't seen this before. This has messed around the mining. I suggest stop mining at this time until we firstly 1) get a keep-it-going solution, and 2) root cause finding and a solution to the fork. The mining just going on, unfortunately, doesn't make sense to me, and I would propose a rollover back to a fair point. Let me know if rollover sounds good to you, and where you want to startover.

I buy 236XMG yesterday 9LXmpBZC54DwirHEc9z5NYKwihuqaj1EHV, rollover back after this tx 25276115ba9311ddf26ecbd754abb1f5d7a169f5f2cfcec7ae6a0bc94549b26f

[Vitalik_Pedik]

The only way to avoid splitting in future is to accept and execute my suggestions:
1. Hardcode main pools in client (need list) to be guarantors of the chain, not forever. For example, we have 10 pools in list, if 7 of 10 accepted block, that block true.
2. Try to find out vector of attack (pow or pos) and develop a protection system.
3. Test protection system several times with emulation of attack
4. Remove hardcoded pools.

Without this steps, we will have new splits again and again.

just one more time)

[starmman]

The only way to avoid splitting in future is to accept and execute my suggestions:
1. Hardcode main pools in client (need list) to be guarantors of the chain, not forever. For example, we have 10 pools in list, if 7 of 10 accepted block, that block true.
2. Try to find out vector of attack (pow or pos) and develop a protection system.
3. Test protection system several times with emulation of attack
4. Remove hardcoded pools.

Without this steps, we will have new splits again and again.

just one more time)

Seems to make sense to me - from what I can see - that should keep block chain in order

[good]

The only way to avoid splitting in future is to accept and execute my suggestions:
1. Hardcode main pools in client (need list) to be guarantors of the chain, not forever. For example, we have 10 pools in list, if 7 of 10 accepted block, that block true.
2. Try to find out vector of attack (pow or pos) and develop a protection system.
3. Test protection system several times with emulation of attack
4. Remove hardcoded pools.

Without this steps, we will have new splits again and again.

just one more time)

Lovely plan mister Vitalik_Pedik

[Vitalik_Pedik]

General steps to improve stability of MAGI chain:
1. Hardcode main pools in client (need list) to be guarantors of the chain, not forever. For example, we have 10 pools in list, if 7 of 10 accepted block, that block true.
2. Try to find out vector of attack (pow or pos) and develop a protection system.
3. Test protection system several times with emulation of attack
4. Remove hardcoded pools.

Please vote for my plan:
https://twitter.com/moiseev_aa/status/899972940887994369

[ELE.ZYK]

General steps to improve stability of MAGI chain:
1. Hardcode main pools in client (need list) to be guarantors of the chain, not forever. For example, we have 10 pools in list, if 7 of 10 accepted block, that block true.
2. Try to find out vector of attack (pow or pos) and develop a protection system.
3. Test protection system several times with emulation of attack
4. Remove hardcoded pools.

Please vote for my plan:
https://twitter.com/moiseev_aa/status/899971624795070464

want to vote ,but need twitter account , sad . i vote here here ,support!

[jcreyesb]

.... so? .. this currency really is interesting and is very important to rookie miners, and, in this moment when the GPUs are expensive, the cpu mining is a greate oportunity for new  miner... don't permit that magi died..

[edward0181]

I'll just wait it out. Have directed all my hashing power to own server running a small stratum. So far still on same chain as poolinfo.systms.org and magi explorer. Will see what will happen. So far one block found hihi

[cryptosamuri]

General steps to improve stability of MAGI chain:
1. Hardcode main pools in client (need list) to be guarantors of the chain, not forever. For example, we have 10 pools in list, if 7 of 10 accepted block, that block true.
2. Try to find out vector of attack (pow or pos) and develop a protection system.
3. Test protection system several times with emulation of attack
4. Remove hardcoded pools.

Please vote for my plan:
https://twitter.com/moiseev_aa/status/899972940887994369

Which ever way the devs decide to go I support it as long as its best for the coin, I vote to keep the discussion on bitcoin talk and in the hands of the dev, once we start having votes here and then on twitter then somewhere else it will be come jumbled and confusing and non productive , then we will have infighting then just other bad things

[eogr-s]

General steps to improve stability of MAGI chain:
1. Hardcode main pools in client (need list) to be guarantors of the chain, not forever. For example, we have 10 pools in list, if 7 of 10 accepted block, that block true.
2. Try to find out vector of attack (pow or pos) and develop a protection system.
3. Test protection system several times with emulation of attack
4. Remove hardcoded pools.

Please vote for my plan:
https://twitter.com/moiseev_aa/status/899972940887994369

If you're not a developer than what's purport to vote or not?
Can you implement your "plan"?
Seems you just rend the air.

[111magic]

.... so? .. this currency really is interesting and is very important to rookie miners, and, in this moment when the GPUs are expensive, the cpu mining is a greate oportunity for new  miner... don't permit that magi died..

Magi will never die! No worries. Despite the issue Magi has awesome & active team and community! So Magi will see better times!

[Vitalik_Pedik]

General steps to improve stability of MAGI chain:
1. Hardcode main pools in client (need list) to be guarantors of the chain, not forever. For example, we have 10 pools in list, if 7 of 10 accepted block, that block true.
2. Try to find out vector of attack (pow or pos) and develop a protection system.
3. Test protection system several times with emulation of attack
4. Remove hardcoded pools.

Please vote for my plan:
https://twitter.com/moiseev_aa/status/899972940887994369

If you're not a developer than what's purport to vote or not?
Can you implement your "plan"?
Seems you just rend the air.

I am developer with +10 years experience.
I know that at least first and last step easy to realize.