Skip to content

Commit

Permalink
Fixed OpenCL bug where incorrect keys would be reported if multiple keys
Browse files Browse the repository at this point in the history
were found in the same kernel call.
  • Loading branch information
brichard19 committed Nov 30, 2018
1 parent 0d55dbd commit 9e924bb
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion CLKeySearchDevice/CLKeySearchDevice.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -420,7 +420,7 @@ void CLKeySearchDevice::getResultsInternal()
KeySearchResult minerResult;

// Calculate the private key based on the number of iterations and the current thread
secp256k1::uint256 offset = (secp256k1::uint256((uint64_t)_blocks * _threads * _pointsPerThread * _iterations) + secp256k1::uint256(getPrivateKeyOffset(ptr->thread, ptr->block, ptr->idx))) * _stride;
secp256k1::uint256 offset = (secp256k1::uint256((uint64_t)_blocks * _threads * _pointsPerThread * _iterations) + secp256k1::uint256(getPrivateKeyOffset(ptr[i].thread, ptr[i].block, ptr[i].idx))) * _stride;
secp256k1::uint256 privateKey = secp256k1::addModN(_start, offset);

minerResult.privateKey = privateKey;
Expand Down

2 comments on commit 9e924bb

@sponnusa
Copy link

@sponnusa sponnusa commented on 9e924bb Nov 30, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Somehow, it doesn't detect the keys properly. For example, I'm loading it from a file which contains some 682 addresses generated from directory.io and they are continuous, but on my system (Capverde 2GB) the clBitcrack does not detect. My keyspace starts from 0 and attached are the input files and the private key reference for checking. Somehow, it just keeps on calculating, but doesn't print anything.

Any tips for troubleshooting? I tried with multiple combinations and even single addresses, but it just doesn't detect / print the private key. Unfortunately, I don't have any other H/W to test it.

Thank you.

addresses with private.txt
input.txt
capture

@dem10
Copy link

@dem10 dem10 commented on 9e924bb Dec 1, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The error persists R9 390X
ccc1

Please sign in to comment.