Quote from: WanderingPhilospher on Today at 08:33:38 PM

Quote from: COBRAS on Today at 08:28:01 PM

Quote from: WanderingPhilospher on Today at 08:25:38 PM

Quote from: COBRAS on Today at 08:00:06 PM

I thin for fined something with Kanagaroo, is only 1 method - split ranges, mak many file move all to 1 bat file and search byte to byte. BECAUSE RANGES IN KANGAROO IS NOT REAL RANGES !!!

Because with rages from "0 to FFFFFF" blablabla Grin

ranges privkey fined impossible.

p.s. And if you thick what your 5000 Mkey/sec GPU can fined someone in range - NO , YOURS GPU NOT SEARCH IN RAGE !!! YOUR GPU SEARCH ONLY LAST BYTE IN TXT FILE SETTING'S' !!!!!! ONLY LAST BYTE !!!!

What do you mean?

If you start at 0000000000000001 and want to end at FFFFFFFFFFFFFFFF, the program will search entire range.

I will make test and show you, standby.

proof please ? Im very disappointing news about if key 25 byte, range from 0 to 50, THEN PRIVATE KEY WILL NEWER BE FINED !!!

Show please your test !!!

PROOF:

Code:

Start:1
Stop :FFFFFFFFFF
Keys :1
Number of CPU thread: 4
Range width: 2^40
Jump Avg distance: 2^19.97
Number of kangaroos: 2^7.00
Suggested DP: 10
Expected operations: 2^21.25
Expected RAM: 12.0MB
DP size: 12 [0xFFF0000000000000]
SolveKeyCPU Thread 0: 1024 kangaroos
SolveKeyCPU Thread 2: 1024 kangaroos
SolveKeyCPU Thread 1: 1024 kangaroos
SolveKeyCPU Thread 3: 1024 kangaroos

Key# 0 [1S]Pub: 0x026BE95A4D26F8411494CE74B52D6958EC0098411C28F53A3BD5D34711072A4315
Priv: 0x1A3D9

Done: Total time 00s

I ran a quick test, from 1 to 40 bit range (so it wouldn't take much time). I created random private key at roughly 17 bit range. The program found it.

Run the test your self. Place this in your kangaroo folder and save it as rangetest.txt and use it as your input file:

Code:

1
FFFFFFFFFF
026BE95A4D26F8411494CE74B52D6958EC0098411C28F53A3BD5D34711072A4315

yes, I was making test right now and make a post asap....