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

[integrale]

hey guys ,
i am trying to compile the new Magi version v1.4.5.2 on my ubuntu machine but i am getting an error when i am trying to execute the "gmake" .

Project MESSAGE: Building with UPNP support
Project MESSAGE: Building with IPv6 support
Project MESSAGE: Building with SSE2 support
Removed plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.
Removed plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.
Removed plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.
Removed plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.

does any one know a solution?

gmake ?

sure a typo

simply continue after qmake   ignore this error  type make  , should works as it do for me

[MCgivney79]

just be patient give the devs time to finalize the latest updates and i will be happy mining and staking soon 

[steven_ik]

hey guys ,
i am trying to compile the new Magi version v1.4.5.2 on my ubuntu machine but i am getting an error when i am trying to execute the "gmake" .

Project MESSAGE: Building with UPNP support
Project MESSAGE: Building with IPv6 support
Project MESSAGE: Building with SSE2 support
Removed plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.
Removed plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.
Removed plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.
Removed plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.

does any one know a solution?

gmake ?

sure a typo

simply continue after qmake   ignore this error  type make  , should works as it do for me

damm yea sorry your right i was looking in the wrong instalation guide file......

[111magic]

just be patient give the devs time to finalize the latest updates and i will be happy mining and staking soon 

Thanks appriciate your post

[RR3US]

{
"version" : "v1.4.5.2",
"protocolversion" : 71064,
"walletversion" : 60000,
"balance" : 0.01990000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 1606986,
"timeoffset" : 0,
"moneysupply" : 7744266.88714873,
"connections" : 8,
"proxy" : "",
"ip" : ",
"ipv4" :,
"ipv6" : "::",
"difficulty" : {
"proof-of-work" : 0.00153754,
"proof-of-stake" : 0.00100981
},
"testnet" : false,
"keypoololdest" : 1508546089,
"keypoolsize" : 100,
"mininput" : 0.00000000,
"paytxfee" : 0.00000000,
"unlocked_until" : 0,
"errors" : ""
}

Was there a fix for this or do i need to be patience?

[jbkel3496]

{
"version" : "v1.4.5.2",
"protocolversion" : 71064,
"walletversion" : 60000,
"balance" : 0.01990000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 1606986,
"timeoffset" : 0,
"moneysupply" : 7744266.88714873,
"connections" : 8,
"proxy" : "",
"ip" : ",
"ipv4" :,
"ipv6" : "::",
"difficulty" : {
"proof-of-work" : 0.00153754,
"proof-of-stake" : 0.00100981
},
"testnet" : false,
"keypoololdest" : 1508546089,
"keypoolsize" : 100,
"mininput" : 0.00000000,
"paytxfee" : 0.00000000,
"unlocked_until" : 0,
"errors" : ""
}

Was there a fix for this or do i need to be patience?

Patient, devs fixing now.

[jbshaps466]

So downloaded and the 1.4.5.2 wallet runs fine.  Get it that the Staking won't work, but the wallet never sync's up.    1.4.5.1 synced up fine when I re-ran this morning, but the newer version is just hanging.
Getinfo dump follows:


{
"version" : "v1.4.5.2",
"protocolversion" : 71064,
"walletversion" : 60000,
"balance" : 4.53856249,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 1606986,
"timeoffset" : -1,
"moneysupply" : 7744266.88714873,
"connections" : 6,
"proxy" : "",
"ip" : "",
"ipv4" : "",
"ipv6" : "0.0.0.0",
"difficulty" : {
"proof-of-work" : 0.00153754,
"proof-of-stake" : 0.00100981
},
"testnet" : false,
"keypoololdest" : 1512514785,
"keypoolsize" : 101,
"mininput" : 0.00000000,
"paytxfee" : 0.01000000,
"unlocked_until" : 0,
"errors" : "EXCEPTION: 12bignum_error \nCBigNum::operator/ : BN_div failed \nMagi in ProcessMessages() \n"
}

do I have to set the posii=0 in order for it to sync?

[RinceWind84]

So downloaded and the 1.4.5.2 wallet runs fine.  Get it that the Staking won't work, but the wallet never sync's up.    1.4.5.1 synced up fine when I re-ran this morning, but the newer version is just hanging.
Getinfo dump follows:


{
"version" : "v1.4.5.2",
"protocolversion" : 71064,
"walletversion" : 60000,
"balance" : 4.53856249,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 1606986,
"timeoffset" : -1,
"moneysupply" : 7744266.88714873,
"connections" : 6,
"proxy" : "",
"ip" : "",
"ipv4" : "",
"ipv6" : "0.0.0.0",
"difficulty" : {
"proof-of-work" : 0.00153754,
"proof-of-stake" : 0.00100981
},
"testnet" : false,
"keypoololdest" : 1512514785,
"keypoolsize" : 101,
"mininput" : 0.00000000,
"paytxfee" : 0.01000000,
"unlocked_until" : 0,
"errors" : "EXCEPTION: 12bignum_error \nCBigNum::operator/ : BN_div failed \nMagi in ProcessMessages() \n"
}

