been hassling with the new miner as mentioned in the other xmg thread, but could not get it working.
so switched back to the marcus miner again. what to do after the hardfork? will this miner still work?
We will be having a new miner to work with the hard fork. I will post download links. |
|
|
|
It's great to see a coin that is working for a long period. Kudos to the Team and Community.  Thanks Ellie, can't wait to see promo from your experienced skills in the area, and I wish this will be further advancing of our marketing role in XMG later on. |
|
|
|
Continue to pay attention.So far the development of more smoothly.Just suggest dev cared more about the market development.
We have few persons working on the marketing inside and outside bitcointalk, and I also keep talking to exchanges about XMG. We will give more details. Any suggestions/helps to the marketing will be appreciated. hey guys,
any profit calculator for magi???
how many magi/day with win 7 64bit i7 4770?
thanks!
25 XMG! = 1/1000 BTC Interesting estimate. While it would depend on the CPU clock speed to some extent, I would expect this CPU to mine around 50 XMG per day if set up the way I recommend i.e. connected to both mining pools and started as multiple instances of minerd. The machine I use has a processor less than half the speed of an i7 4770 and mines around 20 XMG per day on average with the current algorithm. It remains to be seen how things turn out with the new algorithm. The block reward system makes the actual mining returns very variable and depends very much on the total network hashrate, so any profit calculator would have a hard time giving you an accurate figure. XMG is rather unique! It will be difficult to calculate XMG mining based on a calculator. The block rewards are determined by the network difficulty which is in turn affected by the amount of hash rate people have. Calculating a rough close number will be possible though. To help difficulty stabilizing we will have a new diff adjustment method - MQW, to avoid the large variation, and hence the big holes of rewards. These lucky rewards seem like incentive to mining, but somehow are beyond expectation. The variation is not because of actual varying hashrate, but rather a self-adjustment of the block chain. With the actual constant mining hash, this variation will be a type of oscillation. Similar behavior can be found in the PoS diff. Stabilizing the difficulty absolutely benefits equal block time. The MQW operates like moving average, but does a better job on averaging difficulty at rising side which emphasizes tendency of higher weight on the recent hash variation in the network (really pulled my hair out to deal with this complication). Given more stable difficulty should make the calculation further accurate; either way practice is mining it a day or two  and don't forget the PoM ( https://bitcointalk.org/index.php?topic=802681.0). |
|
|
|
The expected hashrate using the new algo is 2.545 times less than that with the prior algo.
What about the PoM campaign? I currently only have a 35kh/s cpu, so it will fall below the 30kh/s level. Will you also lower the limit on the PoM minimums? Dont worry about the PoM, hashrate will be automatically lowed by taking into account a factor, so the threshold will be around 10kh/s with the new algo. |
|
|
|
I have a 64 bit minerd.exe compiled for the new algo and am currently testing it via the testnet wallet, since I am unaware of any test pool that may have been setup by Noncepool and/or Suprnova. The hashrate I am getting has averaged out at 31.42 percent of the hashrate I was getting on the current algo and it pleases me greatly that this number bears an uncanny resemblance to pi. Thus, to estimate the hashrate you can expect from your CPU, go to https://ww.cpubenchmark.net/cpu_list.phpw and find your CPU Passmark, divide by 1000 and multiply by pi (3.142). Isn't that wonderful?  This 64 bit minerd.exe is intended for pool mining, but works just fine on the wallet without having to specify the coinbase address for payouts, which is nice. However, it only generates "hashmeter" output when it actually mines a block via the wallet so benchmarking takes time, even on the testnet. If people would kindly tone down their hashrate on the testnet, it would make my job here a little easier . The miner seems pretty solid so far - nothing unexpected has happened with it. 100% compatible with my automine.bat too. I have not run it up on a few other processors yet for proofing, but have little doubt that it will prove good. I have a day off work so it will not be long before I am finished testing, so we should be good to go before the hardfork. I am not so certain about a 32 bit version - that is my next main task. That's interesting, pi and you won't believe there is a pi in the new algo too. The 64 bit one is fine. We will need to P2pool to work out direct payout to address. aceoyame, do you have prior experience in setting up p2pool? |
|
|
|
[hardfork] - sorry we have a few hardforks to be done and all gonna happen soon1. M7M-v2 (hardfork on 10/26/2014 9:30:00 AM EST) A switchover of the mining algorithm to M7M-v2 will occur on 10/26/2014 9:30:00 AM EST. Details about M7M-v2 can be found here: https://bitcointalk.org/index.php?topic=735170.msg9230961#msg9230961. The expected hashrate using the new algo is 2.545 times less than that with the prior algo. To continue with mining, download the new minerd (we will add download links here and in the OP soon), and follow the pool mining guide. Be sure that you are using the new wallet v1.1.0.1 too.2. Block rewarding system (hard fork at block 32,750) A change in the block rewarding system is needed. This won't change the block rewards, but to be better to comply with the change of hashrate due to the M7M-v2 algo. The new algo leads to less network hashrate; the new block rewards will have maximum value at diff = 0.68 (for low block height); according to hashrate = diff * 2^32/180, that is about 16 Mh/s. We have also made increasing maximum diff with block height, to allow more people mining later on, e.g., optimum hashrate of 27 Mh/s which produces 300XMG at block 40,000. 3. A new difficulty adjustment method - Magi quantum wave (MQW) (hard fork at block 33,500) Superficially a name here: Magi quantum wave (MQW) ( http://en.wikipedia.org/wiki/Wave_function). This adjustment is done by averaging prior 15 block difficulties. A significant difference here from other adjustment implementations is that each block difficulty accounted is given a weight, and higher weights are given to more recent blocks; in addition to that, block time is also taken into account. Usually the lower difficulty, the smaller block time. The adjustment algo considers less weight of a block which has the lower difficulty. See details here: https://github.com/magi-project/magi/blob/master/src/main.cpp#L12964. Finalizing the PoW-IIAs we can see the PoW-I (will be finished at block 50,000) has produced less coins than expected. To continue the CPU mining, also along with the new algo implementation, it will be very necessary to continue the PoW mining, that will finally make XMG a hybrid PoW/PoS-II coin and that is supposed to remain years long. The hybrid system is more secure than the pure PoW or pure PoS. The PoW-II block reward has maximum 50 XMG and minimum 3 XMG, with the same block rewarding adjustment as the PoW-I. Similarly, the optimum diff grows over time. Wallet v1.1.0.1:http://cryptomagic.com/files/magi-release/v1.1.0.1/Github source code: https://github.com/magi-project/magi
|
|
|
|
Hey there, I worked on Simplicity-MYR and just switched my CPU miners to this coin (still GPU & ASIC mining MYR) I was wondering if anyone would be interested in me writing it to work with this coin? It'd be a minor rewrite and make it much more noob friendly. https://github.com/aceoyame/Simplicity-MYRGranted I would need some other dev's to work with me but we could make it work here too. The new 64bit miner that just came out is a giant clusterfuck and couldn't make it work. This would be much more simple. All you guys need is electrum or for the wallet to export the wallet address in plaintext somewhere as well as P2Pool or a pool that is happy taking wallet addresses as the user name. aceoyame, just had a rough looking over the things, not quite getting the tasks to be done to get this work, but guess we'll need a miner (Spexx's miner should work the way as easy as the miners other people provided) and a P2P (or NOMP, I think), unfortunately we don't have these two options yet. Anyone else may give a hand on this. Thx. |
|
|
|
Another option of compiling on windows is using mingw if you'd like to try that out too. Believe me, I've tried It is really clunky and I have had no end of problems with it. I just can't seem to get a 64 bit version of mingw to play ball with me. I am even having trouble with the 32 bit version this time but will get there eventually. Please let me know when I can run up the testnet wallet again without interfering with anything you are doing at the moment. My new version of minerd for the new algo gives a hashrate around 31 percent of the hashrate obtainable with the current algo, but otherwise has much the same properties and still runs best if started with multiple instances as opposed to multiple threads. It is about 51 percent faster than the miner built into the wallet. Spexx, I've done the testnet, you can run the wallet now, will need to download a new wallet though (from here: http://cryptomagic.com/files/magi-release/testnet/ (v1.0.0.4)), cause I just made a hardfork to implement the new difficulty adjustment algo. If you can detect any difficulty change/network hashrate variation that is more stable than before, let me know. I will be expecting this is what we'll get but testnet has much less hashrate and may hardly tell the truth probably. |
|
|
|
This is very nice, Spexx. I made a link in the OP. Another option of compiling on windows is using mingw if you'd like to try that out too. p.s., writing & testing the difficulty adjustment algorithm, plan to release more info regarding mainnet hardfork tomorrow. Stay tuned. |
|
|
|
Dev please change above Old thread is not working anymore Updated the OP. |
|
|
|
|
Anyone running testnet wallet, please stop it for now; I need to test out the difficulty adjustment in testnet. Thx.
|
|
|
|
nonce-pool, you really did a very good job on XMG. I can remember you tried helping me out the GPU miner when XMG was using the M7 algo (long time ago). I am working on the miner, but you just did it super fast. XMG will donate for your work. Thanks. |
|
|
|
Will compile it in free time, no problem ;-) edit: wallet version didn't change? Thanks, pls wait for the finalized pool miner for compilation; the current wallet version is v1.0.0.3. I'll make new miners for you, greedy miners who even didn't send single coin to donation address :-P So it is only for testnet or mainnet also? If mainnet please update links on 1st page! This is for testnet only right now. |
|
|
|
Will compile it in free time, no problem ;-) edit: wallet version didn't change? Thanks, pls wait for the finalized pool miner for compilation; the current wallet version is v1.0.0.3. |
|
|
|
|
lol, I laughed at what's going on lol
|
|
|
|
|
Show Posts
