I'm impressed to see how Magi is gaining traction in development. These new improvements would make Coin Magi stronger than ever, growing solid among the stack of altcoins available. I hope that this would have a nice effect in XMG's price, as more people join it, due to the exciting features that it will provide. The new Magi 1.3.1 wallet release is stellar, and truly demonstrates that there is a good dev behind it and a solid community supporting it. That is to say, I will continue to buy and hold Magi for the long term, as this is one of those cryptocurrencies out there that you don't want to miss out. The thing that I like most about Magi is that it allows any average person to get up and running to mine some coins. Just sharing my thoughts. ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) Thanks for being with the coin for years. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
...
u can easy dedect such copycoins if they only split endless and never start to merge and users have to merge manually
this is bad configured POS in coin code mostly seen in copycoins
one part that lead to many copycoins have this not configured proper is a code comment that read "dont touch this" and any copycoin coder did this didnt touch this line and fucked up his coin POS behavior
its not like PPC and NVC the first two POS coins and sunny king its creator wanted to make it easy copy their POS and so they leave their traps in their code that many copycoin coder did fall in
Well, truthfully this section really shouldn't be touched, and merging staking should be disabled. Imagine one owns 25% + 25% coins in two lines, combining them into a single line would cause potential attacks. This is why general PoS coins in a small scale can fork that easy. The thing is that splitting and merging are not part of PoS protocol. Without having them in the protocol is definitely a deficiency of the PoS. It's quite doable for advanced users to modify the code and enable them without a need of hard fork. I'd vote that the so-called cloud staking does this kind of things. Staking into dust is really a good thing to the healthy of the coin, but of course not good to the wealthy of people.
|
|
|
hey magi friends,
Just installed the new magi wallet, and i must say it lookes very neat and clear.
i like the value for magi at that moment and for the wallet in total but can it be changed from dollars to euro's in the future?
very good work for all who worked on the wallet but spacial thanks to Joelao95
greatings xms
Thanks; yes, that feature is nice, and having different currencies available is what I'd expect in the near future.
|
|
|
For one who missed the poolinfo page, here is the new link: http://poolinfo.systms.orgThanks to ex33s for years' contributions in a couple of things. An little update on that site. I've enabled the following * HTTP2 * Site now responds to IPv6, so now the site responds to both IPv4 and IPv6 * I've installed SSL cert so the site now works with https instead of http Any old links to the site using http will continue to work but you will be redirected over to https instead. Still working on getting the wallet up and running so I can fetch proper data from it and present it on the site. Thanks, take time.
|
|
|
Mining away like a boss on my i5, i3, and even my little netbook lol. Just wondering, are there any thoughts of a GOU miner or is that not possible at this point?
To much hashrate will bring the blockreward down. So not at this point. Got ya, so its a possibility, just not a good idea at this point. Due to there being no GPU miner currently available, do we have any idea what the diff between CPU and GPU mining would be? Would it be a massive difference like scrypt? or something like XMR where CPU mining is still somewhat feasible even with GPU mining available? Im sorry, I cant remember the actual term for the relationship between CPU and GPU hashrates. There are many sayings about GPU miners, while it's obviously not published anywhere and thus no clue the difference between them. In any cases, we're working on this regard, and have to come to a conclusion at some time soon as I'd expect.
|
|
|
I just upgraded to the new wallet from the RC - I like the look of the new version - seems to be a bit more streamlined - and also seems a bit faster =)
Thanks Joe =)
I've put what I thought would be there, but probably not; just let me know. :-)
|
|
|
Cheers! I'll appreciate 111magic who is the best to keep this coin in years going to be frank.
|
|
|
Thanks for the detailed update I think you hit the nail on the head with the priorities.
I can help with the web side if needed - I'll be a bit slow, as things are a bit manic these days, I'm more into back-end development - but have worked on many web projects in the past - but I'm not good at making things look pretty.
Drop me a line with some requirements when you get time (no pressure). I was on the site a few days ago - and its completely full of spam - I suspect a spam filter will be up there.
Thanks for help. I'll PM about the m-talk.
|
|
|
Without formal announcement, I'd mention briefly three major works. The first item should be done in this year 2017.
1. It won't be done without a hard fork, and it will be a major one.
* Optimization on the difficulty adjustment algorithm that expects a fast response to the network hashrate * Adjustment of PoW algo * Establish a channel between PoW and PoS * PoS-II to "mPoS".
The above are four optional areas of improvements, each or all of which should (successfully) lead to support of efficient mining by the low-end devices (except the last one that's PoS).
2. Migrating and combining with the latest bitcoin code base, which, I guess, is yet existed in PoS coins; I believe this way would move the coin much better and strong.
3. Continue / improve Magi's payment gateway: m-epays; it's not our intention to invent a payment gateway, but a way to speed the coin to be accepted and used.
A more detailed roadmap will be announced in the OP and our website in following weeks. The site is currently been worked on. Details are to be announced.
Also, I intend to bring the forum m-talk.org into a good shape, however, I barely have the time and also web skills. If anyone is willing to assist or take this job, drop me a message.
Since we had a slack channel (https://coinmagi.slack.com/), if anyone want to joint, send me your email address; I'll send out invitations:
joelao98@gmail.com
or contact the team:
contact@coinmagi.org
|
|
|
Could I solo mining and stake the same time with new version? thanks for answer
Yes, this can be done.
|
|
|
I agree with that. I think Magi will have a higher value in 6 months. For sure with ups & downs but it will raise. Magi value has been very stable, also with ups&downs in the past. But all those new developments, huge dev & community activity will bring Magi to a higher level in the world of digital currencies.
Bud, the download links in bitcoingarden post needs a fix. :-)
|
|
|
For one who missed the poolinfo page, here is the new link: http://poolinfo.systms.orgThanks to ex33s for years' contributions in a couple of things.
|
|
|
Currently says "not staking because you don't have enough weight", since last upgrade to latest wallet am also seeing "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications", but assumed everyone was seeing same.
Not sure how to do what you suggested in combining, but thinking you mean to send all coins to a new address in the wallet?
Thanks again for the replies and suggestions!
Hope the info mentioned by people solved your problem; just let us know if you're still experiencing that. I should make utilities in the Qt-wallet / RPC, for example, for one to distinguish understaking and overstaking; will be one thing on the to-do-list.
|
|
|
open up your wallet, then go to help and open the debug window. After that, go to console and put it getminingbykhps <your hashrate here> so in your case getminingbykhps 250 You'll have to take the number it gives you and the current market price and figure from there. Lets say the console shows you earn 15 magi a day, you would do this math 15*.00003150*977.952 (total coins)*(price XMG-BTC)*(price BTC-USD), so in that example you would make about 46 cents a day. I hope that all makes sense!
I'd need to get those commands being well documented in the wallet, and a dollar amount adding would be handy as well.
|
|
|
... A few more notes based on my experience:
...
Thanks for a summary of practical results; these are absolutely the observations that we apply to the system to be evaluated further and optimized.
|
|
|
@starmman, we can talk about roadmap now; in what form you'd do a roadmap?
Hi Joe, Great stuff I think best thing to do is get a few bullet points about the next plans for the coin push them into a visualisation and push them into an OP. Then we could also to show where we have come from to show that we are not at the start of the development After that we could elaborate on the bullet points a little more Do you agree that this is a good approach? Think a roadmap is great for fundamental analysis and should give investors some reasons to (or not to - if they disagree with the roadmap) invest in the coins . I'll drop my details across to 111magic for slack - think its an easier platform to communicate in real time. I've got a bit of a full-on weekend coming (both my and my wife's birthday) up so might take a few days before I can dedicate some serious time, I agree. We made some points in the past when I was issuing the RC if one could recall, and also those can be found via links enclosed in the new wallet. It is certain that we aren't limited to that. I am also not much a fan of using fancy stuffs though that catching eyes; a to-do-list would very much do it. I'll have my focus on the OP things and get a new updated list. And enjoy your weekend.
|
|
|
I rebuilt the source using the master branch on git. The wallet looks pretty cool so far - nice job! It seems to be using Berkeley DB again for me as reported on the about page:
Berkeley DB 4.8.30: (April 9, 2010)
Network connections are a 50 and the wallet is synching the block chain again after running previously with v1.3.0rc1. I'm just wondering if I should be doing something different to build so that the LevelDB is used again, or if this okay?
Actually LevelDB is used to deal with blocks.
|
|
|
... (I like the value in US$)
I actually realized now that this wasn't a well-planned idea; we may make better at least with a variety of fiat currencies available.
|
|
|
m-wallet version 1.3.1 released
Please Joe, do you have the .zip files for me. You made a link to .dmg files. Oops, fixed now; pls try the setup, let me know if it works.
|
|
|
|