It is compatible with the prior version so you don't remove except running the latest. You can also download binaries.
Thanks for the prompt reply. I just want to make sure I understand completey. When I initally compiled v1.4.5.2, I used git clone https://github.com/magi-project/magi/ to obtain the files. Now, I know that if I try and do that now, the process will stop/fail since the 'magi' folder already exists. So, I have made a new folder 'magi-1453' and used git clone to get the new files into there. Are you saying that I just need to copy and replace the files from 'magi-1453' into 'magi' and I should be good to go? I don't need to reconfigure as a service or anything? What about the files in ./magi which were created when the magid daemon was first run? Can these all remain the same? You can go to old folder and do git pull. .magi is just fine, not necessary touch any thing. |
|
|
|
I am sure I am not the first person to ever ask this but how do I apply the block chain zip file after I down load it?
There is a README.md inside the file that contains a brief instruction: Quick startup II (replacing the block-chain): 0) Backup wallet.dat; 1) Download block-chain data from here: http://m-core.org/bin/block-chain;2) Delete all of the contents under the .magi (unix-like system) or Magi (OS X or Windows) folder, except for wallet.dat and magi.conf; 3) Unzip the file and copy the folders under "m-block-chain" into the .magi (unix-like system) or Magi (OS X or Windows) folder; 4) Launch the new wallet. |
|
|
|
Thanks for this new version and for your hard work!
Could you please create the tag/release on github so that I can checkout and build on my RPI3?
Thanks!
I've updated 1.4.5.3 release. |
|
|
|
So v1.4.5.3 is now out. I went through all this pain compiling the previous version.
Can the previous version be "upgraded" it do I need to go through the whole recompile fiasco again?
And If I do need to recompile, do I just do this like the previous version wasn't there, or do I need to "remove" the old version first?
It is compatible with the prior version so you don't remove except running the latest. You can also download binaries. |
|
|
|
|
We'll publish an updated version in minutes.
|
|
|
|
m-wallet version v1.4.5.2
Not mandatory, but recommended in order to reject version earlier than 1.4.5.1.
Windows x32 binary is available as well.
m-wallet version v1.4.5.1
Hard fork will take place at block #1606950. See below for the details of hard fork.
Qt-Wallet and Daemon:
https://github.com/magi-project/magi/releases
http://m-core.org/download/
http://m-core.org/bin/m-wallet-1.4.5.1/
Source code: https://github.com/magi-project/magi/
Windows: http://m-core.org/bin/m-wallet-1.4.5.2/m-wallet-1.4.5.2-win.zip
Linux: http://m-core.org/bin/m-wallet-1.4.5.2/m-wallet-1.4.5.2-linux.tar.gz
FreeBSD: http://m-core.org/bin/m-wallet-1.4.5.2/m-wallet-1.4.5.2-freebsd.tar.gz
Windows: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-win.zip
Linux: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-linux.tar.gz
Mac OS X: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-osx.dmg
FreeBSD: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-freebsd.tar.gz
Block chain: http://m-core.org/bin/block-chain/
v1.4.5.2
=============
Minimum protocol version 71063
v1.4.5.1
=============
This release schedules a hard fork at block #1606950 as a solution to the current mining issue that miners cannot mine blocks:
- The PoW / PoS block generation rule is disabled.
- Difficulty adjustment algo switches back to MQW at #1606948.
- Block drift time is limited within 5 min.
- Remove IRC and add DNS seeds.
Quick guide:
- Windows: unpack the files and run the wallet directly;
- Mac OS: unpack the files and copy to the Application folder, and then run the wallet directly;
- Linux: unpack the files and run the wallet directly.
Quick startup I (without touching the block-chain):
0) Backup wallet.dat;
1) Launch the new wallet.
Quick startup II (replacing the block-chain):
0) Backup wallet.dat;
1) Download block-chain data from here: http://m-core.org/bin/block-chain;
2) Delete all of the contents under the .magi (unix-like system) or Magi (OS X or Windows) folder, except for wallet.dat and magi.conf;
3) Unzip the file and copy the folders under "m-block-chain" into the .magi (unix-like system) or Magi (OS X or Windows) folder;
4) Launch the new wallet.
Note to v1.4.5.1
---------------------
v1.4.5.1 is compatible with the current block chain.
Things explained..
Firstly, I admit what's going on isn't good to the situation, and I do see there are needs of further works to fulfill the purpose of the coin.
There is no rollback. I learned few requests about actions on the miners who mined (future) blocks that the generic miners can't mine, and for that, rollback is one of the approaches. However, taking into account the overall situation that time to time transactions are involved, especially exchanges, there will be more damage to the coin when we cease the chain or perform a rollback.
As explained shortly in previous post, what happens is associated with the PoW / PoS rule in combination with the fact that 2-hour future blocks allowed as in the original design. I do see in this rule weakness because of the PoW block generation capable of being on a 10-min pattern without the PoS blocks. The another feature of MAGI's network that is intentionally kept at low hash rate comes a likability that one with a reasonable amount hash can launch a future block attack, the chance of this is increased by a fact that generic users can't make valid blocks owing to the PoW / PoS rule; these blocks are supposed to reset the block time.
By overviewing the situation, I see there is a difficulty in maintaining low-hash rate network, as individuals can always acquire big hash rate. In contrast, advantage lies in a network with huge amount of hash that individuals can't compete with. Nevertheless, it's not our intention to compromise the purpose because of the weakness. The PoS is supposed to dilute such weakness; I'm seeing the merit of the PoW / PoS rule when used beautifully. We shall make efforts on this aspect.
Let us know any questions / suggestions.
|
|
|
|
I haven't yet compiled wallet for different OS but would like to mention an Update to v1.4.5.2 with min protocol version elevated. This is not mandatory as long as v1.4.5.1 is already running: https://github.com/magi-project/magi |
|
|
|
magi coin need update his social channel
on coinmarketcap.com
need to add reddit talk
and on twitter
insted of @CoinMagi (that is not active) update to @Coin_Magi_XMG
that way more buzz and people will trust the coin
I suggest other people fill out CM's form too in order to update relevant info. I tried informing them about updating logo, adding novaexchange, obviously ignored. To clarify, @CoinMagi is mainly for announcement, and @Coin_Magi_XMG for multiple info; I agree the social channel on CM should be switched. hello joelao95, the wallet shows only fiat in dollars, is there a posibilty to change this to euro gr xms That will be possible we'd like to have. |
|
|
|
Could the development team, please, compile a 32 bit Windows version of the wallet? I run my wallet on an old Lenovo tablet and the pre-hardfork version had a 32bit one. Thank you
Unfortunately I got a trip for the past few days (got every backup except for the 32bit compiling environment) and will soon back for the 32bit compiling. |
|
|
|
magi coin need update his social channel
on coinmarketcap.com
need to add reddit talk
and on twitter
insted of @CoinMagi (that is not active) update to @Coin_Magi_XMG
that way more buzz and people will trust the coin
I suggest other people fill out CM's form too in order to update relevant info. I tried informing them about updating logo, adding novaexchange, obviously ignored. To clarify, @CoinMagi is mainly for announcement, and @Coin_Magi_XMG for multiple info; I agree the social channel on CM should be switched. |
|
|
|
m-wallet version v1.4.5.1
Hard fork will take place at block #1606950. See below for the details of hard fork.
...
Particular thanks to who involved in the internal test done by 111magic, ex33s, filoozom. filoozom has been making the code base much improved, and we're expecting some further improvements coming through. goldlabel maintains the facebook page and made prompt actions as well as regular basis operation. There're surely public tests involved many people who are very active on the progress I can't name since so many have offered helps. |
|
|
|
Can't mount the new MacOS X Wallet img file.
Will wait for the main dload page to be updated before redownloading.
I updated the wallet for OS X; should work now. |
|
|
|
|
A side note, good to see unexpected price move; my personal opinion - be smart trading.
|
|
|
|
m-wallet version v1.4.5.1
Hard fork will take place at block #1606950. See below for the details of hard fork.
Qt-Wallet and Daemon:
https://github.com/magi-project/magi/releases
http://m-core.org/download/
http://m-core.org/bin/m-wallet-1.4.5.1/
Source code: https://github.com/magi-project/magi/
Windows: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-win.zip
Linux: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-linux.tar.gz
Mac OS X: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-osx.dmg
FreeBSD: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-freebsd.tar.gz
Block chain: http://m-core.org/bin/block-chain/
v1.4.5.1
=============
This release schedules a hard fork at block #1606950 as a solution to the current mining issue that miners cannot mine blocks:
- The PoW / PoS block generation rule is disabled.
- Difficulty adjustment algo switches back to MQW at #1606948.
- Block drift time is limited within 5 min.
- Remove IRC and add DNS seeds.
Quick guide:
- Windows: unpack the files and run the wallet directly;
- Mac OS: unpack the files and copy to the Application folder, and then run the wallet directly;
- Linux: unpack the files and run the wallet directly.
Quick startup I (without touching the block-chain):
0) Backup wallet.dat;
1) Launch the new wallet.
Quick startup II (replacing the block-chain):
0) Backup wallet.dat;
1) Download block-chain data from here: http://m-core.org/bin/block-chain;
2) Delete all of the contents under the .magi (unix-like system) or Magi (OS X or Windows) folder, except for wallet.dat and magi.conf;
3) Unzip the file and copy the folders under "m-block-chain" into the .magi (unix-like system) or Magi (OS X or Windows) folder;
4) Launch the new wallet.
Note to v1.4.5.1
---------------------
v1.4.5.1 is compatible with the current block chain.
Things explained..
Firstly, I admit what's going on isn't good to the situation, and I do see there are needs of further works to fulfill the purpose of the coin.
There is no rollback. I learned few requests about actions on the miners who mined (future) blocks that the generic miners can't mine, and for that, rollback is one of the approaches. However, taking into account the overall situation that time to time transactions are involved, especially exchanges, there will be more damage to the coin when we cease the chain or perform a rollback.
As explained shortly in previous post, what happens is associated with the PoW / PoS rule in combination with the fact that 2-hour future blocks allowed as in the original design. I do see in this rule weakness because of the PoW block generation capable of being on a 10-min pattern without the PoS blocks. The another feature of MAGI's network that is intentionally kept at low hash rate comes a likability that one with a reasonable amount hash can launch a future block attack, the chance of this is increased by a fact that generic users can't make valid blocks owing to the PoW / PoS rule; these blocks are supposed to reset the block time.
By overviewing the situation, I see there is a difficulty in maintaining low-hash rate network, as individuals can always acquire big hash rate. In contrast, advantage lies in a network with huge amount of hash that individuals can't compete with. Nevertheless, it's not our intention to compromise the purpose because of the weakness. The PoS is supposed to dilute such weakness; I'm seeing the merit of the PoW / PoS rule when used beautifully. We shall make efforts on this aspect.
Let us know any questions / suggestions.
|
|
|
|
I just grabbed wallet 1.4.4.0. The supplied README states that upgrades from previous versions require that the entire block-chain be deleted before using it. Now, I'm not upgrading from a previous version, so it's not a big deal for me to download the, roughly, 1.3Gb chain; unless I'm going to have to do it again in a few days.
Devs, what's the word? Will I have to abandon any block-chain snapshot I download when the hard fork happens?
No, you can use the present chain you had. |
|
|
|
I came here to check why staking was only making orphans. Glad to hear a new wallet version is on its way. I would like to make a request to make sure that it will be possible to compile the new wallet on ARM64 devices. I have ordered some new PI devices that have been shipped, and I really want to run the magi wallet on a low power device that I can leave on all the time. My existing ARM64 device does not have enough space on it to test the new version, but in the past when I tried to build the wallet it failed although I could build wallets for other coins. If someone could test the new version on a Raspberry PI 3 or similar ARM64 device and post build instructions, it would be greatly appreciated.
Good to see you here again. I came across quite few running PI. We don't have organized documentation on that yet; people in slack would be help if you'd like to check over there: slack.m-core.org |
|
|
|
|
To All,
We got an issue few days ago, and here I'd make quick overview:
1) I'm getting to a point for an internal test of the fix (tomorrow night); I appreciated those who have helped MAGI on this incident. In case one wish to test or review changes, you can come to Slack; find 111magic (coin_magi_xmg) / ex33s / me there.
This incident has been observed as being related to the Pow / PoS rule in combination with the fact that 2-hour future blocks allowed as in the original design. Addition to this, the new block rule disturbs the difficulty, and this feature of uncertainty seems yet to get around. In observation of the Pow / PoS rule actually not being a major factor fixing the prior chain forking issue, I'd go (temporarily to go permanent upon no upcoming concerns) disable it. In the meantime, we will do a reduction of time drift for the blocks.
2) We try to make a release of the fix within this week. My expectation is that the fix would be like changes implemented such a way that a hard fork is required. Chain downtime or rollback will be avoided as much as possible, and actually I don't see those are necessary. Except for a need of the hard fork to get mining back to normal, this incident seems no influence on things like sending / receiving. Let me know if I missed some thing.
|
|
|
|
|
Show Posts
