Pages:
Author

Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 37. (Read 245568 times)

?
Activity: -
Merit: -
On Nov. 1st 2024 at 0:00 AM UTC I will post here a BTC P2PKH address (compressed) associated with an 80-bits secure private key.

The address owns 0.005 BTC (~340 $)

Starting from that time, at some point during the next 24 hours an outgoing transaction, containing unspent outputs from that address, will be broadcasted on the BTC network (public mempool, not Mara).

Let's see who breaks it. I only ask one thing if that happens: what method was used to break the key.

Together with the target address I will also provide the range of the search interval.

This will be in the form (just an example):

Code:
minKey = 0xf2e542b46066c4e6f91abc80000000000000000000185e689447431d74c5b133
maxKey = 0xf2e542b46066c4e6f91abcbfffffffffffffffffffd85e689447431d74c5b133

The Hamming length of the range will therefore be 80 contiguous bits, but they may start anywhere.

If your first instinct is to yell "this is not a 80-bits secure private key", please note this competition is NOT for you, do not expect a response from me.

Get your tools ready boys.
let someone be lucky) if a transaction takes place from that address and the public key is known...The case is 5 minutes. Even with my capabilities, it will be very fast to find him. I won't participate, just watch.(OK, not 5 minutes, but 10, sorry...)))


Total range will  be 256 - 80. Too big, you not think so ?

Code:
def hex_to_bin(hex_value):
    # Convert hex to binary string, without the "0b" prefix
    return bin(int(hex_value, 16))[2:]

def hamming_length(hex1, hex2):
    # Convert both hex values to binary
    bin1 = hex_to_bin(hex1)
    bin2 = hex_to_bin(hex2)
    
    # Calculate the Hamming distance
    distance = sum(b1 != b2 for b1, b2 in zip(bin1, bin2))
    
    return distance

# Example usage
hex_value_1 = "0xf2e542b46066c4e6f91abc80000000000000000000185e689447431d74c5b133"
hex_value_2 = "0xf2e542b46066c4e6f91abcbfffffffffffffffffffd85e689447431d74c5b133"

hamming_dist = hamming_length(hex_value_1, hex_value_2)
print(f"Hamming length: {hamming_dist} bits")

80BITS!


not info there is 80 bit, in start or at and of 256.

0.........2e542b46066c4e6f91abcb0fffffffffffffffffff
fffffffffffffffffff2e542b46066c4e6f91abcb


Huh


1111001011100101010000101011010001100000011001101100010011100110111110010001101 010111100100000000000000000000000000000000000000000000000000000000000000000000000000000000 00110000101111001101000100101000100011101000011000111010111010011000101101100010 0110011

1111001011100101010000101011010001100000011001101100010011100110111110010001101 010111100101111111111111111111111111111111111111111111111111111111111111111111111111111111 10110000101111001101000100101000100011101000011000111010111010011000101101100010 0110011

EDIT- They said
Together with the target address I will also provide the range of the search interval.
if they didn't provide the range along with the address then it would be 256, but since it is a puzzle they are providing us with the range. Please correct me if I am wrong kTimesG
member
Activity: 873
Merit: 22
$$P2P BTC BRUTE.JOIN NOW ! https://uclck.me/SQPJk
On Nov. 1st 2024 at 0:00 AM UTC I will post here a BTC P2PKH address (compressed) associated with an 80-bits secure private key.

The address owns 0.005 BTC (~340 $)

Starting from that time, at some point during the next 24 hours an outgoing transaction, containing unspent outputs from that address, will be broadcasted on the BTC network (public mempool, not Mara).

Let's see who breaks it. I only ask one thing if that happens: what method was used to break the key.

Together with the target address I will also provide the range of the search interval.

This will be in the form (just an example):

Code:
minKey = 0xf2e542b46066c4e6f91abc80000000000000000000185e689447431d74c5b133
maxKey = 0xf2e542b46066c4e6f91abcbfffffffffffffffffffd85e689447431d74c5b133

The Hamming length of the range will therefore be 80 contiguous bits, but they may start anywhere.

If your first instinct is to yell "this is not a 80-bits secure private key", please note this competition is NOT for you, do not expect a response from me.

Get your tools ready boys.
let someone be lucky) if a transaction takes place from that address and the public key is known...The case is 5 minutes. Even with my capabilities, it will be very fast to find him. I won't participate, just watch.(OK, not 5 minutes, but 10, sorry...)))


Total range will  be 256 - 80. Too big, you not think so ?

Code:
def hex_to_bin(hex_value):
    # Convert hex to binary string, without the "0b" prefix
    return bin(int(hex_value, 16))[2:]

def hamming_length(hex1, hex2):
    # Convert both hex values to binary
    bin1 = hex_to_bin(hex1)
    bin2 = hex_to_bin(hex2)
   
    # Calculate the Hamming distance
    distance = sum(b1 != b2 for b1, b2 in zip(bin1, bin2))
   
    return distance

