[ANN] cudaMiner & ccMiner CUDA based mining applications [Windows/Linux/MacOSX]

[Spoetnik]

The dev for JackpotCoin posted that they will hardfork the coin as a "fix" to the faster algorithm code... hmmm

https://bitcointalk.org/index.php?topic=584481.msg6413849#msg6413849

the question is did they know about it previously ?

[Spoetnik]

How to use the NVIDIA?
X11 CUDA how to dig

doesn't exist yet...

we took a detour and did the fastest Jackpotcoin miner on the planet

the coin has a serious design flaw, you only need to mine Keccak, and ignore
all the other hashes.

nice to know about Buchner funnels. Hadn't come accross them yet
(although I did use the CUDA funnel shifter before)

just like quark and it's clones.. cough cough Dark coin lol

Would be fun if true... :p

ya old news man other guys figured it out long before me only thing was i was the only one and still am as far as i know that got it working
anyone who used my cudaminer builds for SRC or QRK etc used just what i said..
one of the many changes i did was i cut out one of the algos and dropped it entirely so it was never used what so ever !
search the source code from any other mod makers for "#ifdef CHEAT"
i made that work perfect with no errors ..like 7 months ago lol
that boosted reported hash speed but made little difference on earnings though.
and people wonder why i am the suspicious one around here lol

that supposed cheat code would produce about 40% to 50% bad shares
so what i did was modify the code a bit to improve pre-submit share detection.. a part of my optimizations
So my miner would have no bad shares sent at all what so ever.. you could run all day and night with 100% success rate.
with or with the cheat tweak (drop an algo) functions running.

and again who knew about this ? i am not the guy who wrote in the cheat defines originally other guys figured this out before i did
did the coin devs now this on launch day ?

[atc1]

Well... After the whole, made this guy, stuff, it says Unable to query CUDA driver version! Is an nVidia Driver installed?

Make sure you have driver version 190.38 installed,because apparently in old cards, the newest drivers are more memory aggressive, reporting less free memory to the system. You'll have to revert back to your older drivers if you're going to use a video card with the bare minimum amount of RAM.

But before that,just download GPU-Z and make sure that the CUDA checkbox at the bottom is ticked. Yes,people have large configs for cards, but that is needed only when you want specific configs,but the autotune is generally a really good option.

[cvax]

yeh i can see a lot of people are going to ask, here is 32bit and 64bit ccminer 0.6 compiled
https://mega.co.nz/#!Aw13XIYD!ETSB1GRSQdmqGt1jnlMLV4ZOhJ__qtfOSc0vOMKyUQY

Thanks bigjme. Is this Compute 3.5? I tried using your compile with my same old groestl bat file. The performance was worse. From 3100+ kh/s down to ~2450kh/s. You experiencing any difference?

[nomad1109]

I am not seeing any (Yay!!!) or (Booooo) going by with all the hashing I see...

