Quote from: WanderingPhilospher on Today at 04:47:08 AM

Quote from: studyroom1 on Today at 04:35:50 AM

Do i have to remove 04 from bigging of uncompressed key or software can recognize with 04 also?

and seems like one more issue is there

if i am using range like this
49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5eba34000000000000
its running fine in range but when i use 120 range it is calculating range fine but running very below and showing false collision

this started like this
GPU#0 Cnt:0000000000000000000000000000000000000000000000000000000000000001
.....
GPU#0 Cnt:0000000000000000000000000000000000000000000000160cc3800000000001

but i set range 0x800000000000000000000000000000 to 0xffffffffffffffffffffffffffffff

is something wrong with software ?

You can run with 04 in front of uncompressed key's x,y points; you just can not use a compressed key in any format.

The Cnt's are the giant steps. Program offsets (subtracts start range) pubkey on startup and then after all the baby steps and sorting, the GPU starts the giant steps. Nothing is wrong with the program. If you run a smaller range, you will see the same thing and you will see it will solve for the inputted key. False collisions are normal due to 8 bytes stored in hash table.

awesome man got the point i was worried that something wrong with my setup