# Example usage
hex_value_1 = "0xf2e542b46066c4e6f91abc80000000000000000000185e689447431d74c5b133"
hex_value_2 = "0xf2e542b46066c4e6f91abcbfffffffffffffffffffd85e689447431d74c5b133"

hamming_dist = hamming_length(hex_value_1, hex_value_2)
print(f"Hamming length: {hamming_dist} bits")

80BITS!


not info there is 80 bit, in start or at and of 256.

0.........2e542b46066c4e6f91abcb0fffffffffffffffffff
fffffffffffffffffff2e542b46066c4e6f91abcb


Huh
?
Activity: -
Merit: -
On Nov. 1st 2024 at 0:00 AM UTC I will post here a BTC P2PKH address (compressed) associated with an 80-bits secure private key.

The address owns 0.005 BTC (~340 $)

Starting from that time, at some point during the next 24 hours an outgoing transaction, containing unspent outputs from that address, will be broadcasted on the BTC network (public mempool, not Mara).

Let's see who breaks it. I only ask one thing if that happens: what method was used to break the key.

Together with the target address I will also provide the range of the search interval.

This will be in the form (just an example):

Code:
minKey = 0xf2e542b46066c4e6f91abc80000000000000000000185e689447431d74c5b133
maxKey = 0xf2e542b46066c4e6f91abcbfffffffffffffffffffd85e689447431d74c5b133

The Hamming length of the range will therefore be 80 contiguous bits, but they may start anywhere.

If your first instinct is to yell "this is not a 80-bits secure private key", please note this competition is NOT for you, do not expect a response from me.

Get your tools ready boys.
let someone be lucky) if a transaction takes place from that address and the public key is known...The case is 5 minutes. Even with my capabilities, it will be very fast to find him. I won't participate, just watch.(OK, not 5 minutes, but 10, sorry...)))


Total range will  be 256 - 80. Too big, you not think so ?

Code:
def hex_to_bin(hex_value):
    # Convert hex to binary string, without the "0b" prefix
    return bin(int(hex_value, 16))[2:]

def hamming_length(hex1, hex2):
    # Convert both hex values to binary
    bin1 = hex_to_bin(hex1)
    bin2 = hex_to_bin(hex2)
   
    # Calculate the Hamming distance
    distance = sum(b1 != b2 for b1, b2 in zip(bin1, bin2))
   
    return distance

# Example usage
hex_value_1 = "0xf2e542b46066c4e6f91abc80000000000000000000185e689447431d74c5b133"
hex_value_2 = "0xf2e542b46066c4e6f91abcbfffffffffffffffffffd85e689447431d74c5b133"

hamming_dist = hamming_length(hex_value_1, hex_value_2)
print(f"Hamming length: {hamming_dist} bits")

80BITS!
member
Activity: 873
Merit: 22
$$P2P BTC BRUTE.JOIN NOW ! https://uclck.me/SQPJk
On Nov. 1st 2024 at 0:00 AM UTC I will post here a BTC P2PKH address (compressed) associated with an 80-bits secure private key.

The address owns 0.005 BTC (~340 $)

Starting from that time, at some point during the next 24 hours an outgoing transaction, containing unspent outputs from that address, will be broadcasted on the BTC network (public mempool, not Mara).

Let's see who breaks it. I only ask one thing if that happens: what method was used to break the key.

Together with the target address I will also provide the range of the search interval.

This will be in the form (just an example):

Code:
minKey = 0xf2e542b46066c4e6f91abc80000000000000000000185e689447431d74c5b133
maxKey = 0xf2e542b46066c4e6f91abcbfffffffffffffffffffd85e689447431d74c5b133

The Hamming length of the range will therefore be 80 contiguous bits, but they may start anywhere.

If your first instinct is to yell "this is not a 80-bits secure private key", please note this competition is NOT for you, do not expect a response from me.

Get your tools ready boys.
let someone be lucky) if a transaction takes place from that address and the public key is known...The case is 5 minutes. Even with my capabilities, it will be very fast to find him. I won't participate, just watch.(OK, not 5 minutes, but 10, sorry...)))


Total range will  be 256 - 80. Too big, you not think so ?
?
Activity: -
Merit: -
On Nov. 1st 2024 at 0:00 AM UTC I will post here a BTC P2PKH address (compressed) associated with an 80-bits secure private key.

The address owns 0.005 BTC (~340 $)

Starting from that time, at some point during the next 24 hours an outgoing transaction, containing unspent outputs from that address, will be broadcasted on the BTC network (public mempool, not Mara).

Let's see who breaks it. I only ask one thing if that happens: what method was used to break the key.

