Bitcoin Forum

Bitcoin => Development & Technical Discussion => Topic started by: krashfire on September 13, 2024, 06:19:56 PM



Title: LLL & Babai's Nearest Plane Algorithm to find Private key
Post by: krashfire on September 13, 2024, 06:19:56 PM
I was testing on 2 signatures. both created with different K nonce.

as we all know, it will not lead to the correct private key unless the same nonce is reuse. However, i extended the code to include Babai's Nearest plane algorithm to readjust the wrong private key and get it closer to the correct private key by "guiding it " to the correct pubkey coordinates and it manage to only give me the partial private key from the closest vector.

I think this is interesting and will be exploring further to recover full private key.

result from my test.

Code:

root@MSI:/home/krash/test# python3 test.py
INFO:__main__:Using 2 signatures to build the lattice...
INFO:__main__:Short vectors after LLL reduction:
INFO:__main__:Short vector: (166728803922956164814674931204777127007, 0, -269917836034390020152096309044001076683, 0)
INFO:__main__:Short vector: (284880382552528911560114733869411675383, 0, 233299777452147397360970206987837337582, 0)
INFO:__main__:Short vector: (0, 115792089237316195423570985008687907853269984665640564039457584007908834671663, 0, 0)
INFO:__main__:Short vector: (191322878670180847261800180723017804593, 0, -63475476205101254537288001668546129622, 115792089237316195423570985008687907853269984665640564039457584007913129639936)
INFO:__main__:Completed LLL reduction.
INFO:__main__:partial private key from Babai: 000000000000000000000000000000007d6eccb306788626b5f389b33f092c5f



At this point, the experiment is not completed and i only consider something viable if we can recover the full private key. if anyone interested to work with me on how we can refine this experiment further, do DM me.


Title: Re: LLL & Babai's Nearest Plane Algorithm to find Private key
Post by: cassondracoffee on September 14, 2024, 04:50:47 AM
I was testing on 2 signatures. both created with different K nonce.

as we all know, it will not lead to the correct private key unless the same nonce is reuse. However, i extended the code to include Babai's Nearest plane algorithm to readjust the wrong private key and get it closer to the correct private key by "guiding it " to the correct pubkey coordinates and it manage to only give me the partial private key from the closest vector.

I think this is interesting and will be exploring further to recover full private key.

result from my test.

Code:

root@MSI:/home/krash/test# python3 test.py
INFO:__main__:Using 2 signatures to build the lattice...
INFO:__main__:Short vectors after LLL reduction:
INFO:__main__:Short vector: (166728803922956164814674931204777127007, 0, -269917836034390020152096309044001076683, 0)
INFO:__main__:Short vector: (284880382552528911560114733869411675383, 0, 233299777452147397360970206987837337582, 0)
INFO:__main__:Short vector: (0, 115792089237316195423570985008687907853269984665640564039457584007908834671663, 0, 0)
INFO:__main__:Short vector: (191322878670180847261800180723017804593, 0, -63475476205101254537288001668546129622, 115792089237316195423570985008687907853269984665640564039457584007913129639936)
INFO:__main__:Completed LLL reduction.
INFO:__main__:partial private key from Babai: 000000000000000000000000000000007d6eccb306788626b5f389b33f092c5f



At this point, the experiment is not completed and i only consider something viable if we can recover the full private key. if anyone interested to work with me on how we can refine this experiment further, do DM me.
hi,
i send your dm reply me
thankyou


Title: Re: LLL & Babai's Nearest Plane Algorithm to find Private key
Post by: COBRAS on September 14, 2024, 04:52:59 AM
I was testing on 2 signatures. both created with different K nonce.

as we all know, it will not lead to the correct private key unless the same nonce is reuse. However, i extended the code to include Babai's Nearest plane algorithm to readjust the wrong private key and get it closer to the correct private key by "guiding it " to the correct pubkey coordinates and it manage to only give me the partial private key from the closest vector.

I think this is interesting and will be exploring further to recover full private key.

result from my test.

Code:

root@MSI:/home/krash/test# python3 test.py
INFO:__main__:Using 2 signatures to build the lattice...
INFO:__main__:Short vectors after LLL reduction:
INFO:__main__:Short vector: (166728803922956164814674931204777127007, 0, -269917836034390020152096309044001076683, 0)
INFO:__main__:Short vector: (284880382552528911560114733869411675383, 0, 233299777452147397360970206987837337582, 0)
INFO:__main__:Short vector: (0, 115792089237316195423570985008687907853269984665640564039457584007908834671663, 0, 0)
INFO:__main__:Short vector: (191322878670180847261800180723017804593, 0, -63475476205101254537288001668546129622, 115792089237316195423570985008687907853269984665640564039457584007913129639936)
INFO:__main__:Completed LLL reduction.
INFO:__main__:partial private key from Babai: 000000000000000000000000000000007d6eccb306788626b5f389b33f092c5f



At this point, the experiment is not completed and i only consider something viable if we can recover the full private key. if anyone interested to work with me on how we can refine this experiment further, do DM me.

Hi, bro

You need ask questions in crypto.stackexchangr I think.This will be more productive.


Title: Re: LLL & Babai's Nearest Plane Algorithm to find Private key
Post by: krashfire on September 14, 2024, 06:06:33 AM
I was testing on 2 signatures. both created with different K nonce.

as we all know, it will not lead to the correct private key unless the same nonce is reuse. However, i extended the code to include Babai's Nearest plane algorithm to readjust the wrong private key and get it closer to the correct private key by "guiding it " to the correct pubkey coordinates and it manage to only give me the partial private key from the closest vector.

I think this is interesting and will be exploring further to recover full private key.

result from my test.

Code:

root@MSI:/home/krash/test# python3 test.py
INFO:__main__:Using 2 signatures to build the lattice...
INFO:__main__:Short vectors after LLL reduction:
INFO:__main__:Short vector: (166728803922956164814674931204777127007, 0, -269917836034390020152096309044001076683, 0)
INFO:__main__:Short vector: (284880382552528911560114733869411675383, 0, 233299777452147397360970206987837337582, 0)
INFO:__main__:Short vector: (0, 115792089237316195423570985008687907853269984665640564039457584007908834671663, 0, 0)
INFO:__main__:Short vector: (191322878670180847261800180723017804593, 0, -63475476205101254537288001668546129622, 115792089237316195423570985008687907853269984665640564039457584007913129639936)
INFO:__main__:Completed LLL reduction.
INFO:__main__:partial private key from Babai: 000000000000000000000000000000007d6eccb306788626b5f389b33f092c5f



At this point, the experiment is not completed and i only consider something viable if we can recover the full private key. if anyone interested to work with me on how we can refine this experiment further, do DM me.
hi,
i send your dm reply me
thankyou
hi Cassandra. Yes I have received your dm.. thanks.



I was testing on 2 signatures. both created with different K nonce.

as we all know, it will not lead to the correct private key unless the same nonce is reuse. However, i extended the code to include Babai's Nearest plane algorithm to readjust the wrong private key and get it closer to the correct private key by "guiding it " to the correct pubkey coordinates and it manage to only give me the partial private key from the closest vector.

I think this is interesting and will be exploring further to recover full private key.

result from my test.

Code:

root@MSI:/home/krash/test# python3 test.py
INFO:__main__:Using 2 signatures to build the lattice...
INFO:__main__:Short vectors after LLL reduction:
INFO:__main__:Short vector: (166728803922956164814674931204777127007, 0, -269917836034390020152096309044001076683, 0)
INFO:__main__:Short vector: (284880382552528911560114733869411675383, 0, 233299777452147397360970206987837337582, 0)
INFO:__main__:Short vector: (0, 115792089237316195423570985008687907853269984665640564039457584007908834671663, 0, 0)
INFO:__main__:Short vector: (191322878670180847261800180723017804593, 0, -63475476205101254537288001668546129622, 115792089237316195423570985008687907853269984665640564039457584007913129639936)
INFO:__main__:Completed LLL reduction.
INFO:__main__:partial private key from Babai: 000000000000000000000000000000007d6eccb306788626b5f389b33f092c5f



At this point, the experiment is not completed and i only consider something viable if we can recover the full private key. if anyone interested to work with me on how we can refine this experiment further, do DM me.

Hi, bro

You need ask questions in crypto.stackexchangr I think.This will be more productive.

Hey man. How are you. Long time no talk. Yeah... I hate that place. They hate me too. It's mutual. We argued a lot there. Coz the admins was pretty rude. So I hack one of them
 This was 4 years ago. Not interested to go back there.


Title: Re: LLL & Babai's Nearest Plane Algorithm to find Private key
Post by: COBRAS on September 14, 2024, 06:34:52 AM
I was testing on 2 signatures. both created with different K nonce.

as we all know, it will not lead to the correct private key unless the same nonce is reuse. However, i extended the code to include Babai's Nearest plane algorithm to readjust the wrong private key and get it closer to the correct private key by "guiding it " to the correct pubkey coordinates and it manage to only give me the partial private key from the closest vector.

I think this is interesting and will be exploring further to recover full private key.

result from my test.

Code:

root@MSI:/home/krash/test# python3 test.py
INFO:__main__:Using 2 signatures to build the lattice...
INFO:__main__:Short vectors after LLL reduction:
INFO:__main__:Short vector: (166728803922956164814674931204777127007, 0, -269917836034390020152096309044001076683, 0)
INFO:__main__:Short vector: (284880382552528911560114733869411675383, 0, 233299777452147397360970206987837337582, 0)
INFO:__main__:Short vector: (0, 115792089237316195423570985008687907853269984665640564039457584007908834671663, 0, 0)
INFO:__main__:Short vector: (191322878670180847261800180723017804593, 0, -63475476205101254537288001668546129622, 115792089237316195423570985008687907853269984665640564039457584007913129639936)
INFO:__main__:Completed LLL reduction.
INFO:__main__:partial private key from Babai: 000000000000000000000000000000007d6eccb306788626b5f389b33f092c5f



At this point, the experiment is not completed and i only consider something viable if we can recover the full private key. if anyone interested to work with me on how we can refine this experiment further, do DM me.

Hi, bro

You need ask questions in crypto.stackexchangr I think.This will be more productive.

Hey man. How are you. Long time no talk. Yeah... I hate that place. They hate me too. It's mutual. We argued a lot there. Coz the admins was pretty rude. So I hack one of them
 This was 4 years ago. Not interested to go back there.


ok.


interesting codes:

https://github.com/google/paranoid_crypto/tree/bbee4895041981d7a70b824046608b01a4291720


Title: Re: LLL & Babai's Nearest Plane Algorithm to find Private key
Post by: AbadomRSZ on September 18, 2024, 02:18:33 PM
I was testing on 2 signatures. both created with different K nonce.

as we all know, it will not lead to the correct private key unless the same nonce is reuse. However, i extended the code to include Babai's Nearest plane algorithm to readjust the wrong private key and get it closer to the correct private key by "guiding it " to the correct pubkey coordinates and it manage to only give me the partial private key from the closest vector.

I think this is interesting and will be exploring further to recover full private key.

result from my test.

Code:

root@MSI:/home/krash/test# python3 test.py
INFO:__main__:Using 2 signatures to build the lattice...
INFO:__main__:Short vectors after LLL reduction:
INFO:__main__:Short vector: (166728803922956164814674931204777127007, 0, -269917836034390020152096309044001076683, 0)
INFO:__main__:Short vector: (284880382552528911560114733869411675383, 0, 233299777452147397360970206987837337582, 0)
INFO:__main__:Short vector: (0, 115792089237316195423570985008687907853269984665640564039457584007908834671663, 0, 0)
INFO:__main__:Short vector: (191322878670180847261800180723017804593, 0, -63475476205101254537288001668546129622, 115792089237316195423570985008687907853269984665640564039457584007913129639936)
INFO:__main__:Completed LLL reduction.
INFO:__main__:partial private key from Babai: 000000000000000000000000000000007d6eccb306788626b5f389b33f092c5f


let's work together on this script, send it to my pm


Title: Re: LLL & Babai's Nearest Plane Algorithm to find Private key
Post by: cassondracoffee on September 28, 2024, 03:30:21 AM
I was testing on 2 signatures. both created with different K nonce.

as we all know, it will not lead to the correct private key unless the same nonce is reuse. However, i extended the code to include Babai's Nearest plane algorithm to readjust the wrong private key and get it closer to the correct private key by "guiding it " to the correct pubkey coordinates and it manage to only give me the partial private key from the closest vector.

I think this is interesting and will be exploring further to recover full private key.

result from my test.

Code:

root@MSI:/home/krash/test# python3 test.py
INFO:__main__:Using 2 signatures to build the lattice...
INFO:__main__:Short vectors after LLL reduction:
INFO:__main__:Short vector: (166728803922956164814674931204777127007, 0, -269917836034390020152096309044001076683, 0)
INFO:__main__:Short vector: (284880382552528911560114733869411675383, 0, 233299777452147397360970206987837337582, 0)
INFO:__main__:Short vector: (0, 115792089237316195423570985008687907853269984665640564039457584007908834671663, 0, 0)
INFO:__main__:Short vector: (191322878670180847261800180723017804593, 0, -63475476205101254537288001668546129622, 115792089237316195423570985008687907853269984665640564039457584007913129639936)
INFO:__main__:Completed LLL reduction.
INFO:__main__:partial private key from Babai: 000000000000000000000000000000007d6eccb306788626b5f389b33f092c5f



At this point, the experiment is not completed and i only consider something viable if we can recover the full private key. if anyone interested to work with me on how we can refine this experiment further, do DM me.
hi,
i send your dm reply me
thankyou
hi Cassandra. Yes I have received your dm.. thanks.



I was testing on 2 signatures. both created with different K nonce.

as we all know, it will not lead to the correct private key unless the same nonce is reuse. However, i extended the code to include Babai's Nearest plane algorithm to readjust the wrong private key and get it closer to the correct private key by "guiding it " to the correct pubkey coordinates and it manage to only give me the partial private key from the closest vector.

I think this is interesting and will be exploring further to recover full private key.

result from my test.

Code:

root@MSI:/home/krash/test# python3 test.py
INFO:__main__:Using 2 signatures to build the lattice...
INFO:__main__:Short vectors after LLL reduction:
INFO:__main__:Short vector: (166728803922956164814674931204777127007, 0, -269917836034390020152096309044001076683, 0)
INFO:__main__:Short vector: (284880382552528911560114733869411675383, 0, 233299777452147397360970206987837337582, 0)
INFO:__main__:Short vector: (0, 115792089237316195423570985008687907853269984665640564039457584007908834671663, 0, 0)
INFO:__main__:Short vector: (191322878670180847261800180723017804593, 0, -63475476205101254537288001668546129622, 115792089237316195423570985008687907853269984665640564039457584007913129639936)
INFO:__main__:Completed LLL reduction.
INFO:__main__:partial private key from Babai: 000000000000000000000000000000007d6eccb306788626b5f389b33f092c5f



At this point, the experiment is not completed and i only consider something viable if we can recover the full private key. if anyone interested to work with me on how we can refine this experiment further, do DM me.

Hi, bro

You need ask questions in crypto.stackexchangr I think.This will be more productive.

Hey man. How are you. Long time no talk. Yeah... I hate that place. They hate me too. It's mutual. We argued a lot there. Coz the admins was pretty rude. So I hack one of them
 This was 4 years ago. Not interested to go back there.


I am waiting for 1 week. You are not replying; check DM and write your email.

#130 puzzles were solved by someone, and I think you solved.


Title: Re: LLL & Babai's Nearest Plane Algorithm to find Private key
Post by: AbadomRSZ on September 28, 2024, 04:06:28 PM
I was testing on 2 signatures. both created with different K nonce.

as we all know, it will not lead to the correct private key unless the same nonce is reuse. However, i extended the code to include Babai's Nearest plane algorithm to readjust the wrong private key and get it closer to the correct private key by "guiding it " to the correct pubkey coordinates and it manage to only give me the partial private key from the closest vector.

I think this is interesting and will be exploring further to recover full private key.

result from my test.

Code:

root@MSI:/home/krash/test# python3 test.py
INFO:__main__:Using 2 signatures to build the lattice...
INFO:__main__:Short vectors after LLL reduction:
INFO:__main__:Short vector: (166728803922956164814674931204777127007, 0, -269917836034390020152096309044001076683, 0)
INFO:__main__:Short vector: (284880382552528911560114733869411675383, 0, 233299777452147397360970206987837337582, 0)
INFO:__main__:Short vector: (0, 115792089237316195423570985008687907853269984665640564039457584007908834671663, 0, 0)
INFO:__main__:Short vector: (191322878670180847261800180723017804593, 0, -63475476205101254537288001668546129622, 115792089237316195423570985008687907853269984665640564039457584007913129639936)
INFO:__main__:Completed LLL reduction.
INFO:__main__:partial private key from Babai: 000000000000000000000000000000007d6eccb306788626b5f389b33f092c5f



At this point, the experiment is not completed and i only consider something viable if we can recover the full private key. if anyone interested to work with me on how we can refine this experiment further, do DM me.
hi,
i send your dm reply me
thankyou
hi Cassandra. Yes I have received your dm.. thanks.



I was testing on 2 signatures. both created with different K nonce.

as we all know, it will not lead to the correct private key unless the same nonce is reuse. However, i extended the code to include Babai's Nearest plane algorithm to readjust the wrong private key and get it closer to the correct private key by "guiding it " to the correct pubkey coordinates and it manage to only give me the partial private key from the closest vector.

I think this is interesting and will be exploring further to recover full private key.

result from my test.

Code:

root@MSI:/home/krash/test# python3 test.py
INFO:__main__:Using 2 signatures to build the lattice...
INFO:__main__:Short vectors after LLL reduction:
INFO:__main__:Short vector: (166728803922956164814674931204777127007, 0, -269917836034390020152096309044001076683, 0)
INFO:__main__:Short vector: (284880382552528911560114733869411675383, 0, 233299777452147397360970206987837337582, 0)
INFO:__main__:Short vector: (0, 115792089237316195423570985008687907853269984665640564039457584007908834671663, 0, 0)
INFO:__main__:Short vector: (191322878670180847261800180723017804593, 0, -63475476205101254537288001668546129622, 115792089237316195423570985008687907853269984665640564039457584007913129639936)
INFO:__main__:Completed LLL reduction.
INFO:__main__:partial private key from Babai: 000000000000000000000000000000007d6eccb306788626b5f389b33f092c5f



At this point, the experiment is not completed and i only consider something viable if we can recover the full private key. if anyone interested to work with me on how we can refine this experiment further, do DM me.

Hi, bro

You need ask questions in crypto.stackexchangr I think.This will be more productive.

Hey man. How are you. Long time no talk. Yeah... I hate that place. They hate me too. It's mutual. We argued a lot there. Coz the admins was pretty rude. So I hack one of them
 This was 4 years ago. Not interested to go back there.


I am waiting for 1 week. You are not replying; check DM and write your email.

#130 puzzles were solved by someone, and I think you solved.

 he won't get anywhere with this!