Pages:
Author

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

newbie
Activity: 25
Merit: 3
Not here trying to toot my own horn...

I'm the one that first found 1BY8GQbnueYebq5d6CE1wDfbdAWWy33ZyW, sent it some change, and then sent that change to 67. If someone here is the one that gets 67 and you used the starting point I found and shared with you all, be cool and throw a coin my way, will ya?

txid that first funded 1BY8GQbnueYebq5d6CE1wDfbdAWWy33ZyW: https://mempool.space/tx/cff866f5a1eb771a5886535e4722a9361faf7a912791671a191f825228597a6a

Address: 1CgcibFXFiT2SuY4XiDvGZbUA8wJJagjb3
Message: I found 1BY8GQbnueYebq5d6CE1wDfbdAWWy33ZyW.
Signature: H4sY61XNuImEueQnrhKNxkaeLG3EUHdUq0QdNpwwU9UWfnwBL8QqikbdX0zz2zG696pBOvTvIjIkYtY BFi2cVNI=

Amongst the chatter in various Russian speaking Telegram groups, it looks like several 1BY8GQbnueY prefixes have possibly been found, but I haven't been able to verify any of them. Could be real, or not, but my hunch is that they're fake/disinfo. But I'm no longer monitoring those channels for updates, nor searching for 67, I've dropped out of the race... Thanks everyone and good luck out there.

newbie
Activity: 8
Merit: 0

If money interested, I think most profit is a join to private btc mining pool.

I sent you a message.
member
Activity: 873
Merit: 22
$$P2P BTC BRUTE.JOIN NOW ! https://uclck.me/SQPJk
Hey guys, am new in bitcoin  and i discovered this puzzle about a month ago. Why are you guys brute forcing big numbers just wasting time, for me it just took me a month and now i already cracked 140, 145 150 155 and 160 by using maths, so you say no one  have discoverd the math behind bitcoin public keys?

Try, all math especially move from biger range  to smaller with more many pubkeys etc. No profit math in bitcoin bruteforce. Kangaroo description provide RogueCodee , JLP not say how select DP, without knowing how select DP right, you only spend time nothing also. If money interested, I think most profit is a join to private btc mining pool.
hero member
Activity: 714
Merit: 1010
Crypto Swap Exchange
~~~
Very nice of you that you leave #135 for us puny plebs. Interesting though, none of the coins from #140, #145, #150, #155 and #160 have moved so far or am I only blinded by the overwhelming excellence of your pure math mind? Impressive... your achievement within only one month, show proof... I'm confused...

As albert0bsd said, sign messages or STFU!
hero member
Activity: 862
Merit: 662
Hey guys, am new in bitcoin  and i discovered this puzzle about a month ago. Why are you guys brute forcing big numbers just wasting time, for me it just took me a month and now i already cracked 140, 145 150 155 and 160 by using maths, so you say no one  have discoverd the math behind bitcoin public keys?

It is easy to prove that you have the keys just by publishing a Signed text message that anyone can validate. So if you said that you solve these and you want that the users here believe you then you just need to publish such signatures.

Just like RetiredCoder did:

Address: 1PXAyUB8ZoH3WD8n5zoAthYjN15yN5CVq5
Message: RetiredCoder is a winner for 120,125,130
Signature: ILsD3ydVDKulUbTykvnPl8RNwPeBKqw58rv+ftq0HRxbWyzIbgl29Wup6uTahQ7xkKUG/LAUJLF8xcBxc2FDUU8=

Address: 1Fo65aKq8s8iquMt6weF1rku1moWVEd5Ua
Message: RetiredCoder is a winner for 120,125,130
Signature: IN6XCSv7fAIUioJ7T4ti2x4YmnOcd4FXmd9eb7Na6IofP0+ji8uxdhVEb6vG++vO77t9BS7KnOE2s6Sme38NT0I=


A lot of people here knows the math behind the ECDSA and right know the 2 best algorithms that we have to solve this have a complexity of Square root of N aka (meet me in the middle) [1]

- Baby step giant step
- Kangaroo (This one is the best because it don't have the memory limitation)



[1] https://andrea.corbellini.name/2015/06/08/elliptic-curve-cryptography-breaking-security-and-a-comparison-with-rsa/
?
Activity: -
Merit: -
Hey guys, am new in bitcoin  and i discovered this puzzle about a month ago. Why are you guys brute forcing big numbers just wasting time, for me it just took me a month and now i already cracked 140, 145 150 155 and 160 by using maths, so you say no one  have discoverd the math behind bitcoin public keys?
?
Activity: -
Merit: -
How did he help him with the transaction? I have been reading this thread for quite some time but I think I missed the part about BOTs where someone tries to steal the sats after when someone withdraws the BTC.   Is there someone who can reply to this explanation of what really is going on?  If we really find out the private key then how can we claim it safely by not getting trapped by the Bots?

It already was explained here is the post, but basically you need to trust to the Private service of Mara slipstream.

Link: https://bitcointalksearch.org/topic/m.64379149

The death of the monitoring bots for the low bit challenge/puzzles such as the 66, 67, 68 bits.
The sure fire way to get all of your hard earned 6.6 BTC into one of your safe wallets...or is it a sure fire way?
Let me know what you think.

Ok, so here is the current, thoughtout way to beat the bots when dealing with the puzzle/challenge low bit wallets.

...

The main problem for those low entropy puzzles is the FullRBF feature of some versions of the bitcoin core, if the miners set the flag to accept TX that replace other TX without the RBF Flag



Thank You all for your responses, I will look into this deeply before I start working on it.  Maybe we have to create another bot to compete with it as well, hehe

For what it's worth, Learning is Earning for me in the first place.
?
Activity: -
Merit: -
I don't think anything wrong happened here.

5.94 BTC went to

bc1ql5lrt3y97djyu5k8ewmz87nnemxheycp6wdree
bc1qdplvug87leypur2a27xh64u8cu78e0td8edwv7
bc1qpa20zkg6kr55yl7gxnwh37aj8q00rt70k6q8ru

whereas 0.66 BTC (exactly 10% of the prize 6.60 BTC) went straight to Binance (for cash out ?)

Someone helped the finder with the transaction and got 10% of the prize?


How did he help him with the transaction? I have been reading this thread for quite some time but I think I missed the part about BOTs where someone tries to steal the sats after when someone withdraws the BTC.   Is there someone who can reply to this explanation of what really is going on?  If we really find out the private key then how can we claim it safely by not getting trapped by the Bots?

I've thought about it and I think we shouldn't want to win everything. If I have to pay 5 BTC in commission to win just 1, so be it. At least if I don't win the BOT will lose more than 5 Smiley
But if the bot gets the private key in seconds, why isn't Puzzle 135, 140 etc solved? The bots belong to the owner of the puzzle..I think because it has the private keys to all puzzle Smiley

Once the public key of any puzzle up to say around 90-100 ish is out there kangaroo will solve it in minutes. It will not solve anything higher in minutes or even hours unless you're very very lucky.
People had been going at it for years for 120 and up.
The bots are run from users on this forum believe it or not.
One user on this forum in particular has the fastest bot in the world apparently i wont name them but just think about how the bots works and search this forum you will see for yourself.

Also mara is apparently the place to go to make a TX without broadcasting the public key.
There's a guide to it in this thread.
someone in this thread done a test and it worked. However that was with like $50 or so.
All the answers are in this thread.

hero member
Activity: 862
Merit: 662
Why do you write "if the miners set the flag" for their node(s) to accept Full-RBF? They would be stupid to not enable Full-RBF for them by default. Every miner has a financial incentive to have Full-RBF enabled. I can't think of a reason why any miner or mining pool won't do this.

Do you have an example of a miner who doesn't?

From what I understand (correct me if I'm wrong), the flag is disabled by default. Miners would need to manually change the config file or something to enable it. Obviously, anyone who knows what they're doing would turn on the Full-RBF feature.

That's not really the point here, though. I'm not trying to start a debate about whether miners would set the flag of course they would. It was just a way of write  it, so sorry if it sounded dumb or confusing. Maybe it's just how it came out in my head since English isn’t my first language.
hero member
Activity: 714
Merit: 1010
Crypto Swap Exchange
~~~
Why do you write "if the miners set the flag" for their node(s) to accept Full-RBF? They would be stupid to not enable Full-RBF for them by default. Every miner has a financial incentive to have Full-RBF enabled. I can't think of a reason why any miner or mining pool won't do this.

Do you have an example of a miner who doesn't?
hero member
Activity: 862
Merit: 662
How did he help him with the transaction? I have been reading this thread for quite some time but I think I missed the part about BOTs where someone tries to steal the sats after when someone withdraws the BTC.   Is there someone who can reply to this explanation of what really is going on?  If we really find out the private key then how can we claim it safely by not getting trapped by the Bots?

It already was explained here is the post, but basically you need to trust to the Private service of Mara slipstream.

Link: https://bitcointalksearch.org/topic/m.64379149

The death of the monitoring bots for the low bit challenge/puzzles such as the 66, 67, 68 bits.
The sure fire way to get all of your hard earned 6.6 BTC into one of your safe wallets...or is it a sure fire way?
Let me know what you think.

Ok, so here is the current, thoughtout way to beat the bots when dealing with the puzzle/challenge low bit wallets.

...

The main problem for those low entropy puzzles is the FullRBF feature of some versions of the bitcoin core, if the miners set the flag to accept TX that replace other TX without the RBF Flag

hero member
Activity: 714
Merit: 1010
Crypto Swap Exchange
have been reading this thread for quite some time but I think I missed the part about BOTs where someone tries to steal the sats after when someone withdraws the BTC.
Search for slipstream.mara.com and you will find answers in this thread or the other one with 1000 BTC in the thread's title.

TL;DR is, you can't safely publish the withdrawal transaction where you expose the public key when you want to claim low-entropy puzzles after you managed to find the private key.

Bots will recognize your transaction, take the public key and find within seconds the private key with Kangaroo or whatever is really fast for this. They will then simply replace your withdrawal transaction with their own to their own address. Bots will compete against each other until some substantial amount of the puzzle's price will become transaction fee. Mining pools might participate in this race because they may benefit from the rising transaction fee that every Full-RBF replacement will cause.

Simple answer: you can't publish the withdrawal transaction publicly, you risk loosing the replacement race and thus the puzzle's prize.
?
Activity: -
Merit: -
I don't think anything wrong happened here.

5.94 BTC went to

bc1ql5lrt3y97djyu5k8ewmz87nnemxheycp6wdree
bc1qdplvug87leypur2a27xh64u8cu78e0td8edwv7
bc1qpa20zkg6kr55yl7gxnwh37aj8q00rt70k6q8ru

whereas 0.66 BTC (exactly 10% of the prize 6.60 BTC) went straight to Binance (for cash out ?)

Someone helped the finder with the transaction and got 10% of the prize?


How did he help him with the transaction? I have been reading this thread for quite some time but I think I missed the part about BOTs where someone tries to steal the sats after when someone withdraws the BTC.   Is there someone who can reply to this explanation of what really is going on?  If we really find out the private key then how can we claim it safely by not getting trapped by the Bots?
newbie
Activity: 68
Merit: 0
Quote
In puzzle #67 there are approximately 1024 keys that start with that prefix (approximately), statistically every 2**56 bits it is repeated, so if you want to find another pattern you should subtract or add 2**56 to the private key of this one and look near that result, among one of those 1024 ranges, is the desired private key (probably), then what I would do is discard the 2**56 before and after that pattern because it is unlikely to be there.

this is pure statistics, but it is not crazy to try, as Einstein said "Insanity is doing the same thing over and over again and expecting different results."


Yes my friend, thank you for your explanation.

The goal is not 1024 wallets anyway, there are 4 wallet in the target.
There is already a range close to 2**56 between these ranges.
But it is definitely not 2**56, there are even 2**52 in it.

My target point was 4, so I used 4, but my 2 target is very far. If you ask how I determined these targets, with a very old 7-year-old excel data calculation.

Example

147573952589676000000 = 7FFFFFFFFFFF9B300

147573952589676000000 / 0.5467 or 0.5468 / 2
134967946396264861898= 7510E7828155490CA
134943263158079736649 = 750B6C6E1D9664B49


no wallet will appear up to 160 bits in the calculation range above. 147573952589676000000 is an example.

68 Wallet
295147905179352000000 = FFFFFFFFFFFF36600 instead of this, 68 is definitely not in this range. 69-70-71..... none of them.

Obviously I am progressing with Decimal calculation. Then I scan them with a certain numerical combination.

I forgot to give another example, sorry.

13zb1hQbWc3MrSxUhXkXQCb5JVCwASfZZR
Hex: 2E394A6F45691482A
Decimal: 53292403858936514602

13zb1hQbWc3UCetc7A7EvAGSVxiL1QWifS
Hex: 2E37B9DF452FEAFCD
Decimal: 53285357088854159309

Decimal difference is 7046770082398210 - average is around 2**52-53.
member
Activity: 239
Merit: 53
New ideas will be criticized and then admired.
1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9
1BY8GQbnueYebq5d6CE1wDfbdAWWy33ZyW
HEX:7545bf10859946eca
WIF:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qbRyCkJQmfJhcqQ1bT4q

Thank you very much for this information. cctv5go

Thank you for the 1BY8GQbnueY that I want to include in my own system.


Quote

lets make me clear, did you mean after your script found prefix 1BY8GQbnueY then automatically jump to the next prefix 1BY8GQbnueY?

A similar example.

1BY8GQbnueY how many do you think are in our 67 bit range?
1BY8GQbnue how many do you think are in our 67 bit range?

I found the answers to these in part.

So I confirmed these with hardware that was not too high, but my range is still far but not as far as space. Smiley

So I guess everyone learned the answer to the question I wrote before,
How many 1BY8GQbnueY starts are there in our 67 bit range? The correct answer is 4. Wink
In puzzle #67 there are approximately 1024 keys that start with that prefix (approximately), statistically every 2**56 bits it is repeated, so if you want to find another pattern you should subtract or add 2**56 to the private key of this one and look near that result, among one of those 1024 ranges, is the desired private key (probably), then what I would do is discard the 2**56 before and after that pattern because it is unlikely to be there.

this is pure statistics, but it is not crazy to try, as Einstein said "Insanity is doing the same thing over and over again and expecting different results."
newbie
Activity: 19
Merit: 0
That's correct. The more GPUs you have, the higher the chances of collisions due to the Birthday Paradox and the known key range. But I still don't believe 130 bits in 2 months  Grin


 Don't be fooled that psychology is not part of a very interested organization's toolbox.


130 bits wasn’t solved in two months. It’s just a psychological trick he’s playing on people like JLP and Zielar or many other who also have access to hundreds of GPUs. He’s just playing psychological tricks on them so they won’t work on the higher range and cut down his competitors.
newbie
Activity: 23
Merit: 0
That's correct. The more GPUs you have, the higher the chances of collisions due to the Birthday Paradox and the known key range. But I still don't believe 130 bits in 2 months  Grin

It's technically possible to solve 160 by tomorrow if we start today, as long as there are enough GPUs in existence.

But yes, one of the issues with RC's claim is he used 500 to 1000 GPUs in just 2 months (500 was the overly optimistic case of him being extremely lucky (much more luckier than just his method working as stated) AND without considering any DP overhead AND with using his super-double-fast-than-possible CUDA kernel no one thinks can exist AND assuming his entire distributed system worked perfectly without any bugs, issues, etc. which is always unlikely in the real world). There's better chances winning the lottery than achieving so many advancements in different problem areas.

So, the issue here is that the smoke could be easily lifted on him, because it's not like an every day customer (or employee?) that seeks out renting/"managing" hundreds of GPU instances for months in a row.

Someone who wants to lose his tracks would do it over a very extended period of time, with fewer GPUs. This would also make the attack cheaper, because of spot prices & price per teraflop decreasing over time.

If someone calls this jealousy or being a cry-baby, maybe they should put on their glasses. Creating a curtain of smoke is part of the game, you should think about what's under the curtain, and I think it is about extracting information, under the sense that it might no longer be useful. Don't be fooled that psychology is not part of a very interested organization's toolbox.
This topic is increasingly reminiscent of the rat race movie. maybe it's worth stopping and starting a dialogue and rallying to achieve the goal? I don't have the ability to properly set up a kangaroo. but, there are people who can provide a lot of GPU. for the price of electricity. suggest options...
member
Activity: 165
Merit: 26
That's correct. The more GPUs you have, the higher the chances of collisions due to the Birthday Paradox and the known key range. But I still don't believe 130 bits in 2 months  Grin

It's technically possible to solve 160 by tomorrow if we start today, as long as there are enough GPUs in existence.

But yes, one of the issues with RC's claim is he used 500 to 1000 GPUs in just 2 months (500 was the overly optimistic case of him being extremely lucky (much more luckier than just his method working as stated) AND without considering any DP overhead AND with using his super-double-fast-than-possible CUDA kernel no one thinks can exist AND assuming his entire distributed system worked perfectly without any bugs, issues, etc. which is always unlikely in the real world). There's better chances winning the lottery than achieving so many advancements in different problem areas.

So, the issue here is that the smoke could be easily lifted on him, because it's not like an every day customer (or employee?) that seeks out renting/"managing" hundreds of GPU instances for months in a row.

Someone who wants to lose his tracks would do it over a very extended period of time, with fewer GPUs. This would also make the attack cheaper, because of spot prices & price per teraflop decreasing over time.

If someone calls this jealousy or being a cry-baby, maybe they should put on their glasses. Creating a curtain of smoke is part of the game, you should think about what's under the curtain, and I think it is about extracting information, under the sense that it might no longer be useful. Don't be fooled that psychology is not part of a very interested organization's toolbox.
newbie
Activity: 19
Merit: 0
The amount of loudmouths and stupidity that has surfaced here recently is quite alarming. I don't know what some want to achieve to drive off users who actually achieved some success. But hey, you do yours and I'm quite confident that all the loudmouths simply won't achieve any progress or success here.

Just put the bullshitters on your ignore list. It's highly unlikely they'll contribute anything positive to this thread. Cleans the mess here to an acceptable level and makes following real and good ideas here far less annoying.

Don't waste your time to attack me, you're likely on my ignore list or earn a spot on it anyway.

We have no hate against anyone's success—in fact, we genuinely wish him the best and hope he breaks the world record for solving #135. But let’s not forget that he’s the one who started all the trolling and later deleted his messages to avoid the backlash.



newbie
Activity: 19
Merit: 0
Hey there, how can the "unfortunate event" have place? There's something I'm not getting about it. Could you please explain to me how could the sniper get the private key and snatch all the money on the address?

Look at TX (the real solver)
{
  https://www.blockchain.com/explorer/transactions/btc/8c8ec6b3511c62500ea9b3a1c30ca937e15d251b55d30290a2a6da2f1124f3fb
}

It is safe to assume once he found the key, he accessed his wallet using electrum (or similar) and swept the #66 address (13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so)
{
  You can sweep a key with the WIF -> p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZfFoWMiwBt943V7CQeX
}

Now, that is a massive mistake, since there were 34 UXTO and only 2 actually worth taking.
{
 1) 0.066 BTC
 4) 5.940 BTC
}

About a minute later this TX shows up.
{
  https://www.blockchain.com/explorer/transactions/btc/57a88f47e4c047740b782a5562fca143ce85de0373cbff3a7d406e9ae7fc2f5f
}

Now, this one looks scripted.
{
 A) Only the highest UXTO was selected (5.940 BTC)

 B) The fee offered was 76,395 sats (+50K sats than first TX)
}

So miners dropped the first TX and replaced with the second TX, since it gave them more sats per byte.

The idea here is once you broadcast a TX, the pubkey shows up in the mempool.

Once the bot had the pubkey, it found the secret number in seconds.

And the problem with #66 is the secret number is very very small [46346217550346335726]

And this can possibly happen to keys all the way to #129, assuming the bot has the required precomputed DPs.

This is a theory, you have to do a lot of research on the topic if you want the real answer to #66.

1. How when the bot got the pubkey was able to find the secret number in seconds?
2. What is the secret number [46346217550346335726]?
3. What are the DPs?

sorry for the trivial questions, but I am new and still trying to grasp some terms and how they are related to each other
thanks
Pages:
Jump to: