Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 179. (Read 2375617 times)
I can't install the wallet on my Windows 10 (x 64) ! Do I require any other software for it to work? I see an error
There is a big notice saying:
Quote
Market Paused
Wallet Maintenance
Wallet Maintenance
Cryptopia seems to be updating the wallet finally!
Really how did you notice?
Cryptopia seems to be updating the wallet finally!
Special thanks to Dury
🌟🌟🌟🌟🌟Magi likes to inform the crypto community about progress Special thanks for Dury 👌
https://t.co/rm5B7eEsrk
Nice - thanks for sharing that =) https://t.co/rm5B7eEsrk
on https://www.cryptopia.co.nz/Deposit/Display?currency=XMG&returnUrl=/Exchange says:
Unable to generate address for XMG, Reason: 3/1/2018 Wallet upgraded. Waiting on devs to request it removed from maintenance (Hard fork @ block #1606950)
would you please remove it!
Unable to generate address for XMG, Reason: 3/1/2018 Wallet upgraded. Waiting on devs to request it removed from maintenance (Hard fork @ block #1606950)
would you please remove it!
Hi Guys,
Has the fork happened yet?
Usually id suss this out myself, but there is so much back and forwards and wallet changes, i'm a bit lost with where we are.
I thought a mayor announcent would be made when the fork happened.
Thanks
J
Has the fork happened yet?
Usually id suss this out myself, but there is so much back and forwards and wallet changes, i'm a bit lost with where we are.
I thought a mayor announcent would be made when the fork happened.
Thanks
J
Yes we have, as per info:
m-wallet version v1.4.5.3
v1.4.5.3
=============
Bug fix in difficulty adjustment algo, i.e., "MagiQuantumWave"; the bug manifests as an improper data conversion when carrying out a time-domain average because of the trival time difference between blocks.
Qt-Wallet and Daemon:
https://github.com/magi-project/magi/releases
http://m-core.org/download/
Source code: https://github.com/magi-project/magi/
Windows: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-win.zip
Linux: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-linux.tar.gz
Mac OS X: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-osx.zip
FreeBSD: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-freebsd.tar.gz
Latest Block chain (1603558): http://m-core.org/bin/block-chain/
=============
Regarding this version: we have initial scheduled hard fork here: https://bitcointalksearch.org/topic/m.27192013. We passed the fork point but stuck at 1606987; it was found improper data conversion that is used to deal with difficulty adjustment gets zero when handling small number; diff-adjust takes place using average over a time domain. Many blocks emitted between 1606950 - 1606987 causes tiny difference between their block time, that then hits on the bug.
v1.4.5.3
=============
Bug fix in difficulty adjustment algo, i.e., "MagiQuantumWave"; the bug manifests as an improper data conversion when carrying out a time-domain average because of the trival time difference between blocks.
Qt-Wallet and Daemon:
https://github.com/magi-project/magi/releases
http://m-core.org/download/
Source code: https://github.com/magi-project/magi/
Windows: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-win.zip
Linux: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-linux.tar.gz
Mac OS X: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-osx.zip
FreeBSD: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-freebsd.tar.gz
Latest Block chain (1603558): http://m-core.org/bin/block-chain/
=============
Regarding this version: we have initial scheduled hard fork here: https://bitcointalksearch.org/topic/m.27192013. We passed the fork point but stuck at 1606987; it was found improper data conversion that is used to deal with difficulty adjustment gets zero when handling small number; diff-adjust takes place using average over a time domain. Many blocks emitted between 1606950 - 1606987 causes tiny difference between their block time, that then hits on the bug.
Thank you edward0181
I remember reading that, and am on wallet 1.4.5.3, but thought i'd read the fork wasn't until the 18th....my mistake
May i also ask, which miner do you recommend? I hvae downloaded and tried them all over the last year, but am not sure which is best now with all the changes.
Are these still the only pools?
**************************************************************************************************
"Mining Pools
For pool mining, register one of the following pools. Once registered, create a worker that will be used by the miner to login.
Suprnova: http://xmg.suprnova.cc
MaxMiners: https://xmg.maxminers.net
m-hash: https://pom.m-hash.com
MinerClaim: http://minerclaim.net"
***************************************************************************************************
I also found this list here
https://poolinfo.systms.org/
I always find it strange that all this hard work gets done, and there are literally 1000's of comments and updates on this forum, and elsewhere on the net, yet the main website always seems to be out of date (not just aimed a Magi, same for nearly all coins) - Thats always my first point of call.
J
Hi Guys,
Has the fork happened yet?
Usually id suss this out myself, but there is so much back and forwards and wallet changes, i'm a bit lost with where we are.
I thought a mayor announcent would be made when the fork happened.
Thanks
J
Has the fork happened yet?
Usually id suss this out myself, but there is so much back and forwards and wallet changes, i'm a bit lost with where we are.
I thought a mayor announcent would be made when the fork happened.
Thanks
J
Yes we have, as per info:
m-wallet version v1.4.5.3
v1.4.5.3
=============
Bug fix in difficulty adjustment algo, i.e., "MagiQuantumWave"; the bug manifests as an improper data conversion when carrying out a time-domain average because of the trival time difference between blocks.
Qt-Wallet and Daemon:
https://github.com/magi-project/magi/releases
http://m-core.org/download/
Source code: https://github.com/magi-project/magi/
Windows: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-win.zip
Linux: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-linux.tar.gz
Mac OS X: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-osx.zip
FreeBSD: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-freebsd.tar.gz
Latest Block chain (1603558): http://m-core.org/bin/block-chain/
=============
Regarding this version: we have initial scheduled hard fork here: https://bitcointalksearch.org/topic/m.27192013. We passed the fork point but stuck at 1606987; it was found improper data conversion that is used to deal with difficulty adjustment gets zero when handling small number; diff-adjust takes place using average over a time domain. Many blocks emitted between 1606950 - 1606987 causes tiny difference between their block time, that then hits on the bug.
v1.4.5.3
=============
Bug fix in difficulty adjustment algo, i.e., "MagiQuantumWave"; the bug manifests as an improper data conversion when carrying out a time-domain average because of the trival time difference between blocks.
Qt-Wallet and Daemon:
https://github.com/magi-project/magi/releases
http://m-core.org/download/
Source code: https://github.com/magi-project/magi/
Windows: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-win.zip
Linux: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-linux.tar.gz
Mac OS X: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-osx.zip
FreeBSD: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-freebsd.tar.gz
Latest Block chain (1603558): http://m-core.org/bin/block-chain/
=============
Regarding this version: we have initial scheduled hard fork here: https://bitcointalksearch.org/topic/m.27192013. We passed the fork point but stuck at 1606987; it was found improper data conversion that is used to deal with difficulty adjustment gets zero when handling small number; diff-adjust takes place using average over a time domain. Many blocks emitted between 1606950 - 1606987 causes tiny difference between their block time, that then hits on the bug.
Hi Guys,
Has the fork happened yet?
Usually id suss this out myself, but there is so much back and forwards and wallet changes, i'm a bit lost with where we are.
I thought a mayor announcent would be made when the fork happened.
Thanks
J
Has the fork happened yet?
Usually id suss this out myself, but there is so much back and forwards and wallet changes, i'm a bit lost with where we are.
I thought a mayor announcent would be made when the fork happened.
Thanks
J
Please Dev, can you put some pressure to Cryptopia to let them know the maintenance is ended ?
I've more than 2K of XMG blocked on them due to wallet in maintenace ...blah blah blah..
Thx guys for your greate efforts
Thanks crazy72. I will send another message. I already updated the latest wallet links on their own forum, sent multipli request & messages. It might help if more people send them messages about the released wallet update.I've more than 2K of XMG blocked on them due to wallet in maintenace ...blah blah blah..
Thx guys for your greate efforts
Please Dev, can you put some pressure to Cryptopia to let them know the maintenance is ended ?
I've more than 2K of XMG blocked on them due to wallet in maintenace ...blah blah blah..
Thx guys for your greate efforts
I've more than 2K of XMG blocked on them due to wallet in maintenace ...blah blah blah..
Thx guys for your greate efforts
Given the recent influxes, all I'm contributing is a Pi 3, splitting the hash rate between 3 pools, and solo mining on my PoS wallet. With rewards lately there isn't any point in throwing anything less efficient at the Magi network, and anyone that does IMO deserves to lose money on this coin.
This coin really is "it takes a village", now if everyone reading this thread mining dropped their contribution to the network down to 10khash, split among multiple pools, we would all make more Magi (and strengthen the network). There are a bunch of other coins that are much more profitable for people with high khash available, no reason to go Gung-ho with Desktop CPU's on this coin.
I honestly thing the biggest problem with this coin is the pools, because they give "shares", which give rewards proportionate to the number of shares contributed as a whole to the pool, thus giving the appearance of more hash power = more rewards, when this coin is the opposite (and people don't research before-hand; for which I think the pools should educate their users where possible about this, and/or enforce some speed limit, for their own profitability, and that of the network).
I think you are right about the fact that people with huge hashrate can receive better profit mining other coins.This coin really is "it takes a village", now if everyone reading this thread mining dropped their contribution to the network down to 10khash, split among multiple pools, we would all make more Magi (and strengthen the network). There are a bunch of other coins that are much more profitable for people with high khash available, no reason to go Gung-ho with Desktop CPU's on this coin.
I honestly thing the biggest problem with this coin is the pools, because they give "shares", which give rewards proportionate to the number of shares contributed as a whole to the pool, thus giving the appearance of more hash power = more rewards, when this coin is the opposite (and people don't research before-hand; for which I think the pools should educate their users where possible about this, and/or enforce some speed limit, for their own profitability, and that of the network).
And you are right about the pools. There are some pools added rules about the hashrate.
Think it would be good if there was a multipool available for XMG.
Given the recent influxes, all I'm contributing is a Pi 3, splitting the hash rate between 3 pools, and solo mining on my PoS wallet. With rewards lately there isn't any point in throwing anything less efficient at the Magi network, and anyone that does IMO deserves to lose money on this coin.
This coin really is "it takes a village", now if everyone reading this thread mining dropped their contribution to the network down to 10khash, split among multiple pools, we would all make more Magi (and strengthen the network). There are a bunch of other coins that are much more profitable for people with high khash available, no reason to go Gung-ho with Desktop CPU's on this coin.
I honestly thing the biggest problem with this coin is the pools, because they give "shares", which give rewards proportionate to the number of shares contributed as a whole to the pool, thus giving the appearance of more hash power = more rewards, when this coin is the opposite (and people don't research before-hand; for which I think the pools should educate their users where possible about this, and/or enforce some speed limit, for their own profitability, and that of the network).
People will always try to create closed pools or split power between pools, etc. switching power from coin to coin. Therefore, the strategy of waiting for the whales to leave will not work. This coin really is "it takes a village", now if everyone reading this thread mining dropped their contribution to the network down to 10khash, split among multiple pools, we would all make more Magi (and strengthen the network). There are a bunch of other coins that are much more profitable for people with high khash available, no reason to go Gung-ho with Desktop CPU's on this coin.
I honestly thing the biggest problem with this coin is the pools, because they give "shares", which give rewards proportionate to the number of shares contributed as a whole to the pool, thus giving the appearance of more hash power = more rewards, when this coin is the opposite (and people don't research before-hand; for which I think the pools should educate their users where possible about this, and/or enforce some speed limit, for their own profitability, and that of the network).
HI
please give mi link to the Blockchain .
https://chainz.cryptoid.info/xmgplease give mi link to the Blockchain .
You are welcome above the link.
Given the recent influxes, all I'm contributing is a Pi 3, splitting the hash rate between 3 pools, and solo mining on my PoS wallet. With rewards lately there isn't any point in throwing anything less efficient at the Magi network, and anyone that does IMO deserves to lose money on this coin.
This coin really is "it takes a village", now if everyone reading this thread mining dropped their contribution to the network down to 10khash, split among multiple pools, we would all make more Magi (and strengthen the network). There are a bunch of other coins that are much more profitable for people with high khash available, no reason to go Gung-ho with Desktop CPU's on this coin.
I honestly thing the biggest problem with this coin is the pools, because they give "shares", which give rewards proportionate to the number of shares contributed as a whole to the pool, thus giving the appearance of more hash power = more rewards, when this coin is the opposite (and people don't research before-hand; for which I think the pools should educate their users where possible about this, and/or enforce some speed limit, for their own profitability, and that of the network).
This coin really is "it takes a village", now if everyone reading this thread mining dropped their contribution to the network down to 10khash, split among multiple pools, we would all make more Magi (and strengthen the network). There are a bunch of other coins that are much more profitable for people with high khash available, no reason to go Gung-ho with Desktop CPU's on this coin.
I honestly thing the biggest problem with this coin is the pools, because they give "shares", which give rewards proportionate to the number of shares contributed as a whole to the pool, thus giving the appearance of more hash power = more rewards, when this coin is the opposite (and people don't research before-hand; for which I think the pools should educate their users where possible about this, and/or enforce some speed limit, for their own profitability, and that of the network).
I see no reason now to include workers at current yields 
If anyone the last day had trouble to register your account on our pool TrasMaMod XMG pool https://magi.trasmamod.com .
Then the problem is now solved and you can now try to register again.
We have upgraded the recaptcha security feature.
Thanks for the update tommyrsk Then the problem is now solved and you can now try to register again.
We have upgraded the recaptcha security feature.
If anyone the last day had trouble to register your account on our pool TrasMaMod XMG pool https://magi.trasmamod.com .
Then the problem is now solved and you can now try to register again.
We have upgraded the recaptcha security feature.
Then the problem is now solved and you can now try to register again.
We have upgraded the recaptcha security feature.
Jump to: