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

[starmman]

Right Cryptonit. Magi team will no give up.
Dev is doing a great job at the moment.
And I honesty think that with the improvements, our awesome community, new campaigns, the nice & stable value of XMG, Magi will have a great future!

Good to hear - Magi has an awesome, active community!

[1714824393]

1714824393

[1714824393]

1714824393

[1714824393]

1714824393

[111magic]

Right Cryptonit. Magi team will no give up.
Dev is doing a great job at the moment.
And I honesty think that with the improvements, our awesome community, new campaigns, the nice & stable value of XMG, Magi will have a great future!

Good to hear - Magi has an awesome, active community!

 

[nodecoin5]

Right Cryptonit. Magi team will no give up.
Dev is doing a great job at the moment.
And I honesty think that with the improvements, our awesome community, new campaigns, the nice & stable value of XMG, Magi will have a great future!

Good to hear - Magi has an awesome, active community!

community will not help if magi will be delisted from polo

[111magic]

Right Cryptonit. Magi team will no give up.
Dev is doing a great job at the moment.
And I honesty think that with the improvements, our awesome community, new campaigns, the nice & stable value of XMG, Magi will have a great future!

Good to hear - Magi has an awesome, active community!

community will not help if magi will be delisted from polo

I don't understand you're line?
Did I miss something? I don't see a warning or received a message about polo delisting Magi.
??

------------------------------------------

------------------------------------------
No worries all!
Magi is save on polo!

[111magic]

Magi is up again! 

[goldlabel]

I would love to, but according to my schedule for the following week, ill be very busy too.  I hope someone from the community step up and volunteer to organize this Signature Campaign Idea for XMG.   This will promote XMG to other thread of Bitcointalk.org.

And this is THE problem with XMG. So many good thoughts so little time.
The only way to save XMG from going to 100 sat would be a well paid team with good programmers and marketing guys.
Otherwise I assume the end will come very soon, because the coin will be removed from all exchanges.
But with a marketcap of nearly 50.000 there will be no money for a well paid team.

Well, end is WE GAVE IT UP.

Magi never give up!!!!

[joelao95]

Right Cryptonit. Magi team will no give up.
Dev is doing a great job at the moment.
And I honesty think that with the improvements, our awesome community, new campaigns, the nice & stable value of XMG, Magi will have a great future!

Good to hear - Magi has an awesome, active community!

community will not help if magi will be delisted from polo

I don't understand you're line?
Did I miss something? I don't see a warning or received a message about polo delisting Magi.
??

------------------------------------------

------------------------------------------
No worries all!
Magi is save on polo!

He means community won't be help if polo decided to delist, suppose. 

[IMJim]

Right Cryptonit. Magi team will no give up.
Dev is doing a great job at the moment.
And I honesty think that with the improvements, our awesome community, new campaigns, the nice & stable value of XMG, Magi will have a great future!

Good to hear - Magi has an awesome, active community!

community will not help if magi will be delisted from polo

I don't understand you're line?
Did I miss something? I don't see a warning or received a message about polo delisting Magi.
??

------------------------------------------

------------------------------------------
No worries all!
Magi is save on polo!

He means community won't be help if polo decided to delist, suppose. 

He means he didn't understand the comment as there's been no supposed threat of Polo de-listing, suppose:-)

[starmman]

Great picture goldlabel! Hope you are well.

[starmman]

All Altcoins seem to be doing very well this morning, 10-20% increase on BTC on almost all of them =)

[goldlabel]

Great picture goldlabel! Hope you are well.

Im doing great starmman, thx

[111magic]

Right Cryptonit. Magi team will no give up.
Dev is doing a great job at the moment.
And I honesty think that with the improvements, our awesome community, new campaigns, the nice & stable value of XMG, Magi will have a great future!

Good to hear - Magi has an awesome, active community!

community will not help if magi will be delisted from polo

I don't understand you're line?
Did I miss something? I don't see a warning or received a message about polo delisting Magi.
??

------------------------------------------

------------------------------------------
No worries all!
Magi is save on polo!

He means community won't be help if polo decided to delist, suppose. 

He means he didn't understand the comment as there's been no supposed threat of Polo de-listing, suppose:-)

