Hey Coin Magi Community, We should really try to get this coin listed early on in the release of www.coinmarketapp.com which is launching on the 29th of this month - check it out https://bitcointalk.org/index.php?topic=792912.20As a community, we already achieved to get listed on 'Coin Market Cap' which was the very same day, thanks to all of us +1ing it.. I think we should collaborate on what links should be listed in this app.. in order to help the community find info without digging through hundreds of hours of threads. Dev what do you think? Community? I think this is a smart play, we all are early investors here with CoinMagi... and its just the beginning... If this app takes off and magi is listed in the TOP 10 or even top 20 position, guess how much publicity Coin Magi will continue to get? Yeah, exactly... I'm doing all I can to help, but we need the community to continue their efforts to work together. Sam, this is a breaking news, thanks, the app looks very nice and informative; community will love to see magi on the app. The following are links I have collected so far: Website: http://www.cryptomagic.com/Bitcointalk thread: https://bitcointalk.org/index.php?topic=735170.0twitter: https://twitter.com/CoinMagifacebook: http://www.facebook.com/CoinMagiExchanges: https://cryptoine.com/trade/xmg_btchttps://c-cex.com/?p=xmg-btc https://c-cex.com/?p=xmg-usdhttps://www.swisscex.com/market/XMG_BTC(got two exchanges added us today) Block explorer: https://chainz.cryptoid.info/xmgAnyone suggests links?
|
|
|
I do not get coin swap! When?
tomorrow.
|
|
|
Re: Opinions on the state of play.
Restricting the source code and restricting hashrate by brute force is the wrong way to go and unlikely to win friends. Excessive tinkering at this point would be unwise and it seems good the way it is right now imho. Far better to simply get the message across to the miners with over say 1 Mh/s at their disposal that they are actually the problem. These miners need to realize that they could be throwing far far less hashing at it and get much higher rewards. Yeah - it's counter-intuitive and people need to wise up. Perhaps this particular feature requires greater emphasis in publications. From a few back-of-a-cigarette-packet calculations I reckon miners should be aiming for a maximum 200 Kh/s each, then we can see how the totals work out in more detail. The only problem I see with this approach is that self-restraint in not general human nature while greed is generally the norm. XMG is different - greed should not be rewarded.
“Greed, hatred and ignorance rise endlessly, I vow to abandon them” - Zen chat I agree, I sent you a tip for your wise words. I think in general that community and harmony will let us go farther faster and self-restraint will be helpful. The rules of the game are changing and thankfully so – many people are waking up to this. However, I do think we have to give each other a break there are so many old habit energies that are hard for us to break – greed, stealing, and doing what is not of benefit even to ourselves in the long run. We really have know idea what someone's situation is; perhaps they are the 81 richest person in the world and they need just a little bit more to get in with the 80 people who's combined wealth equals that of the lower half of humanity. Perhaps they need to get the heck out of some terrible situation. Who are we to deprive them of their chance to earn more magic coins? There is no real long term scarcity in cryptocoins - new coins are popping up every day some numbering in the billions - whats tough is to find is good community of supporters that are willing to put some value into the product they are building together and help each other out. We have a common goal and people working together can do wonderful things, I think toleration, generosity and incentives can work better than greed and ignorance in the long run. XMG: 9Romi8ZpevAwcu218gNsuCrv8i9Li6oarj I am glad the magi community has seen some posts with deep thoughts. Lightsplasher, I remembered your video made few months ago, that impressed me.
|
|
|
Hey Coin Magi Community, We should really try to get this coin listed early on in the release of www.coinmarketapp.com which is launching on the 29th of this month - check it out https://bitcointalk.org/index.php?topic=792912.20As a community, we already achieved to get listed on 'Coin Market Cap' which was the very same day, thanks to all of us +1ing it.. I think we should collaborate on what links should be listed in this app.. in order to help the community find info without digging through hundreds of hours of threads. Dev what do you think? Community? I think this is a smart play, we all are early investors here with CoinMagi... and its just the beginning... If this app takes off and magi is listed in the TOP 10 or even top 20 position, guess how much publicity Coin Magi will continue to get? Yeah, exactly... I'm doing all I can to help, but we need the community to continue their efforts to work together. Sam, this is a breaking news, thanks, the app looks very nice and informative; community will love to see magi on the app. The following are links I have collected so far: Website: http://www.cryptomagic.com/Bitcointalk thread: https://bitcointalk.org/index.php?topic=735170.0twitter: https://twitter.com/CoinMagifacebook: http://www.facebook.com/CoinMagiExchanges: https://cryptoine.com/trade/xmg_btchttps://c-cex.com/?p=xmg-btc https://c-cex.com/?p=xmg-usdhttps://www.swisscex.com/market/XMG_BTC(got two exchanges added us today) Block explorer: https://chainz.cryptoid.info/xmgDice Game http://xmg.maxbet.club
|
|
|
LOL, pool limiting hashrate is impossible. Use a proxy and create more workers.
You're trying to make mining into something it's not - centralizing it and forcing people to use small amounts of hash just... isn't going to work.
I know that you employer will not be happy for sure. But i agree. Dev, Please don't do this and forget what said. We will just stay where we are unless big voice comes up.
|
|
|
@MarcusDe and other contributors
will send coins, too busy in stuffs.
|
|
|
can any1 post the latest windows 64bit miner plz It's few pages back, not yet have time to update the OP; Spexx, can you post your compilation for Zlush1337?
|
|
|
Re: Opinions on the state of play.
Restricting the source code and restricting hasrate by brute force is the wrong way to go and unlikely to win friends. Excessive tinkering at this point would be unwise and it seems good the way it is right now imho. Far better to simply get the message across to the miners with over say 1 Mh/s at their disposal that they are actually the problem. These miners need to realize that they could be throwing far far less hashing at it and get much higher rewards. Yeah - it's counter-intuitive and people need to wise up. Perhaps this particular feature requires greater emphasis in publications. From a few back-of-a-cigarette-packet calculations I reckon miners should be aiming for a maximum 200 Kh/s each, then we can see how the totals work out in more detail. The only problem I see with this approach is that self-restraint in not general human nature while greed is generally the norm. XMG is different - greed should not be rewarded.
Very suggestive comments, Spexx; you're right we should emphasize lower hash getting higher rewards. There is a feature I didn't disclose yet, the diff where maximum XMG occurs increases over time, that will allow more and more people mining XMG and share the maximum rewards later on. Thank you very much, dcct. I love the explorer, particularly the diff vs time graph: It's clear that diff is nearly constant between 09/18 and 09/21, while it declines after 09/21 when hard fork happened. Currently 530 active miners.
|
|
|
Check out the pool statistics please, if you suspect that; no more wording arguing, just check out everything you suspect, and figure how your guess works.
|
|
|
The XMG trading volume has broken 1 BTC yesterday, and now rise up to more than 2 BTC; this is very good to a new coin, especially we're on a new exchange; importantly XMG had a consistent transaction since launch. Don't worry too much the price, volume is most important we should be looking at at this moment. All should spread the news, tweet and facebook, @BittrexExchange in any circumstance. https://cryptoine.com/trade/xmg_btc
|
|
|
很喜欢这个硬币,确实做到了纯CPU算法,作者真心不错,赞一个的说 This sounds positive. Good comments on the second Magicoin XMG Thread. I am pleased that the Chinese community liked this coin, usually they object to new coins without reasons likely because there are so many out there.
|
|
|
Please Help with ubuntu_14_amd64_magi-qt_v1.0.0.2. I'm getting the following error: Error initializing database environment /home/tony/.magi! To recover, BACKUP THAT DIRECTORY, then remove everything from it except for wallet.dat.
Removing everything form .magi dosen't help. Here is my debug.log: Magi version v1.0.0.2-magi (2014-09-20 22:27:22 -0400) Using OpenSSL version OpenSSL 1.0.1f 6 Jan 2014 Startup time: 14-09-25 21:22:38 Default data directory /home/tony/.magi Used data directory /home/tony/.magi dbenv.open LogDir=/home/tony/.magi/database ErrorFile=/home/tony/.magi/db.log ERROR: CDB() : error Invalid argument (22) opening database environment
Here is my db.log BDB0055 illegal flag specified to DB_ENV->open BDB0055 illegal flag specified to DB_ENV->open
Looks like because of db. can you try compilation from source code? I had the same error on a Gentoo install when I compiled from source. The issue was that I have multiple versions of libdb and needed to specify witch version to use. Thanks ex33s, seems like the same error.
|
|
|
[A quick update]
# Have a report about the new block rewards due (already take too long time), post most likely tomorrow; and then launch the proof of mining campaign.
# We had a discussion about the mining today, and different voices about algo changes. I am sure if we stay with the current rewards (most of time we're getting 5 XMG/block though we suppose to see coming 300 XMG), we will need to extend the PoW-I mining period; because of the low block reward, coin swap may need to be extended too. All prior magicoin holders must understand this situation. We have to keep the amount of coin swapped less than the freshly mined XMG in order to protect the market. If XMG crashes, no point of doing swap and even the existing of magicoins. Hope you all agree with this!
# We will carrier out coin swap in this week as we scheduled; I've received several messages asking for swap; I have something more important to do, so please be patient. I will assure some of coins to be issued in this week, but again I don't want see impacts on the price. If you're a prior magicoin holder, please continue to be a holder, that will allow us to issue more coins for swap in the near future.
|
|
|
Thanks for help, I'm happy to report that it builds and runs fine with magi-qt-or.pro under Ubuntu 14.04 with qt5.2.1. (the other file magi-qt.pro gives the errors I posted) I'm not sure what to suggest for the problem with the database though, everything works fine for me.
The wallet you built has a bitcoin-like look, while compiling with magi-qt.pro looks nice. I actually used magi-qt.pro for general compilation, for example, the file here: http://cryptomagic.com/files/magi-release/ubuntu_14_amd64_magi-qt_v1.0.0.2 . can you try this in your system? (if double click not working: chmod 755 ubuntu_14_amd64_magi-qt_v1.0.0.2) Very interesting! After building from source I ran the resulting file once and it worked just fine. When I tried using the original version ubuntu_14_amd64_magi-qt_v1.0.0 after this it gave the database error and won't start. Now the only thing that will work on my system is the new file I just compiled using the magi-qt-or.pro The version here must be v1.0.0.2, otherwise won't work original version ubuntu_14_amd64_magi-qt_v1.0.0 after This is sort of strange. My compilation is under ubuntu 14 too, with the latest updates, or because of db version?
|
|
|
Thanks for help, I'm happy to report that it builds and runs fine with magi-qt-or.pro under Ubuntu 14.04 with qt5.2.1. (the other file magi-qt.pro gives the errors I posted) I'm not sure what to suggest for the problem with the database though, everything works fine for me.
The wallet you built has a bitcoin-like look, while compiling with magi-qt.pro looks nice. I actually used magi-qt.pro for general compilation, for example, the file here: http://cryptomagic.com/files/magi-release/ubuntu_14_amd64_magi-qt_v1.0.0.2 . can you try this in your system? (if double click not working: chmod 755 ubuntu_14_amd64_magi-qt_v1.0.0.2)
|
|
|
Please Help with ubuntu_14_amd64_magi-qt_v1.0.0.2. I'm getting the following error: Error initializing database environment /home/tony/.magi! To recover, BACKUP THAT DIRECTORY, then remove everything from it except for wallet.dat.
Removing everything form .magi dosen't help. Here is my debug.log: Magi version v1.0.0.2-magi (2014-09-20 22:27:22 -0400) Using OpenSSL version OpenSSL 1.0.1f 6 Jan 2014 Startup time: 14-09-25 21:22:38 Default data directory /home/tony/.magi Used data directory /home/tony/.magi dbenv.open LogDir=/home/tony/.magi/database ErrorFile=/home/tony/.magi/db.log ERROR: CDB() : error Invalid argument (22) opening database environment
Here is my db.log BDB0055 illegal flag specified to DB_ENV->open BDB0055 illegal flag specified to DB_ENV->open
Looks like because of db. can you try compilation from source code? Maybe I need to install different library versions but I keep trying to build under Ubuntu 14 but get these errors, so I've been using the provide file: overviewpage.cpp:49: error: 'qVariantCanConvert' was not declared in this scope if(qVariantCanConvert<QColor>(value)) ^ overviewpage.cpp:49: error: expected primary-expression before '>' token if(qVariantCanConvert<QColor>(value)) ^ what is you qt version? I've tested both qt4 and qt5; you can use magi-qt-or.pro and magi-qt.pro, see if one of them works.
|
|
|
Please Help with ubuntu_14_amd64_magi-qt_v1.0.0.2. I'm getting the following error: Error initializing database environment /home/tony/.magi! To recover, BACKUP THAT DIRECTORY, then remove everything from it except for wallet.dat.
Removing everything form .magi dosen't help. Here is my debug.log: Magi version v1.0.0.2-magi (2014-09-20 22:27:22 -0400) Using OpenSSL version OpenSSL 1.0.1f 6 Jan 2014 Startup time: 14-09-25 21:22:38 Default data directory /home/tony/.magi Used data directory /home/tony/.magi dbenv.open LogDir=/home/tony/.magi/database ErrorFile=/home/tony/.magi/db.log ERROR: CDB() : error Invalid argument (22) opening database environment
Here is my db.log BDB0055 illegal flag specified to DB_ENV->open BDB0055 illegal flag specified to DB_ENV->open
Looks like because of db. can you try compilation from source code?
|
|
|
What is your opinion about the following idea? We talked about it long time ago, but didn't push it further (had a discussion with Bojcha too): modify the algo, keep it half-closed source, and pool setting a limit to the hashrate.
That was mine proposal for this hashrate limiting. If this 5 coin reward stays so and hashrate does not fall under 50MH/s, it will be needed much longer time to mine all coins. This can be double-edged sword for sure but it's possible. Here is how it should work, by also looking and learning on errors of other coins that used same thing. - Source is (how i like to call it) half-closed, meaning olny dev, pools and exchange have source. - wallet mining disabled - pools limit hashrate - pools need to have worker limit (1 worker) - if more PC's are in use, all can be pointed to 1 worker without problems. - etc.. This way hashrate will be easy controlled and easy to follow by everyone. Everyone can follow blocks on pools so if some blocks are missed then someone is mining out of system. However when POS blocks starts in the middle of POW those block will be missed on pools ofc! So what you all think? Are those proposals a JOKE?Bojcha is proposing an idea to make the coin be minable by most of people that will eliminate the 10-MHps miners; some other coins already used this idea. Just a thought, would say, if more people follow, that will be something seriously to be taken, what would you say? Yea, but that's not the way... it's like trying to stop diseases by limiting access to medicine ;-) considering somewhere around 5MHps, so people can still get the amount paid proportional to their rig (not so powerful to freak out small miners ) Sounds like a lot of work and I really don't think your going to change the situation much or limit the hash rate per person if that is the intent. There is nothing that prevents the same person from making multiple accounts on the pool and sending payments to multiple wallet addresses. Even a limit of one worker per ip address won't really change anything for someone the least bit technical. Plus open source helps everyone have confidence in the coin so that things like this are less likely: http://blog.cryptsy.com/post/84830322907/asiacoin I trust you guys but I shouldn't have too. In many ways this is really nice right now, price is high, large community involvement, enough hash rate to secure the coin, I would just leave it as is. You're right that when sort of limitation placed comes some other issues; people may make fud according to some "hidden" facts unless carely being taken care of. Any way this is yet a thought under discussion.
|
|
|
What is your opinion about the following idea? We talked about it long time ago, but didn't push it further (had a discussion with Bojcha too): modify the algo, keep it half-closed source, and pool setting a limit to the hashrate.
That was mine proposal for this hashrate limiting. If this 5 coin reward stays so and hashrate does not fall under 50MH/s, it will be needed much longer time to mine all coins. This can be double-edged sword for sure but it's possible. Here is how it should work, by also looking and learning on errors of other coins that used same thing. - Source is (how i like to call it) half-closed, meaning olny dev, pools and exchange have source. - wallet mining disabled - pools limit hashrate - pools need to have worker limit (1 worker) - if more PC's are in use, all can be pointed to 1 worker without problems. - etc.. This way hashrate will be easy controlled and easy to follow by everyone. Everyone can follow blocks on pools so if some blocks are missed then someone is mining out of system. However when POS blocks starts in the middle of POW those block will be missed on pools ofc! So what you all think? Are those proposals a JOKE?Bojcha is proposing an idea to make the coin be minable by most of people that will eliminate the 10-MHps miners; some other coins already used this idea. Just a thought, would say, if more people follow, that will be something seriously to be taken, what would you say? Yea, but that's not the way... it's like trying to stop diseases by limiting access to medicine ;-) considering somewhere around 5MHps, so people can still get the amount paid proportional to their rig (not so powerful to freak out small miners )
|
|
|
|