Bitcoin puzzle transaction ~32 BTC prize to who solves it

[nomachine]

Subtraction, multiplication, addition.....

This is like the movie Groundhog Day.
About a man reliving the same day over and over and over.
In this case trying to break the ECDSA. 

[citb0in]

Subtraction, multiplication, addition.....

This is like the movie Groundhog Day.
About a man reliving the same day over and over and over.
In this case trying to break the ECDSA. 

Tirelessly digaran tries again and again, OMG
ignore list updated and increased by 1

[Sg4j1n3ll0]

someone solved it ?

[alek76]

Launched it on one video card.

Code:

[i] Upload work file: Work_Kangaroos_128.txt 
[i] File Work_Kangaroos_128.txt: 255590400 bytes 1317476 lines 

[i] Get Keys time: 24549.068 msec From file: Work_Kangaroos_128.txt Size: 255590400 bytes 
[i] GPU Use Start Keys from work file: Work_Kangaroos_128.txt 

[+] Runing Comparator every: 300 sec
[i] Save Work_Kangaroos_id.txt file every: 600 sec

[i] WILD Check Distance: 8D206E8B3814706BABF1C3A693EE7A0
[i] TAME Check Distance: 3E23F093957C9DD9A3D9AB48B3482F85C
[|][  0: 0:36 ;   0.0  j/s; [GPU 0.00 Mj/s]   0.0 j   0.0%; dp/kgr=0.0;   1.0Ty  2m 22d 14: 0:32 ]  
[i] Write work Kangaroos in file: Work_Kangaroos_128.txt 
[i] Save Work file OK
[/][  0: 0:38 ;   0.0  j/s; [GPU 0.00 Mj/s]   0.0 j   0.0%; dp/kgr=0.0;   1.0Ty  2m 22d 14: 0:32 ]  
[i] Load Work file to Drive
[|][  0:11:48 ; 460.8M j/s; [GPU 460.83 Mj/s] 311.0Gj   0.0%; dp/kgr=0.0;   2.0Ky 10m 28d 19:52:16 ]  
Python Comparator time: 708831.895 msec 
[-][  0:12:40 ; 461.3M j/s; [GPU 461.26 Mj/s] 335.0Gj   0.0%; dp/kgr=0.0;   2.0Ky  6m  1d 10:52: 6 ]  
[i] WILD Check Distance: 8D206EC1A13D020EFECB550DA146C3D
[i] TAME Check Distance: 3E23F093CC220F1301640B64F086A15D5
[|][  0:13:24 ;   0.0  j/s; [GPU 0.00 Mj/s] 335.0Gj   0.0%; dp/kgr=0.0;   1.0Ty  7m 14d  3:41:52 ]  
[i] Write work Kangaroos in file: Work_Kangaroos_128.txt 
[i] Save Work file OK
[-][  0:13:28 ;   0.0  j/s; [GPU 0.00 Mj/s] 335.0Gj   0.0%; dp/kgr=0.0;   1.0Ty  7m 14d  3:41:52 ]  
[i] Load Work file to Drive
[|][  0:13:56 ; 461.1M j/s; [GPU 461.14 Mj/s] 348.0Gj   0.0%; dp/kgr=0.0;   2.0Ky  2m  0d 10:55:49 ]  
[i] Copy tame and wild files in My Drive 
[-][  0:24:16 ; 461.1M j/s; [GPU 461.09 Mj/s] 634.0Gj   0.0%; dp/kgr=0.0;   2.0Ky  5m  9d  9:27:12 ]  

And leave it like that until January 1, 2025  

[WanderingPhilospher]

Launched it on one video card.

Code:

[i] Upload work file: Work_Kangaroos_128.txt 
[i] File Work_Kangaroos_128.txt: 255590400 bytes 1317476 lines 

[i] Get Keys time: 24549.068 msec From file: Work_Kangaroos_128.txt Size: 255590400 bytes 
[i] GPU Use Start Keys from work file: Work_Kangaroos_128.txt 

[+] Runing Comparator every: 300 sec
[i] Save Work_Kangaroos_id.txt file every: 600 sec

[i] WILD Check Distance: 8D206E8B3814706BABF1C3A693EE7A0
[i] TAME Check Distance: 3E23F093957C9DD9A3D9AB48B3482F85C
[|][  0: 0:36 ;   0.0  j/s; [GPU 0.00 Mj/s]   0.0 j   0.0%; dp/kgr=0.0;   1.0Ty  2m 22d 14: 0:32 ]  
[i] Write work Kangaroos in file: Work_Kangaroos_128.txt 
[i] Save Work file OK
[/][  0: 0:38 ;   0.0  j/s; [GPU 0.00 Mj/s]   0.0 j   0.0%; dp/kgr=0.0;   1.0Ty  2m 22d 14: 0:32 ]  
[i] Load Work file to Drive
[|][  0:11:48 ; 460.8M j/s; [GPU 460.83 Mj/s] 311.0Gj   0.0%; dp/kgr=0.0;   2.0Ky 10m 28d 19:52:16 ]  
Python Comparator time: 708831.895 msec 
[-][  0:12:40 ; 461.3M j/s; [GPU 461.26 Mj/s] 335.0Gj   0.0%; dp/kgr=0.0;   2.0Ky  6m  1d 10:52: 6 ]  
[i] WILD Check Distance: 8D206EC1A13D020EFECB550DA146C3D
[i] TAME Check Distance: 3E23F093CC220F1301640B64F086A15D5
[|][  0:13:24 ;   0.0  j/s; [GPU 0.00 Mj/s] 335.0Gj   0.0%; dp/kgr=0.0;   1.0Ty  7m 14d  3:41:52 ]  
[i] Write work Kangaroos in file: Work_Kangaroos_128.txt 
[i] Save Work file OK
[-][  0:13:28 ;   0.0  j/s; [GPU 0.00 Mj/s] 335.0Gj   0.0%; dp/kgr=0.0;   1.0Ty  7m 14d  3:41:52 ]  
[i] Load Work file to Drive
[|][  0:13:56 ; 461.1M j/s; [GPU 461.14 Mj/s] 348.0Gj   0.0%; dp/kgr=0.0;   2.0Ky  2m  0d 10:55:49 ]  
[i] Copy tame and wild files in My Drive 
[-][  0:24:16 ; 461.1M j/s; [GPU 461.09 Mj/s] 634.0Gj   0.0%; dp/kgr=0.0;   2.0Ky  5m  9d  9:27:12 ]  

And leave it like that until January 1, 2025  

What happened to your vansearch kangaroo on github? You take it down?

[alek76]

What happened to your vansearch kangaroo on github? You take it down?

For an unspecified time.
_______________________________________________________________________________ __________
This is another one that remembers the steps and saves it to a file; re-running does not generate new start keys. It extracts them from the file. Save and unload functions were once available in the repository. Kangaroos are not currently available.
No, I will not distribute this version of the program for now. It seems like a lot of work has been done. Thanks also to the farm owners who offer paid access to GPU computing resources. This is starting to annoy me

There is also a division function, installed with the -div command...
In 2020, the beginning of my Kangaroo GPU code was laid, before the start of version 1.0 from Jean Luc.
Where the functions of adding points in the GPU were used in the same way as in the VanitySearch program.
A couple of people said thank you and that’s it. It looks funny.

[nomachine]

And leave it like that until January 1, 2025  

I have ~90 Ekeys/s in BSGS/keyhunt

I've been tweaking linux for months to get every atom out of Dual CPU configuration.

#RT kernel

Code:

wget -qO - https://dl.xanmod.org/archive.key | sudo gpg --dearmor -o /usr/share/keyrings/xanmod-archive-keyring.gpg
echo 'deb [signed-by=/usr/share/keyrings/xanmod-archive-keyring.gpg] http://deb.xanmod.org releases main' | sudo tee /etc/apt/sources.list.d/xanmod-release.list
sudo apt-get -y update && sudo apt install linux-xanmod-rt-x64v3

Code:

sudo apt install -y tuned tuned-utils tuned-utils-systemtap
sudo tuned-adm profile latency-performance

Code:

cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor

should be performance for all cores

/etc/default/grub

Code:

quiet msr.allow_writes=on nosoftlockup mce=ignore_ce skew_tick=1 clocksource=hpet iommu=soft noresume mitigations=off nmi_watchdog=0

Nvme config (It must be a good Heatsink on Nvme, otherwise it goes over 50 C/I have had white smoke from them more than once.)
/etc/fstab

Code:

ext4 noatime,nodiratime,errors=remount-ro,inode_readahead_blks=0 0 1

AMD EPYC config

Code:

wrmsr -a 0xc0011020 0x4400000000000
wrmsr -a 0xc0011021 0x4000000000040
wrmsr -a 0xc0011022 0x8680000401570000
wrmsr -a 0xc001102b 0x2040cc10

And so on and on....This is only part of it.

I even modify BIOS on Intel boards and even GPU bios.  Until the components burn *from efficiency.

[alek76]

And so on and on....This is only part of it.

I even modify BIOS on Intel boards and even GPU bios.  Until the components burn *from efficiency.

Wow... Approaching your goal step by step. This is great !

[FlleOWA]

And leave it like that until January 1, 2025  

I have ~90 Ekeys/s in BSGS/keyhunt

I have less. Only 5 Ekeys/s, which is very little.
He should be taught not to slow down if there are a lot of keys.
By the way, I modified the divider from Alberto ecctools.
I made a subtractor out of it, and it saves everything into a text file. It can also take keys line by line from a file and take them away in order and write them either to a given file, or it creates a file with the name of who it subtractor it from and writes the keys.

[nomachine]

I have less. Only 5 Ekeys/s, which is very little.

And that's enough to solve 65 in two seconds.


I'm scratching my head to find a way to make baby steps for the H160. There seems to be no way.

[mabdlmonem]

I have less. Only 5 Ekeys/s, which is very little.

And that's enough to solve 65 in two seconds.


I'm scratching my head to find a way to make baby steps for the H160. There seems to be no way.

There is only one way pub to rmd

[nomachine]

I have less. Only 5 Ekeys/s, which is very little.

And that's enough to solve 65 in two seconds.


I'm scratching my head to find a way to make baby steps for the H160. There seems to be no way.

There is only one way pub to rmd

And make binary database full with H160. I don't know how long that process would take. I haven't tried it yet.

[mabdlmonem]

I have less. Only 5 Ekeys/s, which is very little.

And that's enough to solve 65 in two seconds.


I'm scratching my head to find a way to make baby steps for the H160. There seems to be no way.

There is only one way pub to rmd

And make binary database full with H160. I don't know how long that process would take. I haven't tried it yet.

Serialized point and get hash160 for it on the fly

[nomachine]

I have less. Only 5 Ekeys/s, which is very little.

And that's enough to solve 65 in two seconds.


I'm scratching my head to find a way to make baby steps for the H160. There seems to be no way.

There is only one way pub to rmd

And make binary database full with H160. I don't know how long that process would take. I haven't tried it yet.

Serialized point and get hash160 for it on the fly

I moved this to another topic
https://bitcointalk.org/index.php?topic=5477342.msg63451195#msg63451195

[FlleOWA]

I uploaded the subtraction program to GitHub. If anyone needs it, you can use it, there is a compiled version for Windows.
https://github.com/Flleowa/ecctools-Subtraction

[mabdlmonem]

I uploaded the subtraction program to GitHub. If anyone needs it, you can use it, there is a compiled version for Windows.
https://github.com/Flleowa/ecctools-Subtraction

What is 68719476736 , why this number and how you calculated it?

[FlleOWA]

I uploaded the subtraction program to GitHub. If anyone needs it, you can use it, there is a compiled version for Windows.
https://github.com/Flleowa/ecctools-Subtraction

What is 68719476736 , why this number and how you calculated it?

This is Hex 1000000000 in decimal

[vneos]

HI everyone, maybe someone here can explain to me how public key subtraction works? Thanks.

[nomachine]

HI everyone, maybe someone here can explain to me how public key subtraction works? Thanks.

Or even better.... a simplified NSA accelerated study on how to solve any puzzle with key-subtraction.

[albert0bsd]

I have developed a new method!
I have studied it 100% and it works.
My calculations tell me that before the end of January 2024 I will have unlocked puzzle #130 (if someone else doesn't solve it before).
For registration, I will send it to this address BTC bc1qxs47ttydl8tmdv8vtygp7dy76lvayz3r6rdahu

This message will not have edits for its validity.

If you want to question it, do it on February 1, 2024 if I don't send it to that address.

happy new year in advance, see you in February!, if life allows me.

blessings for all.

Quoting this just for archive right now puzzle 130 is 610K USD not bad lets to see how much is on Feb 1st.