Ah ok. That might be it!

[111magic]

Great picture goldlabel! Hope you are well.

Im doing great starmman, thx

Awesome Goldlabel and Congrats with your birthday!

[111magic]

New wallet will be released in few days/hours!

[goldlabel]

Thx Magic,

Like us and have a chance to win 1000 xmg, but your walletadress on the topic at Facebook.

[keepall]

This is a great coin, but the bitcoin price is crazy by now.

Don't worry, everything is going to be ok

[joelao95]

Updates (06/22/2016):

New wallet 1.3.0rc1 available:

Download link: http://coinmagi.org/bin/m-wallet-1.3.0rc1/
(I'll fulfill OSX compiling, TBD)

Source: https://github.com/magi-project/magi/tree/1.3.0rc

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

Release notes: http://coinmagi.org/bin/release-notes.md

Changelog:
# Changed database for storing transaction and block indices from Berkeley DB to LevelDB;
# Enabled block hash storing in storage and loaded directly from disk;
# Fixed "Checkpoint is too old" warning
# PoS stake splitting and combining features, which can be set by stakesplitthreshold=VALUE and stakecombinethreshold VALUE in magi.conf, or by RPC commands: setstakesplitthreshold and setstakecombinethreshold; RPC commands getstakesplitthreshold and getstakecombinethreshold to show their current values;
# Added price information on Qt Overviewpage;
# Qt wallet logo change and GUI improvements;
# Merge pull request of version check updates by feldenthorne; fixed automatic version check including test/rc versions.
# Merge pull request of adding total balance in "Transactions" page by lightsplasher;

Thanks to feldenthorne and lightsplasher for the contributions to the code base and sorry for the long-delayed merge. I am supposed to respond to the pull request significantly fast from now on. If anyone is able to make changes to source, please.

Note 1:
We are changing to leveldb for block index storing. For this purpose, we suggest use of the new wallet in limited occasions. This is the reason of the RC version, though I didn't see any issue in my own side. At this moment, I DON'T recommend using the wallet in your minings, pool server, or exchanges. In my estimate about two weeks long without having any issues coming up, we will roll out a stable release.  

Note 2:
Due to change to leveldb data, you have to get rid of the old version of block data before using the new client. To save the time, I have pulled out an up-to-date block chain which can be downloaded from here: http://coinmagi.org/bin/block-chain/

A bit concern of stake splitting & combing in original ppc design since it involves security concerns:
https://github.com/magi-project/magi/blob/1.3.0rc/src/wallet.cpp#L1595

Code:

                // The original design prevents stakes having the same parent transaction from combining
                // which somehow reads as encouraging splitting (improve security);
                // This mechanism is to be disabled in Magi since combining won't cause security concern 

                /* Splitting is only enforced at wallet, not by PoS protocol as well as consensus over network.
                 * Original PPCoin design encourages splitting as per "Lower coinstake combine threshold to
                 * improve security", which can be understood by the fact that in general PoS, with a large
                 * number of coins in stake comes greater chance of (PoS) mining blocks. This is not going to 
                 * happen in Magi. Also, hardening nStakeCombineThreshold is impractical since an advanced user 
                 * can easilly make a change to that and rebuild a wallet. The change to nStakeCombineThreshold 
                 * should be available externally, e.g., RPC command, magi.conf configuration file. 
                 ** Magi, for optimum staking, nStakeCombineThreshold should be used in combination with nStakeSplitThreshold.*/

You should use nStakeCombineThreshold along with nStakeSplitThreshold for best results. The optimum threshold is neither a random number nor as large as possible; it should be an appropriate value, say 500 XMG, according to MAGI's PoS protocol.  

Update procedure:
1) Backup wallet.dat to a safe place;
2) Delete everything under the Magi or .magi folder except wallet.dat;
3) Download block chain from here http://coinmagi.org/bin/block-chain/ and unzip the fille;
4) Unzip all of the stuffs under the folder m-blockchain into Magi or .magi;
5) Start up the new wallet.

At the last minute when I compiled the wallet in windows, the price info on the new wallet in Windows seems not working, though it all worked out in my linux machine; we'll fix it in the final version.

