MagiPay is down  It could be down & up randomly; doing some fixing. |
|
|
|
I don't know how to install it, I just know how to download it  If you have the GMP source, you need to compile it. ./configure --enable-cxx --enable-static --disable-shared --enable-alloca=alloca (note1: you may have to specify --build=[your hardware] if config.guess gets it wrong) (note2: using static library gives you a faster miner than shared library) make make check (optional test suite before installing) make install then run your minerd compile again. Incidentally, you need other libraries too, such as CURL. Installation is much the same. I will continue this tomorrow, thank you before, Spexx Also try for debian-like os: sudo apt-get install libgmp-dev |
|
|
|
In order to spread the word about Coin Magi, there is now a puzzle contest with a XMG 1,000 prize available on http://www.coinmagipuzzle.org/The idea is to have as many Coin Magi supporters play the game and submit their score, so their record score is shared among friends on Facebook. Please do not set a worldrecord right away, as that will demotivate others to give it a try, and the goal is to get as many new people as possible get to know Coin Magi! www.coinmagipuzzle.org Thank you very much Digithusiast, great work.  |
|
|
|
Another new wrinkle in the BDB updating: I was reading the packages for Debian incorrectly (and it was pointed out on GitHub)- libdb5.1-dev is only available by default in Debian 7 (wheezy), not Debian 8 (jessie). I really don't know how you'd like to handle that as a dev team. Debian 7 is the "stable" release and Debian 8 is the "testing" release, but I really don't know much about the usage statistics for Debian in terms of what version is more popular. Since Ubuntu 14.04 and Debian 8 both default to using BDB 5.3, though, it may be a reasonable option to just shoot for BDB 5.3 as the actual upgrade choice. Debian 7 users can also use the backports repositories to download libdb5.3 reasonably easily, which means that Ubuntu 13 (and even 12 LTS, I think) users can also compile with minimal effort. I also checked the Raspberry Pi repositories and it appears that armv6l and armv7l both have access to libdb5.3-dev libraries as well (which makes sense since it's based on Debian, but it wasn't certain). And Gentoo and FreeBSD appear to have libdb5.3-dev too. Windows and OSX can use the easily-accessible BDB 5.3.28.NC release from http://www.oracle.com/technetwork/database/database-technologies/berkeleydb/downloads/index-082944.html, so the two more prominent platforms should have no problem either. This time my research into package availability was a little more extensive, so everything should work out if you decide on BDB 5.3. But that will inevitably force people that are using older Linux releases (however many there are) to compile the BDB libraries themselves. If they're on older releases, though, they're probably more comfortable with compiling... But it's also another hoop to go through. Some community input on this might be best, to determine if this will affect anyone enough to take them out of their comfort zone... But I suppose upgrading to BDB 5.1 could have had the same effect. In the end, though, it's your choice as developers to make the call. I can revert to BDB 4.8 if you'd rather stick with that, keep it at 5.1, or rework everything for 5.3. Just let me know. This is a thing I didn't notice; I checked my Mac os compilation which acutally used the version 6. I agree that we should stick to one version. It is likely that the future release of linux (debian and else) steps into more than 5.3. It won't be a big concern if the wallet gets updated by that time as well; let me check it out and fix the way we should take. |
|
|
|
mining really is hard now. as i understand the bigger the hashrate is the lesser the reward right?
isnt it possible to limit the hashrate of an account.?
like for example in supernova you can only have 1 worker?
Exactly; we're trying to get this option for PoM. |
|
|
|
Magi World Online Campaign! Magi (XMG) the unique coin of the future
launches the Magi World Online Campaign
This multiple promotion campaign rewards current community members by receiving some extra XMG and offers new members the opportunity to become acquainted with the Coin of the Magi and receive their first XMG for free.
The tour consists of multiple assignments for which you can receive some XMG. Check here: http://bitcoingarden.tk/forum/index.php?topic=3315.msg89738#msg89738Thanks mate, this is ever unique social to the community. I am confident it only happens to magi because of our passionate and loyal supporting magi team member! |
|
|
|
Yes, this looks fine, while I haven't yet done the compilation; will do so in the following days. |
|
|
|
Someone reported a pretty bad blunder in the documentation in the GitHub repo: https://github.com/magi-project/magi/issues/7. In short, Debian 8 (Jessie) removes libdb4.8 from the official repositories, which the wallets rely on to be built and several other build dependencies were missing from the build documentation. I added the missing dependencies to the documentation in my pull request, but I didn't want to make the decision to change the Berkeley DB version for the official builds as well, since it will screw up the usage of wallet.dat between user-compiled and official versions. I do think, however, that it would be best to officially migrate to libdb5.1 for official builds because it's one more thing that will work out of the box for users. (If the devs talk it over and want to bump up the version to 5.1, let me know and I'll add that to my pull request.) feldenthorne, thanks for the heads up. Let's move to version 5.1. I shall build the binaries as well. |
|
|
|
http://coinmagi.blogspot.com/thanks [img ]http://3.bp.blogspot.com/-GEd0APSfkRA/VR_D9M7AyHI/AAAAAAAAA0o/ZQDjMMDsc5Y/s1600/coinmagi-blogspot-com.PNG[/img] [img ]http://2.bp.blogspot.com/-mnKpwuAi3d8/VR_D92fjOGI/AAAAAAAAA0w/A1m5Wv6nTko/s1600/coinmagi-blogspot-com-about.PNG[/img] I LOVE MAGI COIN...  Thanks guys. I love magi too. You know what, when I look through stuffs, posts, sites, and work on the stuffs even simply writing replies to posts, I forgot everything else; time goes by faster than usual. It's sad that coming back to life surrounds by many many real stuffs to cope with. |
|
|
|
UrgentMaxminers XMG pool needs more support. If you can switch over your hashpower it would be appreciated Spread the hashpower guys! Some other nice news: Message from Cryptoine: #Cryptoine users will receive 100% XMG refund. Thanks to @coinmagi donation. Unique #Magi community. Thank you for your cooperation. #XMG Awesome Joe! Well done. Will wait for their response about when refund starts, then we will respond to that. I do hope Cryptoine will survive in this incident; seems like they have a plan. |
|
|
|
i want ur coin on cryptsy my main trading exchange u have a campaign running to get listed there? @111magic Magi XMG Proof of Interest 2015 is a great initiative thx for organicing it magi did move in my investment priorities on slot 3 so u clear a horse i bet on its not in investment amount on slot 3 because for that u are still to cheap dont wana buy 25% of total coins  we have high respect about the achievements of magi dev team and will include some of their stuff into DMD Diamond code magi seems to me high undervalued compared to dev team and community size and activity Thanks friend; please don't buy too much cause we're supposed to get coins into more hands. |
|
|
|
As i see in this page, block height = 248823, if hashrate from 30 to 40 MHz, the reward will be 48-18 XMG, But in real time, the network hashrate at this moment are 30-34MHz, but the newest block values only 5-6 XMG instead of 47  The block rewards are actually calculated using the average of the previous 2000 block difficulties... so the plotter is probably correct, but it operates as if your inputs are the average difficulty on the network, not the instantaneous difficulty. So the average hashrate for the last 2000 blocks has apparently been ~46 MH/s. It's possible to address this issue by keeping a log of block difficulties and performing a rolling average of the most recent 2000 blocks... but that's a lot of work. It's probably easier to check the most recent block's reward and to use that as a guideline for where the hashrate is. Thanks for your info But i personally think that there is a problem with 2000blocks time.... - Magicoin has unique POW: if hashrate is high, the block reward will drop => high hashrate miners will not get much benefit than lower ones => they'll leave or use less hashpower => hashrate lower => block reward raises => lower hashrate miners who stay will get better block rewards. But If block reward was caculated with average of 2000 blocks's hashrate: - If hr is high => reward will drop => high hr miners will leave and mine another thing, until the reward raise again => they mine XMG again => lower hr miners who stay wont get good amount of XMG ( because event when reward high, they only get small amount of shares ) It happen because the time we mine 2000 blocks is long enough to high hr miners switch coins... If the time is shorter, high hr miners wont have enough time to switch. Just my personal thought  Let me bring this up again. Actually the average is done for the past 100 blocks mostly; in other words, only the most recent 100 blocks affects the block reward. There is a complication behind the scene, and it's neither a simple average, nor a simple moving average. The 2000 block average is here - rDiffAver: https://github.com/magi-project/magi/blob/master/src/main.cpp#L987However, rDiffAverEMA is the actual quantity of diff for block reward computation, which is done over the past 100 blocks. rDiffAver comes into effect in here: https://github.com/magi-project/magi/blob/master/src/main.cpp#L1022, simply providing a diff baseline. rDiffAver is used to determine diff deviation. The deviation gets either amplified or compromised; this way re-adjusts the "deviation" which is regarded as a normalization of the fluctuation to better deal with real situations. This is to discourage block reward due to big-miner caused great fluctuation of diff, while the effect of the natural fluctuation of diff needs to be mitigated (the diff compromising). When I look back this right now, I do realize the idea is complicated, while it seems that we do have stabilized the block reward. Any comments are welcome. |
|
|
|
If you're talking about the undershoot between D=2.25 and D=2.625,  , that's a problem with using Bezier curves to fit a line to the points, not a point calculation issue. I've already included the whole of GetProofOfWorkReward_OPM(). Because that was a little misleading, though, I just added the ability to set the number of sampling points for the curve, which should fix the aliasing issue if you add enough points (I set the default to 15). I'd just kill the Bezier curve use altogether, but the amount of points necessary to make a smooth curve without them makes the plots look cluttered. Now I got it , that's fine and actually the trivial part; people shall get the idea; thanks for the site. |
|
|
|
Very nice picture again Hefty! Sharp view and modern, well done!  Loving this pic. Superginormouslyfantasmagorical would be too small a word to describe it. Like I can reach out and touch them. They exist! I want some! Me too, nice work, Hefty. Probably "COIN OF THE MAGI" better than "THE COIN OF THE MAGI". How does standalone logo look like in 2D? |
|
|
|
Nice work; a bit wondering about the reward not hitting zero? (actually minimum mining fee) at high difficulty values.
I grabbed GetProofOfWorkReward() from main.cpp, which has an if (nSubsidy < 3) nSubsidy = 3; in the PoW phase 2 code.
Now that I look at this, having had some more sleep, should I be using the GetProofOfWorkRewardV2()? Which I guess would mean GetProofOfWorkReward_OPM()?Edit: I swapped the script to use GetProofOfWorkReward_OPM(), for ( BLOCK_REWARD_ADJT_M7M_V2 < nHeight < END_MAGI_POW_HEIGHT_V2). But the block reward still continues indefinitely as MIN_TX_FEE if (nHeight >= END_MAGI_POW_HEIGHT_V2), as per the code. I also fixed point calculation because it was concatenating floats as strings, which screwed up middle points on the plot when low difficulty was greater than 0. Hard refresh (Ctrl+F5) or clear your cache if you're stuck on the old one. GetProofOfWorkReward_OPM() is the right one; I am looking at block 242212; there is a rising up to diff = 2.625 after the dip, that's calculated by https://github.com/magi-project/magi/blob/master/src/main.cpp#L1064, anyways this is a trivial part though. Here is a figure showing the reward vs diff: https://bitcointalk.org/index.php?topic=735170.msg9991269#msg9991269 |
|
|
|
Since people seem to ask about the fluctuation in block rewards pretty frequently, I put together a responsive HTML/JS page that makes a pretty plot based on an input block number and difficulty range. It outputs stuff like this:  You can play around with the actual plotter here: http://starflakenights.net/crypto/blockreward/xmg.html. I hope it helps explain block rewards to someone down the line, but it was fun to finally figure out how Javascript works regardless. Nice work; a bit wondering about the reward not hitting zero? (actually minimum mining fee) at high difficulty values. |
|
|
|
Magi XMG Proof of Interest 2015 Launch 01-04-2015 Earth is something Magical. Coin of the #Magi will show the magic of digital currency! (quote twitter @103tango) Banks give interest. Today, not much! Magi does this better!
The Coin of the Magi is the digital currency of the future, fair unique and for all people living everywhere!
Rules for first Magi Proof of Interest 2015!The base is very simple.
Time period: The Proof of Interest will last two months.
When can I register to participate? Registration is now open!
How do I sign up? Tell me that you want to join the PoI here: http://bitcoingarden.tk/forum/index.php?topic=3265.0
What information should I include? Give your wallet XMG address in a post here: http://bitcoingarden.tk/forum/index.php?topic=3265.0 (only one address allowed to join)
I want to join the Proof of Interest but don't want to share my walletaddress? Just PM me the information.
I will check the balance, and that balance will start participating in the PoI. (After confirmation participant)
When will I receive my interest? Interest will be paid on 01-06-2015
What happens if I have more XMG in my wallet on 01-06-2015? You will receive interest on the amount present in your wallet on that date. (Advantage participant)
What happens if I have less XMG in my wallet on 01-06-2015?
you will not receive any interest if you have more than 20% less coins in your wallet! (Drawback participant)
What happens if I XMG have used to pay for goods? This has no negative effect on your interest. (Receipt required)
How will be interest distributed? The interest will be distributed by means of a specific calculation. This can be influenced by the number of participants, level of the fund and total number of coins that participate.
Who will pay the interest for this Proof of Interest campaign? I received the first donation of 25,000 XMG. On his request, the donor will remain anonymous!
Interest will be paid to the designated address wallet.
Changes during the Proof of Interest are not possible.
Exchanges or wallet address on an exchange are excluded from participation.
If you have questions don't hesitate just ask me.
Thanks mate for this great movement, and sorry for my absence. I am currently subject to some massive personal stuffs (mostly negative  ). I will post something regarding this situation soon. |
|
|
|
Message from Cryptoine!
2015-03-27 21:26 UTC
Users will receive a refund in the following amounts:
...
It's nice to see Cryptoine's action; I hope the security concern is improved later on and look forward to their return. |
|
|
|
|
Show Posts
