Quote from: kTimesG on Today at 11:36:30 AM

Quote from: Akito S. M. Hosana on Today at 07:50:52 AM

130bit test

2F633CBE3EC02B9401000000007000000
2F633CBE3EC02B9401000000009000000
021c20007f8c8984d403a695494d6afbff37f55a01c8bd1aafb9b958fa9485bb02

Done: Total time 00s

Key# 0 [1S]Pub: 0x021C20007F8C8984D403A695494D6AFBFF37F55A01C8BD1AAFB9B958FA9485BB02
Priv: 0x2F633CBE3EC02B9401000000008000000

That is not a 130-bit test, it's a 26-bit range, so the search is for a 26-bit private key that starts from some 130-bit offset (which size's is irrelevant).

26 bit is crackable in less than a second even if using slow-as-shit Python script, which is thousands of times slower than some native fast code.

It only takes around 5000 or so point additions to find the key.

this same test

Kangaroo 2.2 (JeanLucPons) : found the key in 15 seconds
Kangaroo 2.3 (256-bit) : 0.2 seconds
Etar-Kangaroo : no result
Rotor-Cuda: found key in 15 seconds - like Kangaroo 2.2

I am not sure if I am starting those tools with the correct options