[2014-04-26 23:33:06] thread 3: 6946816 hashes, 11132 khash/s
[2014-04-26 23:33:06] thread 5: 6815744 hashes, 10852 khash/s
[2014-04-26 23:33:06] thread 4: 6815744 hashes, 10870 khash/s
[2014-04-26 23:33:06] thread 2: 6815744 hashes, 10852 khash/s
[2014-04-26 23:33:06] thread 0: 6946816 hashes, 11277 khash/s
[2014-04-26 23:33:06] thread 1: 6946816 hashes, 11258 khash/s
[2014-04-26 23:33:06] thread 3: 7077888 hashes, 10805 khash/s
[2014-04-26 23:33:07] thread 4: 6815744 hashes, 11118 khash/s
[2014-04-26 23:33:07] thread 5: 6815744 hashes, 10750 khash/s
[2014-04-26 23:33:07] thread 2: 6815744 hashes, 11302 khash/s
[2014-04-26 23:33:07] thread 0: 7077888 hashes, 11660 khash/s
[2014-04-26 23:33:07] thread 1: 7077888 hashes, 11181 khash/s
[2014-04-26 23:33:07] thread 3: 6815744 hashes, 11246 khash/s
[2014-04-26 23:33:07] thread 4: 7077888 hashes, 10939 khash/s
[2014-04-26 23:33:07] thread 5: 6815744 hashes, 10632 khash/s
[2014-04-26 23:33:07] thread 2: 7077888 hashes, 10740 khash/s
[2014-04-26 23:33:07] thread 0: 7340032 hashes, 11274 khash/s
[2014-04-26 23:33:07] thread 1: 7077888 hashes, 11288 khash/s
[2014-04-26 23:33:08] thread 3: 7077888 hashes, 10627 khash/s
[2014-04-26 23:33:08] thread 5: 6684672 hashes, 10886 khash/s
[2014-04-26 23:33:08] thread 4: 6946816 hashes, 10854 khash/s
[2014-04-26 23:33:08] thread 2: 6815744 hashes, 10801 khash/s
[2014-04-26 23:33:08] thread 0: 7077888 hashes, 11163 khash/s
[2014-04-26 23:33:08] thread 1: 7077888 hashes, 11324 khash/s
[2014-04-26 23:33:08] thread 3: 6684672 hashes, 11505 khash/s
[2014-04-26 23:33:09] thread 5: 6815744 hashes, 10666 khash/s
[2014-04-26 23:33:09] thread 4: 6815744 hashes, 10784 khash/s
[2014-04-26 23:33:09] thread 2: 6815744 hashes, 10767 khash/s
[2014-04-26 23:33:09] thread 1: 7077888 hashes, 11452 khash/s
[2014-04-26 23:33:09] thread 0: 7077888 hashes, 11288 khash/s
[2014-04-26 23:33:09] thread 3: 7208960 hashes, 10648 khash/s
[2014-04-26 23:33:09] thread 5: 6684672 hashes, 10746 khash/s
[2014-04-26 23:33:09] thread 4: 6815744 hashes, 10852 khash/s
[2014-04-26 23:33:09] thread 2: 6815744 hashes, 10733 khash/s
[2014-04-26 23:33:09] thread 0: 7077888 hashes, 11306 khash/s
[2014-04-26 23:33:09] thread 1: 7208960 hashes, 11022 khash/s
[2014-04-26 23:33:09] thread 3: 6684672 hashes, 10661 khash/s

Is that normal? seems like something is amiss...

Thanks in advance.

[nomad1109]

You wanna know lazy?

Here is what I am running: ccminer.exe -a jackpot -o localhost:15372 -u user -p pass

This is the same config I am running, but I have never solo mined before... should I be getting confirmations or 'boo/yea!' for each hash scrolling by?

I am very unsure if this is actually working right now.

[goo38]

I am not seeing any (Yay!!!) or (Booooo) going by with all the hashing I see...

[2014-04-26 23:33:06] thread 3: 6946816 hashes, 11132 khash/s
[2014-04-26 23:33:06] thread 5: 6815744 hashes, 10852 khash/s
[2014-04-26 23:33:06] thread 4: 6815744 hashes, 10870 khash/s
[2014-04-26 23:33:06] thread 2: 6815744 hashes, 10852 khash/s
[2014-04-26 23:33:06] thread 0: 6946816 hashes, 11277 khash/s
[2014-04-26 23:33:06] thread 1: 6946816 hashes, 11258 khash/s
[2014-04-26 23:33:06] thread 3: 7077888 hashes, 10805 khash/s
[2014-04-26 23:33:07] thread 4: 6815744 hashes, 11118 khash/s
[2014-04-26 23:33:07] thread 5: 6815744 hashes, 10750 khash/s
[2014-04-26 23:33:07] thread 2: 6815744 hashes, 11302 khash/s
[2014-04-26 23:33:07] thread 0: 7077888 hashes, 11660 khash/s
[2014-04-26 23:33:07] thread 1: 7077888 hashes, 11181 khash/s
[2014-04-26 23:33:07] thread 3: 6815744 hashes, 11246 khash/s
[2014-04-26 23:33:07] thread 4: 7077888 hashes, 10939 khash/s
[2014-04-26 23:33:07] thread 5: 6815744 hashes, 10632 khash/s
[2014-04-26 23:33:07] thread 2: 7077888 hashes, 10740 khash/s
[2014-04-26 23:33:07] thread 0: 7340032 hashes, 11274 khash/s
[2014-04-26 23:33:07] thread 1: 7077888 hashes, 11288 khash/s
[2014-04-26 23:33:08] thread 3: 7077888 hashes, 10627 khash/s
[2014-04-26 23:33:08] thread 5: 6684672 hashes, 10886 khash/s
[2014-04-26 23:33:08] thread 4: 6946816 hashes, 10854 khash/s
[2014-04-26 23:33:08] thread 2: 6815744 hashes, 10801 khash/s
[2014-04-26 23:33:08] thread 0: 7077888 hashes, 11163 khash/s
[2014-04-26 23:33:08] thread 1: 7077888 hashes, 11324 khash/s
[2014-04-26 23:33:08] thread 3: 6684672 hashes, 11505 khash/s
[2014-04-26 23:33:09] thread 5: 6815744 hashes, 10666 khash/s
[2014-04-26 23:33:09] thread 4: 6815744 hashes, 10784 khash/s
[2014-04-26 23:33:09] thread 2: 6815744 hashes, 10767 khash/s
[2014-04-26 23:33:09] thread 1: 7077888 hashes, 11452 khash/s
[2014-04-26 23:33:09] thread 0: 7077888 hashes, 11288 khash/s
[2014-04-26 23:33:09] thread 3: 7208960 hashes, 10648 khash/s
[2014-04-26 23:33:09] thread 5: 6684672 hashes, 10746 khash/s
[2014-04-26 23:33:09] thread 4: 6815744 hashes, 10852 khash/s
[2014-04-26 23:33:09] thread 2: 6815744 hashes, 10733 khash/s
[2014-04-26 23:33:09] thread 0: 7077888 hashes, 11306 khash/s
[2014-04-26 23:33:09] thread 1: 7208960 hashes, 11022 khash/s
[2014-04-26 23:33:09] thread 3: 6684672 hashes, 10661 khash/s

Is that normal? seems like something is amiss...

Thanks in advance.

If you are solo mining this is normal, if you find a block it will say Yay!!! and you will get all the coins in the block to yourself.

[nomad1109]

If you are solo mining this is normal, if you find a block it will say Yay!!! and you will get all the coins in the block to yourself.

Much appreciated. I sit and stare then

[goo38]

If you are solo mining this is normal, if you find a block it will say Yay!!! and you will get all the coins in the block to yourself.

Much appreciated. I sit and stare then

Block reward at 100,000 coins 
You will be an instant JackpotCoin thousandaire!

[nomad1109]

Block reward at 100,000 coins 
You will be an instant JackpotCoin thousandaire!

Can anyone (Christian even) explain to me the ramifications of this kind of failure of a coin launch?

I mean, is hashing away on a clearly broken coin going to ever yield any results money wise even if you get a few hundred-thousand coins out of it?

Is there actually people that would even pay real money for the coins that come out of things like this?

I am still pretty new so I haven't encountered anything like this before, but I know Christian mentioned he had already found like 35 blocks in just 3 hours, which would be like 3.5 mil coins already... but who would ever buy those?

Thanks for any background on events like this or what the results are.

I am mining away hoping to see a 'Yay!' at some point.

[goo38]

Block reward at 100,000 coins 
You will be an instant JackpotCoin thousandaire!

Can anyone (Christian even) explain to me the ramifications of this kind of failure of a coin launch?

I mean, is hashing away on a clearly broken coin going to ever yield any results money wise even if you get a few hundred-thousand coins out of it?

Is there actually people that would even pay real money for the coins that come out of things like this?

I am still pretty new so I haven't encountered anything like this before, but I know Christian mentioned he had already found like 35 blocks in just 3 hours, which would be like 3.5 mil coins already... but who would ever buy those?

Thanks for any background on events like this or what the results are.

I am mining away hoping to see a 'Yay!' at some point.

I think the idea is not so much support for the coin itself from most people, but the expectation that an exchange will pick up the coin.
If it has enough interest where people want to trade it for profit, then the miners can start selling the coin to the traders who want to play the market.

Let's say an exchange opens a JackpotCoin market and some trader wants to buy it for 0.0000050 and you have one blocks worth of the coin (100,000) you can sell for these for BitCoin.
The price is hypothetical, but if you can sell 100,000 at 0.0000050 that is 0.5 of a bitcoin or roughly 225 USD. So if you mine for a bit and are lucky enough to find a block and sell it you can make a bit of money; potentially more than mining at a multipool in the same time frame.

[cbuchner1]

I am not seeing any (Yay!!!) or (Booooo) going by with all the hashing I see...

[2014-04-26 23:33:06] thread 3: 6946816 hashes, 11132 khash/s
[2014-04-26 23:33:06] thread 5: 6815744 hashes, 10852 khash/s
[2014-04-26 23:33:06] thread 4: 6815744 hashes, 10870 khash/s
[2014-04-26 23:33:06] thread 2: 6815744 hashes, 10852 khash/s

pro tip. With the -q option you'll only see this:

Code:

[2014-04-27 00:32:31] accepted: 15/15 (100.00%), 69609 khash/s (yay!!!)
[2014-04-27 00:33:01] accepted: 16/16 (100.00%), 68731 khash/s (yay!!!)
[2014-04-27 01:36:51] accepted: 17/17 (100.00%), 69243 khash/s (yay!!!)
[2014-04-27 01:39:14] accepted: 18/18 (100.00%), 68866 khash/s (yay!!!)
[2014-04-27 01:45:52] accepted: 19/19 (100.00%), 57464 khash/s (yay!!!)
[2014-04-27 02:17:15] accepted: 20/20 (100.00%), 68433 khash/s (yay!!!)
[2014-04-27 03:18:12] accepted: 21/21 (100.00%), 68690 khash/s (yay!!!)
[2014-04-27 04:02:30] accepted: 22/22 (100.00%), 69513 khash/s (yay!!!)
[2014-04-27 04:31:51] accepted: 23/23 (100.00%), 69313 khash/s (yay!!!)
[2014-04-27 04:34:03] accepted: 24/24 (100.00%), 67704 khash/s (yay!!!)
[2014-04-27 05:52:48] accepted: 25/25 (100.00%), 69604 khash/s (yay!!!)
[2014-04-27 07:03:44] accepted: 26/26 (100.00%), 59688 khash/s (yay!!!)
[2014-04-27 07:11:30] accepted: 27/27 (100.00%), 68527 khash/s (yay!!!)
[2014-04-27 07:52:12] accepted: 28/28 (100.00%), 68082 khash/s (yay!!!)

Every yay is worth 100000 coins. Above was mined with 68 MHash/s.
So expect about 1 Yay per hour with ~30 MHash/s.

Christian

[cbuchner1]

Block reward at 100,000 coins  
You will be an instant JackpotCoin thousandaire!

Can anyone (Christian even) explain to me the ramifications of this kind of failure of a coin launch?

I mean, is hashing away on a clearly broken coin going to ever yield any results money wise even if you get a few hundred-thousand coins out of it?

Well for one, the huge amount of coins will make this a penny stock (think few satoshis per coin).

The failure with the JHA algorithm at the coin launch and the required hard fork will somewhat
undermine trust in the developers, for sure.

The lottery nature of this coin may attract a few folks, but as I see it the current size of the
jackpot is less than what I've mined in 12 hours. But the jackpot grows with time.

Let's see where this goes.

Christian

[cbuchner1]

new multi-algo coin launch https://bitcointalk.org/index.php?topic=586320.0

I think you might be able to mine this with cudaminer (scrypt) or with ccminer (either groestlcoin or myr-gr algorithm, not sure).

Christian

[cbuchner1]

yeh i can see a lot of people are going to ask, here is 32bit and 64bit ccminer 0.6 compiled
https://mega.co.nz/#!Aw13XIYD!ETSB1GRSQdmqGt1jnlMLV4ZOhJ__qtfOSc0vOMKyUQY

Thanks bigjme. Is this Compute 3.5? I tried using your compile with my same old groestl bat file. The performance was worse. From 3100+ kh/s down to ~2450kh/s. You experiencing any difference?

on Windows this should now be built in four flavours, when done correctly

Compute 2.0  with #define MAXWELL_OR_FERMI 1   <-- Fermi
Compute 3.0  with #define MAXWELL_OR_FERMI 0   <-- old Kepler
Compute 3.5  with #define MAXWELL_OR_FERMI 0   <-- highend Kepler and GT630/640 with compute 3.5
Compute 3.5  with #define MAXWELL_OR_FERMI 1   <-- for Maxwell

the flag must be set in both .cu modules with "groestl" in its name. It affects
the speed optimization of the Groestl code.

at some point I will code a runtime selection of the MAXWELL_OR_FERMI flag.

Christian

[nomad1109]

Every yay is worth 100000 coins. Above was mined with 68 MHash/s.
So expect about 1 Yay per hour with ~30 MHash/s.

Christian

I am not sure everything is right, but I am going to leave it overnight and see what happens...

Even without rounding it looks like each 750ti is doing 10Mhash/s or more, so with 6 of them I would think it is doing about 60 Mhash/s?

Haven't found anything in over an hour.... which seems odd.

Oh well, at worst I am NOT mining 600 or so Groestlcoins. Not a whole lot of risk in doing this for a few hours even if I have something screwed up.

Thanks for all you do Christian.

[cbuchner1]

Every yay is worth 100000 coins. Above was mined with 68 MHash/s.
So expect about 1 Yay per hour with ~30 MHash/s.

Christian

I am not sure everything is right, but I am going to leave it overnight and see what happens...

Even without rounding it looks like each 750ti is doing 10Mhash/s or more, so with 6 of them I would think it is doing about 60 Mhash/s?

It's been very slow for me also (150 MHash/s total, last block found was 1:45 hours ago).

Time for this to appear on an exchange!

[cayars]

I mined all night on 3 different machines with no Yays on Jackpot.

Time to call it quits and get back to other coins.

[hash-monkey]

Can CudaMiner mine x11 algo?

[Dotcommie]

yeh i can see a lot of people are going to ask, here is 32bit and 64bit ccminer 0.6 compiled
https://mega.co.nz/#!Aw13XIYD!ETSB1GRSQdmqGt1jnlMLV4ZOhJ__qtfOSc0vOMKyUQY

Thanks bigjme. Is this Compute 3.5? I tried using your compile with my same old groestl bat file. The performance was worse. From 3100+ kh/s down to ~2450kh/s. You experiencing any difference?

on Windows this should now be built in four flavours, when done correctly

Compute 2.0  with #define MAXWELL_OR_FERMI 1   <-- Fermi
Compute 3.0  with #define MAXWELL_OR_FERMI 0   <-- old Kepler
Compute 3.5  with #define MAXWELL_OR_FERMI 0   <-- highend Kepler and GT630/640 with compute 3.5
Compute 3.5  with #define MAXWELL_OR_FERMI 1   <-- for Maxwell

the flag must be set in both .cu modules with "groestl" in its name. It affects
the speed optimization of the Groestl code.

at some point I will code a runtime selection of the MAXWELL_OR_FERMI flag.

Christian

I'm guessing the build bigjme made was for maxwell and that's why my 670 in the system is reporting crazy high hashrate, but is there a chance it's actually hashing between 1-2Mhash? lol  (I normally run separate bat files but I just left it since it looks like I've missed the train on this one anyways)