Together with the target address I will also provide the range of the search interval.

This will be in the form (just an example):

Code:
minKey = 0xf2e542b46066c4e6f91abc80000000000000000000185e689447431d74c5b133
maxKey = 0xf2e542b46066c4e6f91abcbfffffffffffffffffffd85e689447431d74c5b133

The Hamming length of the range will therefore be 80 contiguous bits, but they may start anywhere.

If your first instinct is to yell "this is not a 80-bits secure private key", please note this competition is NOT for you, do not expect a response from me.

Get your tools ready boys.
Shocked Cool

Welp. Was just getting into more of the technical side of things with my understanding of Pollards Kangaroo and starting out with python. Can do #40 in 27 minutes, #45 in 48 minutes with cpu (yes I know this won't scale as some would think just seeing those two timeframes). Not great speed, will be making it in a few languages. Will release a repo soon for others that have not gotten into Pollards Kangaroo yet. Currently multi threaded and yes I am pre computing the G*Step partitions and mapping it. And for release of "research" code, should I keep "constants" at their basic levels for just exploring with <#20. Think I have the README detailed enough for those who want to understand to be able to dive into it and further into the papers.

While I respect you for just slapping the people with a large trout who haven't read the creators post about how it was generated and then posting all these "This is how the creator generated it" or those coming up with clearly "lower bound roos" ideas. It's funny yet sad at the same time. No where near the intellect of yourself or others here but it must be frustrating. And yes, please slap me with a large trout if I say something wrong!

Good luck to those who have the right tools at the ready!
newbie
Activity: 23
Merit: 0
On Nov. 1st 2024 at 0:00 AM UTC I will post here a BTC P2PKH address (compressed) associated with an 80-bits secure private key.

The address owns 0.005 BTC (~340 $)

Starting from that time, at some point during the next 24 hours an outgoing transaction, containing unspent outputs from that address, will be broadcasted on the BTC network (public mempool, not Mara).

Let's see who breaks it. I only ask one thing if that happens: what method was used to break the key.

Together with the target address I will also provide the range of the search interval.

This will be in the form (just an example):

Code:
minKey = 0xf2e542b46066c4e6f91abc80000000000000000000185e689447431d74c5b133
maxKey = 0xf2e542b46066c4e6f91abcbfffffffffffffffffffd85e689447431d74c5b133

The Hamming length of the range will therefore be 80 contiguous bits, but they may start anywhere.

If your first instinct is to yell "this is not a 80-bits secure private key", please note this competition is NOT for you, do not expect a response from me.

Get your tools ready boys.
let someone be lucky) if a transaction takes place from that address and the public key is known...The case is 5 minutes. Even with my capabilities, it will be very fast to find him. I won't participate, just watch.(OK, not 5 minutes, but 10, sorry...)))
member
Activity: 165
Merit: 26
On Nov. 1st 2024 at 0:00 AM UTC I will post here a BTC P2PKH address (compressed) associated with an 80-bits secure private key.

The address owns 0.005 BTC (~340 $)

Starting from that time, at some point during the next 24 hours an outgoing transaction, containing unspent outputs from that address, will be broadcasted on the BTC network (public mempool, not Mara).

Let's see who breaks it. I only ask one thing if that happens: what method was used to break the key.

Together with the target address I will also provide the range of the search interval.

This will be in the form (just an example):

Code:
minKey = 0xf2e542b46066c4e6f91abc80000000000000000000185e689447431d74c5b133
maxKey = 0xf2e542b46066c4e6f91abcbfffffffffffffffffffd85e689447431d74c5b133

The Hamming length of the range will therefore be 80 contiguous bits, but they may start anywhere.

If your first instinct is to yell "this is not a 80-bits secure private key", please note this competition is NOT for you, do not expect a response from me.

Get your tools ready boys.
?
Activity: -
Merit: -
I see some people here believe that high-number puzzles >100 can be solved by BSGS or
by some other method other than kangaroos. I could prove that kang is the only known way,
but when people want to believe to something - it's almost impossible to stop them.
Better save your time and don't argue, let them talk about solving #135 with BSGS, with splitting ranges, with magic scripts and circles, it's funny  Grin

Indulged me.
Your final edited comment in the mini 120 puzzle.
What would of impressed you of how i did it ?

I also owe you a drink lol
?
Activity: -
Merit: -
you only need a db with approximately 100m keys to reduce the 130 puzzle to 100 bits.
195325 output I can make for 130 to 100
member
Activity: 165
Merit: 26
Please send help.

You can find some water at 0x1b7b24bfec17f17cfad4ed5d26f3ba3f2ecde9516100d16dbfa3986c27223893 to your right and a map behind 0xe484db4013e80e83052b1267603def814791291a8a098469934ed0bc5f7e2739 to your left.

