Blockchain splits on PoS and it has been related to the recent issue. We've sent out requests to put wallet into maintenance mode few days ago; Bittrex did so which made them be not affected.
I'll be uploading blockchain data, or people can connect to 104.128.225.215, and will post test regarding the current issue.
We do be aware of the situation, and try as much as possible to bring back normal operation, and fix the PoS issue.
Thanks for the update Joe, anything we can do to help? Thanks; we'll need more people run test wallet as mentioned above. |
|
|
|
|
Blockchain splits on PoS and it has been related to the recent issue. We've sent out requests to put wallet into maintenance mode few days ago; Bittrex did so which made them be not affected.
I'll be uploading blockchain data, or people can connect to 104.128.225.215, and will post test regarding the current issue.
We do be aware of the situation, and try as much as possible to bring back normal operation, and fix the PoS issue.
|
|
|
|
I'll try to make out a test tonight as much as possible; since got a daily work to do, would depend how the thing proceeds.
I'm gonna post tomorrow. |
|
|
|
|
I'll try to make out a test tonight as much as possible; since got a daily work to do, would depend how the thing proceeds.
|
|
|
|
Decision was made  by joelao95 nice community coin ! free and very " dezentral" magi is joelao95 own petro coin Well the coin is originally designed with PoW, such decision was built in. People like to have alternative, there was already an option that Noblecoin who stopped PoW and we offered magi's codebase and PoS. It's not about how many people own the coin make it decentralization; we advertise idea in the website that has to be with original design, or we make us real dead. At this point, yes, I seem to the main one making the direction. Out there are free to make things like coin initial distribution, chain swap, such like, I do want to make sure we're down to the original way, that I believe (certainly personal optinion) is the way going. |
|
|
|
hello,
plaese joe change the algo a bit so all the non CPU miners are fucked.
gr xms
There are many down on the road looking for better mining experiences and some are in active development. Let's recommend what optional algo that can fulfill well? |
|
|
|
this make sense so the main issue is weak legit hashpower compared to hostile hashpower as long as u dont fix that this attack vector will stay valid remove POW issue is fixed plain and simple fuck traditions if they are bad @cryptonit, we respect suggestions, but here magi will never remove PoW. Decision was made, and I wish all future proposals are brewed under this circumstance. I'm sure people have different opinions, and reasonably one would figure association with PoW dooms to be a failure, let it be, I would barely argue. |
|
|
|
I'm keen to traditions.
What does that even mean? What traditions? Does this mean you'll be actively trying to patch this vulnerability? I get things should go where they suppose to go, in a quite simple and straightforward way. |
|
|
|
Hey Joe,
I was wondering if you guys need any help on fixing the vulnerability that has been exploited by the russian. I have experience working with C/C++, and would be glad to help get this fixed as soon as possible. (I tried to PM, but it didn't go through. I'm still too new on this forum)
-Nathan
Thanks for offering helps. You can go http://slack.m-core.org/; github code is where you might want to look into and make changes. Have to work out somethings to live by, but shall try to catch things up. |
|
|
|
|
It has appeared that network disturbance gets similar symptom to the last incident, and there was a leftover that is currently upon the PoS atm. In the last fix, we've been modifying time-drift to suppress PoW disturbance; in terms of less PoS block time than PoW, the time-drift seems not that strict. The last incident on PoW network disables PoS, and vice versa, at now PoW blocks was affected by PoS. The allowance of 5 minute drift pretty much matches future PoS blocks currently going on.
I'm going to make corresponding adjustments, meanwhile, have a look at diff-adjustment and make corrections when needed, and then send out a test.
|
|
|
|
Your name is oddly similar to a user on a pool who does about 5000 - 8000khs
im beyond mining since ages POS and masternodes and harvesting thats the way i make money this days on multiple coins XMG is no earner in no way but i like joe and magic and i know they are honest guys just they didnt made the jump to fulltime crypto and the whole project suffers by that POW is so dead even if u think u see it still walking its walking dead i hope joe realize and cut the head of this zombie technology [img]https://i.imgur.com/NQ9ec20.png[/img_] Well Put  I'm keen to traditions. |
|
|
|
Dev is gone so Magi is helpless.
No he's not. Stop spreading this kinda msgs, just because things not fixed within the time you want it to... When these kinds of things have happened in the past and the Dev was on top of it, it seems like the Dev has lost hope in the project, or he's just lost interest. For a decentralized crytocurrency (emphasis on the currency, as in money), we need an active developer to zap problems as soon as they pop up. The absence of the dev proves two things: (1): Not enough people are looking at the source code to patch issues like this as soon as they happen (a big problem with proprietary software for obvious reasons) (2): The developer doesn't care enough to keep a close eye on his projects, which will ultimately lead to the death of the MagiCoin Call me what you will, but its stopped being profitable for me to mine this coin, and like I'm sure many other people will, I'll be moving my miners over to something like Monero. At least they're on top of their game. We're seeking to impact while some real things get piled up. Well, good point that we see that Joe is alive, this is good news, but it is the only one and frankly not enough. A few more words would be much more helpful. Put together a proper update and post it on all social media where Magi is present. At the moment the community has no idea what is the current development/roadmap situation. What it the current status of updates, any roadmap changes, what is happening with the new webpage and how is the mpays system getting along? These would be just a few points that you should address when posting a new update, and hopefully not in September or so, but sooner. I agree going the way that helps in general should be said. |
|
|
|
Dev is gone so Magi is helpless.
No he's not. Stop spreading this kinda msgs, just because things not fixed within the time you want it to... When these kinds of things have happened in the past and the Dev was on top of it, it seems like the Dev has lost hope in the project, or he's just lost interest. For a decentralized crytocurrency (emphasis on the currency, as in money), we need an active developer to zap problems as soon as they pop up. The absence of the dev proves two things: (1): Not enough people are looking at the source code to patch issues like this as soon as they happen (a big problem with proprietary software for obvious reasons) (2): The developer doesn't care enough to keep a close eye on his projects, which will ultimately lead to the death of the MagiCoin Call me what you will, but its stopped being profitable for me to mine this coin, and like I'm sure many other people will, I'll be moving my miners over to something like Monero. At least they're on top of their game. We're seeking to impact while some real things get piled up. |
|
|
|
The osx donwload link is now fixed. |
|
|
|
@Historical, many thanks for years' running the m-hash pool. |
|
|
|
So this didn't work. Using the GUI (like you would in Windows, as I couldn't find a command line I was comfortable with), I moved all the files, sub-directories, etc. from the freshly downloaded magi-1453 folder into the original Magi folder.
I then tried to start the service but it wouldn't work. I renamed the existing .Magi folder - the one that contains the block chain, wallet.dat etc. and ran the service again - a new .Magi folder was created!
However it was unable to come online as there was no user information. So I made a new magi.conf file and restated the service and it seems to be active. HOWEVER, each time I do a 'magid getinfo' I get a reply that it's unable to connect to the server. I'll give it a little while to catchup with the block chain from yesterday, however I'm worried there's still more to do.
odroid@odroid:~$ magid getinfo
error: couldn't connect to server
Hope you get it up & running; it takes time to load up the chain, then you'll be able to check status. |
|
|
|
If I understand correctly, downloading block-chain data (which is a 1,3 GB file) is not necessary. One can just (1) backup the file wallet.dat, (2) install the new m-wallet leaving the old folder Magi unchanged (3) open the new m-wallet and wait until it syncs.
Is this correct? Is the old block-chain folder stored in the Magi folder still usable? Will it sync correctly? Thanks
Yes, NOT necessary to redownload chain data. |
|
|
|
Thanks. I think this in another folder...something like users/user/appdata/roaming/magi?
This is correct. |
|
|
|
|
Show Posts
