Thanks for inputs itod. Now I see another advantage with the CPU coin. Magi will have most of coins to be mined firstly (depending on the diff to ensure fair distribution), and then long-term mining period with much less reward (GPU won't matter much if out in this period). I think we can go this direction.

I am sorting out things; will announce the plan soon (apologize for many times of saying "soon").

Unfortunately cudaminer is not working yet; I've spent a few days on this, my mac didn't work out well initially so I used an Amazon EC2 spot instance and spent sometime too on the driver, cuda stuff. After some tests on cudaminer with complainings, I turned to ccminer. My initial thinking is that all about the block header but I was wrong; actually the block header does lead to a very different implementation of M7 using cuda. This basically means a different cuda version of M7 to be done for XMG, although we are using the same M7 as XCN, that'll be like recalculation of all the stuffs. This looks like unlikely for me to accomplish within a short time. Somehow it has been nearly two weeks since 1st testnet, and my focus was totally on the miners instead of the PoS-II. I think from now on I should place my emphasis on other stuffs. In any cases, the standalone cpuminer is ready.

Realizing the actual difference of the M7 implemented in standard block chain compared to the minichain, I think it won't be necessary to keep the same form of M7 as in XCN. An interesting thing about M7 is the use of multiplication of hashes. The multiplication is done by using GMP which allows arbitrary precision, only limited by available memory of the machine. This makes me thinking of an interesting feature to add into XMG: we can repeat many times of multiplications which literally increase the memory needed; the memory relies on the repeating times. This repeat is not just to get a pointless dataset to 'eat' memory, instead these 'huge' numbers are hashed by sha256 as the final. One of the consequence is that we can make GPU miner hard to be implemented. So it will be like tending to be a CPU coin, but I don't see any unlikely of GPU miners in the future. Another consequence is it could be memory hard (that also means not energy efficient by mining with GPU, efficiency will depend on the multiplication times), so the CPU/GPU mining could have a higher efficiency ratio compared to the pure M7, though it remains to be confirmed. It will also be possible to use varying multiplication times with time/block height etc to make GPU even harder. I am open to suggestions.

Since a few days on the miners, I will need sometime back to the coin itself; it will be assured my next update will be about the official release plan.

The AMD miner is not available, here is a CPU miner: https://github.com/magi-project/magi-minerd.

Had a hard time in dealing with the cudaminer testing, will work on it a while; In any cases, I will announce a schedule for the formal launch in following days.

you're right, AMD is not out yet.

Thanks again, truckythin, appreciate your help; I figured I may use my mac Nvidia for test or I'll try GPU Cloud; will update ASAP (a bit away from stuffs today).

Thanks truckythin. This sounds weird but seems like the only way we can do. I've been working with the cpuminer constantly checking outputs and adjusting the code, real pain. I am thinking if I should buy a Nvidia that might leads to complication; I'll leave that as the final, or genius people can take care of the miner.

What I can see is the nonce is not updated after finding a block. Can you run the miner again (anytime at your convenience), just updated github, need to see further outputs (all outputs you get).

Hi truckythin, can you try out cudaminer again (use the new uploaded git source)? debug output must be enabled, which can be done by giving "-D" or "--debug" in the command line parameters. Once a block is found, some info will be issued right before exit. Copy those after "Submit work". Thanks in advance.

This means the block under inquiry is PoW block.

Guess there are bugs to be fixed, works submitted successfully but not actually passing through.



This is out of expectation since block time is 3min; will check the code.

Compiling the windows miner, even cpuminer is a headache right now.

Keep me posted.

Thanks, nice work. 

Thanks advice, will PM for helps.

Nicknha (cant find your forum username), if you see this post, pls contact me for windows compilation. Thx.

Hi truckythin, unfortunately I don't have Nvidia to test and pinpoint the error quickly; anyone knows how to mine with Nvidia GeForce 9400M on mac will be a great help.

Looks like I found a bug during work submission, just uploaded new code to github. Can you try it out?

Never noticed the GPU server, though the price is a bit heavy to handle $0.65/hr.

Looks like I am relying on volunteers here for the testing, hope we can get the miner done before launch; or we have to wait people optimizing the miners once source code is available on git.

Thanks; PMed you.

Current block is 1010, your sync seems ok. Some prior posts indicated possible sync issue or conf file (rpcallowip and port).

https://bitcointalk.org/index.php?topic=408268.msg7901615#msg7901615
https://bitcointalk.org/index.php?topic=52643.0

Can you see if cpuminer works?

Edit: I just updated wallets half hour ago (http://cryptomagic.com/files/magi-release/, corrected PoS coinage calculation (testnet) and PoS block checking; for whatever reason some blocks generated were picked as having with zero money supply).