albert0bsd
|
 |
January 03, 2024, 02:09:43 PM |
|
Hey Guys i have a question.. well lets say we subtract a target public key puzzle (130) using key subtractor with 1000000000000000000000000000 continuously at some point it movies from the additive inverse to the negative inverse right? are there any ways we could possible know at what point the reset point happened ?
No there is no way to know that, that break ECDSA, any method to get single bit leak information of the privatekey break the ECDSA.
|
|
|
|
FlleOWA
Newbie
Offline
Activity: 13
Merit: 0
|
 |
January 03, 2024, 04:19:07 PM |
|
Hey Guys i have a question.. well lets say we subtract a target public key puzzle (130) using key subtractor with 1000000000000000000000000000 continuously at some point it movies from the additive inverse to the negative inverse right? are there any ways we could possible know at what point the reset point happened ?
You can reduce each range 16 times, and then reduce all the results obtained by 16. And so you can go all the way to 0. But the lower you decrease, the more your number of public keys will grow. But 100% them will have 1 working key. There is another option, a little simpler. Make the G point the 130 range key. Then generate new keys in the 130 range. And then simply subtract 1 from all these keys. If successful, you will get a key in the lower range, and then it’s a matter of little things.
|
|
|
|
FlleOWA
Newbie
Offline
Activity: 13
Merit: 0
|
 |
January 04, 2024, 11:46:37 AM |
|
Here are the numbers I found out of boredom. This is the minimum number 16492674416640 And this is the Maximum 115792089237316195423570985008687907853269984665640564039457584006813618012160 With these numbers, nothing is possible on the curve. Subtraction, multiplication, addition does not work with them. Perhaps they are simply 0 on the curve. If you change the number at the end to +, you get one.
The curve does not accept these numbers at all. 789842187514178900234385207627528242391713215504118334407332331520 394921093757089450117192603813764121195856607752059167203666165760 197460546878544725058596301906882060597928303876029583601833082880 I couldn’t find this information about these numbers at all on the forum. Maybe someone will find this information useful. I have already done everything that came into my head with these numbers.
|
|
|
|
nomachine
Member

Offline
Activity: 507
Merit: 38
|
 |
January 04, 2024, 12:49:03 PM |
|
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. 
|
bc1qdwnxr7s08xwelpjy3cc52rrxg63xsmagv50fa8
|
|
|
citb0in
|
 |
January 04, 2024, 01:51:27 PM |
|
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
|
_ _ _ __ _ _ _ __ |_) | / \ / |/ (_ / \ | \ / |_ |_) (_ |_) |_ \_/ \_ |\ __) \_/ |_ \/ |_ | \ __) --> citb0in Solo-Mining Group <--- low stake of only 0.001 BTC. We regularly rent about 5 PH/s hash power and direct it to SoloCK pool. Wanna know more? Read through the link and JOIN NOW
|
|
|
Sg4j1n3ll0
|
 |
January 05, 2024, 09:01:15 AM |
|
someone solved it ?
|
|
|
|
alek76
Member

Offline
Activity: 93
Merit: 16
|
 |
January 05, 2024, 07:49:32 PM |
|
Launched it on one video card. [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
Sr. Member
  
Offline
Activity: 1288
Merit: 253
Shooters Shoot...
|
 |
January 05, 2024, 10:42:31 PM |
|
Launched it on one video card. [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
Member

Offline
Activity: 93
Merit: 16
|
 |
January 06, 2024, 04:16:53 AM Last edit: January 06, 2024, 05:19:06 AM by 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
Member

Offline
Activity: 507
Merit: 38
|
 |
January 06, 2024, 05:49:28 AM Last edit: January 06, 2024, 06:41:59 AM by 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 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 sudo apt install -y tuned tuned-utils tuned-utils-systemtap sudo tuned-adm profile latency-performance cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor should be performance for all cores /etc/default/grub 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 ext4 noatime,nodiratime,errors=remount-ro,inode_readahead_blks=0 0 1 AMD EPYC config 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. 
|
bc1qdwnxr7s08xwelpjy3cc52rrxg63xsmagv50fa8
|
|
|
alek76
Member

Offline
Activity: 93
Merit: 16
|
 |
January 06, 2024, 06:59:05 AM |
|
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
Newbie
Offline
Activity: 13
Merit: 0
|
 |
January 06, 2024, 08:20:22 AM |
|
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
Member

Offline
Activity: 507
Merit: 38
|
 |
January 06, 2024, 10:46:06 AM |
|
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. 
|
bc1qdwnxr7s08xwelpjy3cc52rrxg63xsmagv50fa8
|
|
|
mabdlmonem
Jr. Member
Offline
Activity: 37
Merit: 1
|
 |
January 06, 2024, 11:01:54 AM |
|
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
Member

Offline
Activity: 507
Merit: 38
|
 |
January 06, 2024, 11:26:46 AM |
|
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. 
|
bc1qdwnxr7s08xwelpjy3cc52rrxg63xsmagv50fa8
|
|
|
mabdlmonem
Jr. Member
Offline
Activity: 37
Merit: 1
|
 |
January 06, 2024, 11:31:03 AM |
|
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
Member

Offline
Activity: 507
Merit: 38
|
 |
January 06, 2024, 12:11:06 PM |
|
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
|
bc1qdwnxr7s08xwelpjy3cc52rrxg63xsmagv50fa8
|
|
|
|
mabdlmonem
Jr. Member
Offline
Activity: 37
Merit: 1
|
 |
January 06, 2024, 09:23:24 PM |
|
What is 68719476736 , why this number and how you calculated it?
|
|
|
|
FlleOWA
Newbie
Offline
Activity: 13
Merit: 0
|
 |
January 07, 2024, 07:53:18 AM |
|
What is 68719476736 , why this number and how you calculated it? This is Hex 1000000000 in decimal
|
|
|
|
|