do I have to set the posii=0 in order for it to sync?

It seems that we are all stuck on Block 1606986 :-)

[alex_vigorskiy]

good afternoon. I noticed such a feature when growing bitcoin grows and magi. Why is that? And remind us how many coins and prospects the project has. Thank you

[jbshaps466]

So downloaded and the 1.4.5.2 wallet runs fine.  Get it that the Staking won't work, but the wallet never sync's up.    1.4.5.1 synced up fine when I re-ran this morning, but the newer version is just hanging.
Getinfo dump follows:


{
"version" : "v1.4.5.2",
"protocolversion" : 71064,
"walletversion" : 60000,
"balance" : 4.53856249,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 1606986,
"timeoffset" : -1,
"moneysupply" : 7744266.88714873,
"connections" : 6,
"proxy" : "",
"ip" : "",
"ipv4" : "",
"ipv6" : "0.0.0.0",
"difficulty" : {
"proof-of-work" : 0.00153754,
"proof-of-stake" : 0.00100981
},
"testnet" : false,
"keypoololdest" : 1512514785,
"keypoolsize" : 101,
"mininput" : 0.00000000,
"paytxfee" : 0.01000000,
"unlocked_until" : 0,
"errors" : "EXCEPTION: 12bignum_error \nCBigNum::operator/ : BN_div failed \nMagi in ProcessMessages() \n"
}

do I have to set the posii=0 in order for it to sync?

It seems that we are all stuck on Block 1606986 :-)

Well, I set the posii=0 and that error goes away, but still no sync...will just wait.  My miners on XMGPool are working but Bullmining is in maintenance mode, so not mining.

[kiiiiiiiii]

So downloaded and the 1.4.5.2 wallet runs fine.  Get it that the Staking won't work, but the wallet never sync's up.    1.4.5.1 synced up fine when I re-ran this morning, but the newer version is just hanging.
Getinfo dump follows:


{
"version" : "v1.4.5.2",
"protocolversion" : 71064,
"walletversion" : 60000,
"balance" : 4.53856249,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 1606986,
"timeoffset" : -1,
"moneysupply" : 7744266.88714873,
"connections" : 6,
"proxy" : "",
"ip" : "",
"ipv4" : "",
"ipv6" : "0.0.0.0",
"difficulty" : {
"proof-of-work" : 0.00153754,
"proof-of-stake" : 0.00100981
},
"testnet" : false,
"keypoololdest" : 1512514785,
"keypoolsize" : 101,
"mininput" : 0.00000000,
"paytxfee" : 0.01000000,
"unlocked_until" : 0,
"errors" : "EXCEPTION: 12bignum_error \nCBigNum::operator/ : BN_div failed \nMagi in ProcessMessages() \n"
}

do I have to set the posii=0 in order for it to sync?

It seems that we are all stuck on Block 1606986 :-)

Well, I set the posii=0 and that error goes away, but still no sync...will just wait.  My miners on XMGPool are working but Bullmining is in maintenance mode, so not mining.

Same here

[111magic]

just be patient give the devs time to finalize the latest updates and i will be happy mining and staking soon 

Info will follow asap!

[icedfiend]

I discovered Magi a few days ago looking for a budget friendly coin to mine and grow with... Just wanted to say "Keep up with the great work" to the devs and the comunity.

I'll patiently wait for the wallet fix and hope for the best!

[extant]

please fix  eager to start mining 

[Jeremy450]

either  0.2 XMG  , long enough in Crypto im out there

What pool is working ?? I tried many, but today they all stopped!   

Here is my pool:

http://crypto.ngrok.majed.pro:9999/site/gomining?algo=m7m

username:root
password:toor

min Payout is now 1.5 XMG

WOW that was a waste of time and energy and mining. lost 33xmg of coins and all the blocks went orphaned!

[111magic]

I discovered Magi a few days ago looking for a budget friendly coin to mine and grow with... Just wanted to say "Keep up with the great work" to the devs and the comunity.

I'll patiently wait for the wallet fix and hope for the best!

Great! 👍

[Visteras]

i can started mining magi on my pool?
i owner pool.mineproject.ru
or need wait?

[111magic]

i can started mining magi on my pool?
i owner pool.mineproject.ru
or need wait?

No not yet. Magi team will post here, twitter, slack & telegram when its ready to start mining.

[Jeremy450]

No amount of bugging/nagging/pleading/swearing/annoying/begging is going to speed up the fixing process.

This is coming from a software developer myself.

software developing is like a sweet devil. tickle her right and she will give you joy.
tickle her in the wrong spot and she'll rip your b*lls off!

Just be Patient and she will give you the world

[deztroyr1]

either  0.2 XMG  , long enough in Crypto im out there

What pool is working ?? I tried many, but today they all stopped!   

Here is my pool:

http://crypto.ngrok.majed.pro:9999/site/gomining?algo=m7m

username:root
password:toor

min Payout is now 1.5 XMG

WOW that was a waste of time and energy and mining. lost 33xmg of coins and all the blocks went orphaned!

well people have been warning for that the whole time. soon we can pick things back up properly though.