I guess this is it.

I'll talk more most likely tomorrow night.

[lionheart78]

Updates (06/22/2016):

New wallet 1.3.0rc1 available:

Download link: http://coinmagi.org/bin/m-wallet-1.3.0rc1/
(I'll fulfill OSX compiling, TBD)

Source: https://github.com/magi-project/magi/tree/1.3.0rc

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

Release notes: http://coinmagi.org/bin/release-notes.md

Changelog:
# Changed database for storing transaction and block indices from Berkeley DB to LevelDB;
# Enabled block hash storing in storage and loaded directly from disk;
# Fixed "Checkpoint is too old" warning
# PoS stake splitting and combining features, which can be set by stakesplitthreshold=VALUE and stakecombinethreshold VALUE in magi.conf, or by RPC commands: setstakesplitthreshold and setstakecombinethreshold; RPC commands getstakesplitthreshold and getstakecombinethreshold to show their current values;
# Added price information on Qt Overviewpage;
# Qt wallet logo change and GUI improvements;
# Merge pull request of version check updates by feldenthorne; fixed automatic version check including test/rc versions.
# Merge pull request of adding total balance in "Transactions" page by lightsplasher;

Thanks to feldenthorne and lightsplasher for the contributions to the code base and sorry for the long-delayed merge. I am supposed to respond to the pull request significantly fast from now on. If anyone is able to make changes to source, please.

Note 1:
We are changing to leveldb for block index storing. For this purpose, we suggest use of the new wallet in limited occasions. This is the reason of the RC version, though I didn't see any issue in my own side. At this moment, I DON'T recommend using the wallet in your minings, pool server, or exchanges. In my estimate about two weeks long without having any issues coming up, we will roll out a stable release.  

Note 2:
Due to change to leveldb data, you have to get rid of the old version of block data before using the new client. To save the time, I have pulled out an up-to-date block chain which can be downloaded from here: http://coinmagi.org/bin/block-chain/

A bit concern of stake splitting & combing in original ppc design since it involves security concerns:
https://github.com/magi-project/magi/blob/1.3.0rc/src/wallet.cpp#L1595

Code:

                // The original design prevents stakes having the same parent transaction from combining
                // which somehow reads as encouraging splitting (improve security);
                // This mechanism is to be disabled in Magi since combining won't cause security concern 

                /* Splitting is only enforced at wallet, not by PoS protocol as well as consensus over network.
                 * Original PPCoin design encourages splitting as per "Lower coinstake combine threshold to
                 * improve security", which can be understood by the fact that in general PoS, with a large
                 * number of coins in stake comes greater chance of (PoS) mining blocks. This is not going to 
                 * happen in Magi. Also, hardening nStakeCombineThreshold is impractical since an advanced user 
                 * can easilly make a change to that and rebuild a wallet. The change to nStakeCombineThreshold 
                 * should be available externally, e.g., RPC command, magi.conf configuration file. 
                 ** Magi, for optimum staking, nStakeCombineThreshold should be used in combination with nStakeSplitThreshold.*/

You should use nStakeCombineThreshold along with nStakeSplitThreshold for best results. The optimum threshold is neither a random number nor as large as possible; it should be an appropriate value, say 500 XMG, according to MAGI's PoS protocol.  

Update procedure:
1) Backup wallet.dat to a safe place;
2) Delete everything under the Magi or .magi folder except wallet.dat;
3) Download block chain from here http://coinmagi.org/bin/block-chain/ and unzip the fille;
4) Unzip all of the stuffs under the folder m-blockchain into Magi or .magi;
5) Start up the new wallet.

At the last minute when I compiled the wallet in windows, the price info on the new wallet in Windows seems not working, though it all worked out in my linux machine; we'll fix it in the final version.

I guess this is it.

I'll talk more most likely tomorrow night.

Great work there XMG Dev, I'm still waiting for 111magic reply so i can finalize the calculation of the upcoming campaign.  Hopefully we can pull lots of interest toward XMG in this campaign.

[PetATL]

Thanks for new wallet running great can you upload somewhere magi.conf or what I have write inside.

[starmman]

Great, I'll test it out in a few days time =)
Thanks for your hard work