Bitcoin Forum

Alternate cryptocurrencies => Altcoin Discussion => Topic started by: finnjaevel on February 11, 2014, 07:27:55 PM



Title: Maxcoin -- Time to take the crown back from NVIDIA
Post by: finnjaevel on February 11, 2014, 07:27:55 PM
Have you noticed that your WU is extremely low when mining Maxcoin with modified cgminer ?

I had WU of ~80 on my R9 280X when hashing @360MH/s. I fixed the kernel and now WU is ~1300 !!!

Here is an optimized and corrected kernel:
https://anonfiles.com/file/4507f9f7232f2c1f8a8f8d3762528740 (https://anonfiles.com/file/4507f9f7232f2c1f8a8f8d3762528740)

Instructions:
- Save/Backup your keccak130718.cl file if things don't work as expected...
- Overwrite it with the file from zip
- Delete all *.bin files (in my case keccak130718Tahitigv1w64l8.bin)
- Restart cgminer and go for it !

With the updated kernel I had to lower the intensity to get rid of the HW errors. Now running with I = 10 and WU hits 1300!

EDIT: These changes do not give much benefit. In most of the cases only WU-meter is affected.


Title: Re: Maxcoin -- Time to take the crown back from NVIDIA
Post by: Shao128 on February 11, 2014, 07:55:29 PM
I looked at the changes you made (4 lines) and it's not increasing anything except the number that is displayed.  I'm not sure if you actually believe that there is any improvement or you just posted this in hopes of people seeing a bigger number and would send you a donation.  


Title: Re: Maxcoin -- Time to take the crown back from NVIDIA
Post by: HashEngineering on February 11, 2014, 08:06:41 PM
I looked at the changes you made (4 lines) and it's not increasing anything except the number that is displayed.  I'm not sure if you actually believe that there is any improvement or you just posted this in hopes of people seeing a bigger number and would send you a donation. 

Impressive.  Posting source code is good enough for some, but those that can read it can see if it will really work as advertised.


Title: Re: Maxcoin -- Time to take the crown back from NVIDIA
Post by: rocketron on February 11, 2014, 09:03:47 PM
can also confirm this, does nothing


Title: Re: Maxcoin -- Time to take the crown back from NVIDIA
Post by: MaGNeT on February 11, 2014, 09:05:37 PM
This is the first scam that made me laugh ;D



Title: Re: Maxcoin -- Time to take the crown back from NVIDIA
Post by: scarface on February 11, 2014, 09:40:30 PM
to bad maxcoin is a joke and a scam


Title: Re: Maxcoin -- Time to take the crown back from NVIDIA
Post by: peterlustig on February 11, 2014, 11:58:17 PM


The last time somebody tried something this lame was when Realsolid released his Solidcoin miner with inflated hashing values!



~BCX~
That sounds interesting, can you throw us noobs a link?  ;D


Title: Re: Maxcoin -- Time to take the crown back from NVIDIA
Post by: eddilicious on February 12, 2014, 02:21:34 AM
thanks god. I scrolled down before I copy the max address.  8)


Title: Re: Maxcoin -- Time to take the crown back from NVIDIA
Post by: finnjaevel on February 12, 2014, 04:11:29 PM
Embarrassing indeed, but last night I really thought I found the holy grail  ;D

I had no intention of any kind of scam. Maxcoin seems to have a lot of scams going on so I understand your input based on that. Thanks to your replies I ended up doing more research instead of just hasty conclusions. Let me explain...

When miner is started it gets low difficulty/target values from pool. The current kernel discards the lowest difficulty (diff < 16) shares and some valid shares are lost because GPU kernel does not report them. With my changes even those easy (high probability) shares get reported. So one can actually benefit of those changes. This is also the reason why I first thought I had found something really good. It does not only affect the WU-meter. However, a modern GPU gets diff >= 16 difficulty from pool quite fast so it is very true that in the long run with a proper pool (not always disconnecting) my changes do absolutely nothing. Those changes could give some benefit if you had a really old GPU and the pool difficulty stayed low.

So thank you guys for pointing out my newbie mistake. I learned a lot.