Quote from: reorder on January 18, 2014, 04:21:47 pm

Beware, the binary this guy has stolen from mmc.1gh.com is modified and may contain malware (and most certainly it does).

While I commend you for doing the detective work and making sure binaries are not altered, I have an issue with you using the work "stolen" everytime someone uses your binary and modifies it.

How do I know your original binary doesn't have malware to begin with? I have to take your word for it, which doesn't inspire much confidence. You could have malware on the machine that you used to build the binary, even if you didn't intend to include one. The lack of open sourced projects here is not helping the confidence in this coin. There are plenty of people out there who will ONLY build from source.

We could set a bounty for open sourcing both yam and reorder's binaries and then all that "stealing" argument would go away. I'm sure everything and everyone has a price.

Furthermore - is it really stealing if it's already stolen? I could be wrong, but isn't your so called binary built on top of open source that has GNU license, hence the law says you should open source your binaries anyways? It's just hypocritical. I understand that you want to get rewarded for you efforts, and I think we can all benefit a lot more if these projects get open sourced. Then more people can look at optimizations, etc.

For what it's worth. There is no GPL-ed code inside, everything but Python interpreter is original work. While I admit I should have included this link: http://docs.python.org/2/license.html , this seems to be a quite minor violation.

Why not just provide a link to the original download location if one does not plan something nasty?

$ md5sum mc2-1gh-lin-x64.tgz                                                                                                                                                                                                                 
02a3c6231b934e77a2c2fdeda906a23d  mc2-1gh-lin-x64.tgz[/code]

The same md5 are on your files

ORLY?
MD5 (mmc-miner.exe) = 9efeb412c23f33ec9e40b9a934b8f65a


was wondering if there are plans to let us fine tune settings like in cgminer to squeeze out a bit of extra cpm!

cgminer is crunching hundreds thousands rather simple hashes per second so it can let you adjust the 'spacing' between then and how many to process at once. PTS does a couple thousand 'hashes' per minute tops, and running even two threads of it in parallel slows down both in more than half on any card. So, there is essentially nothing to tune. The only 'variable' is memory size, and the miner automatically chooses the best for your card.

Funny, after my last message here, my share per block has gone down to .030 +/- a bit. Have a lot of new miners jumped onto 1GH lately?

Also is 1070 cpm ok on a 770 GTX? Will it get better if I OC the card?

The pool hashrate has increased 15-20% in the last 24h, so indeed your share got lower, but this also means blocks are being found more often on average now. (And the pool luck has improved a lot in the last hours, but it is just a lottery of course).

I think noone has reported CPM for 770 yet, so I cannot tell if 1070 cpm is right for it. Overclocking will improve it of course.

Quote from: Gekko on January 16, 2014, 12:37:45 pm

Quote from: bytemaster on January 16, 2014, 05:41:53 am

I was aiming originally for CPU only and it seems I was more successful than others that have gone before me, but not perfectly.

Could you explain that a little more? What is the problem creating a coin that can only be mined by CPU?
Your answer sounds like it's impossible to create a CPU-only coin, because you have tried to and put a high bounty on what you thought was the solution. Why didn't you know what others (GPU miner creators) now know when you were programming it?
Knowing how the GPU miners work, could you create a CPU only coin now?

Well there is a successfull CPU only coin out there: Primecoin, stable for more than half a year now and impossible to create GPU miners with decent results due to the design of prime numbers being integers It's so simple tbh.

The Creator has created all prime numbers integer indeed, but what does it have to do with GPU mining?

Please keep in mind the coin employs 'Kimoto gravity well' difficulty adjustment retargeting on every single block (!) This, and small/irregular cpm, makes all calculations based on averaging pretty much inaccurate, and this includes calculator, (some of the) charts and hashrate displayed on sites. If you PM me the MMC address you mine with, I could provide you the exact calculation towards your payment for one of last blocks found on 1gh.

Quote from: reorder on January 17, 2014, 12:34:05 pm

We are working on adding yam support now.

Great, I could then also point my cpus (8core opteron, 8core bulldozer, 8core i7, 4 core i7) to the same pool as my gpu rig.
Would I be able to use the same payout address for several workers (gpu&cpu mixed) or would I have to use different?

Whichever is more convenient to you (whether you want separate statistics per worker or aggregated over all workers).