The pubkey is there so the private key can be found in a few seconds.
How?
000000000000000000000000000000000000000000000017724AFA4320DAF4A7
He assumed the address was within 69.
Good morning, but how did you get the private key for address 19vkiEajfhnHnZjGpogP6Rv8sUQFvF7PiS, having only the public key?
Correct, I made the assumption that the private key for that wallet was in range 69. Since that address has 1 outgoing transaction, it's public key is shown. I ran RCKangaroo with the public key and got the hex private key under 5 seconds, with an RTX4070.
$ time ./run69.sh
********************************************************************************
* RCKangaroo v3.0 (c) 2024 RetiredCoder *
********************************************************************************
This software is free and open-source: https://github.com/RetiredC
It demonstrates fast GPU implementation of SOTA Kangaroo method for solving ECDLP
Linux version
CUDA devices: 1, CUDA driver/runtime: 12.7/12.8
GPU 0: NVIDIA GeForce RTX 4070, 11.99 GB, 46 CUs, cap 8.9, PCI 1, L2 size: 36864 KB
Total GPUs for work: 1
MAIN MODE
Solving public key
X: F5C18F93F837065C3673B64F0426D08283D5097C54C465AF92A399A017DDEBC7
Y: 0C5EBEFBB70A7D8F266754279ECF093963B644D47C49B09B9D4107A051660F27
Offset: 0000000000000000000000000000000000000000000000100000000000000000
Solving point: Range 68 bits, DP 14, start...
SOTA method, estimated ops: 2^34.202, RAM for DPs: 0.232 GB. DP and GPU overheads not included!
Estimated DPs per kangaroo: 4.267. DP overhead is big, use less DP value if possible!
GPU 0: allocated 868 MB, 282624 kangaroos. OldGpuMode: No
GPUs started...
Stopping work ...
Point solved, K: 0.757 (with DP and GPU overheads)
PRIVATE KEY: 000000000000000000000000000000000000000000000017724AFA4320DAF4A7
real 0m4.444s
user 0m2.720s
sys 0m1.805s