Also, don't be so negative, you're just one hop away to be half-way out!
member
Activity: 63
Merit: 14
I'm working around the clock to fit 2^160 magic circles into mcdouglasx brain fart db so I can astral project myself in front of it at 3am during a full moon, while Rotor-Cuda runs on the background searching for 1 trillion divided public keys in a smaller range. This is it guys, wish me luck.

Update: Was chased down by some NSA wraith wielding a huge scimitar, am now lost beyond the coordinates 00000000000000000000003b78ce563f89a0ed9414f5aa28ad0d96d6795f9c63, 3f3979bf72ae8202983dc989aec7f2ff2ed91bdd69ce02fc0700ca100e59ddf3. Please send help.

Oh, look! Digirombs is here too, hey dude
member
Activity: 165
Merit: 26
I see some peoples here believe that high-number puzzles >100 can be solved by BSGS or
by some other method other than kangaroos. I could prove that kang is the only known way,
but when people want to believe to something - it's almost impossible to stop them.
Better save your time and don't argue, let them talk about solving #135 with BSGS, with splitting ranges, with magic scripts and circles, it's funny  Grin

The only problem is that other people may end up falling for what can best be described as fantasy-land stories about breaking the bounds of classical understanding of what information is made out of. And calling those living in the actual reality as religious fanatics... I didn't invent Kangaroo, to have any reason to defend it, but that doesn't mean it shouldn't be acknowledged as the only viable way to go forward, in lack of anything else. I know Darwin's law will take care of things for me though.
?
Activity: -
Merit: -
I see some people here believe that high-number puzzles >100 can be solved by BSGS or
by some other method other than kangaroos. I could prove that kang is the only known way,
but when people want to believe to something - it's almost impossible to stop them.
Better save your time and don't argue, let them talk about solving #135 with BSGS, with splitting ranges, with magic scripts and circles, it's funny  Grin
newbie
Activity: 30
Merit: 0
Where are all the people who said the creator of the puzzles solved 120, 125 and 130 ?
Where are they ?

Just because you have no programming knowledge and you are waiting for JLP, AlbertoBSD, WanderingPhilosopher, Nomachine, Alek76 and Brichard to produce something so you use it for free and solve the puzzles doesn't mean everyone else is doing the same.

Think about it, if one of these people I named, produces something that gives the user an edge to solve the puzzles easily, do you think he will release it to the public ? He would use it himself privately, the puzzles are worth a lot.
I have another theory for you:
The reason the creator removed these puzzles could be that, when JLP officially made the Kangaroo source code public, they realized this method was highly cost-efficient for solving the puzzles. Since the source code is publicly available, anyone with multiple GPUs could crack them within a few years, or even by luck, making it much more cost-effective compared to the prize and difficulty of the puzzle.



If he can provide the private keys to Puzzle 125&130. I definitely will accept all my theories were wrong.
newbie
Activity: 8
Merit: 0
Where are all the people who said the creator of the puzzles solved 120, 125 and 130 ?
Where are they ?

Just because you have no programming knowledge and you are waiting for JLP, AlbertoBSD, WanderingPhilosopher, Nomachine, Alek76 and Brichard to produce something so you use it for free and solve the puzzles doesn't mean everyone else is doing the same.

Think about it, if one of these people I named, produces something that gives the user an edge to solve the puzzles easily, do you think he will release it to the public ? He would use it himself privately, the puzzles are worth a lot.
member
Activity: 503
Merit: 38
ASIC versions of kangaroo

asics kangaroo soccer shoes  Grin


Don't tell me you Googled the term 'ASICs Kangaroo'?  Cheesy  Cheesy  Cheesy
jr. member
Activity: 42
Merit: 0
ASIC versions of kangaroo





asics kangaroo soccer shoes  Grin
newbie
Activity: 15
Merit: 0
All I wanna know is whether it was a manner of hopping or a manner of giant babies. Nothing more.

Of course it was a lot of crazy fast kangaroos  Cheesy
My kangaroos, not JLP's.

How long you run your kangaroo script until get the key p120? how many GPU you used? or your Kang run for CPU mode. I read your previous comment I guess you create your secret weapon from improvement the JLP's Kangaroo am I right?
?
Activity: -
Merit: -
All I wanna know is whether it was a manner of hopping or a manner of giant babies. Nothing more.

Of course it was a lot of crazy fast kangaroos  Cheesy
My kangaroos, not JLP's.

Yes congrats and thank you for the mini puzzle and being generous.
so you are 3Emiwz ? Maybe more mini puzzle lol ?
member
Activity: 63
Merit: 14
Of course it was a lot of crazy fast kangaroos  Cheesy
My kangaroos, not JLP's.

If I might ask, GPU based or is it something else?

Congratulations by the way, we are pleased to finally meet you.
Pages:
Jump to: