Pages:
Author

Topic: == Bitcoin challenge transaction: ~1000 BTC total bounty to solvers! ==UPDATED== - page 2. (Read 54732 times)

member
Activity: 165
Merit: 26
At the moment I can't explain it with scientific precision. The reason to scrap the puzzles #161 to #256 isn't that #160 likely won't be reachable in our lifetime and/or this century and maybe beyond. The reason is that hashing with RIPEMD160 caps the unambiguous bitrange to 160.

The relation private key --> public key is very likely unique, we can assume no collisions (I can't prove that mathematically, though), i.e. no two different private keys will give you the same public key.

To get a legacy public address there's a hashing step with RIPEMD160 that gives you a 160bit hash, thus there are mathematically obvious at max. 296 public keys with the same RIPEMD160 hash aka same legacy address.

Therefore by the initial puzzle conditions (no public key was revealed first), puzzles #161 to #256 make not much sense. This didn't occur to the puzzle creator at first but when he was nudged to it, he realized his mistake and redistributed funds from the no-sense range to the makes-sense range.

AFAIR revealing public keys for puzzles of multiples of 5 came even later (I could be wrong, don't have it crystal clear from my memory's bottom area).

Well by the same reasoning, puzzles from 81 to 159 don't make sense at all. It would have made more sense for 161-255 to only have outgoing TX, not be redistributed, because for example puzzle 254 would have somewhat similar difficulty as puzzle 127. But once #160 gets solved, then no one would be interested in solving 81 for a half-reward but double difficulty.
hero member
Activity: 714
Merit: 1010
Crypto Swap Exchange
~~~
At the moment I can't explain it with scientific precision. The reason to scrap the puzzles #161 to #256 isn't that #160 likely won't be reachable in our lifetime and/or this century and maybe beyond. The reason is that hashing with RIPEMD160 caps the unambiguous bitrange to 160.

The relation private key --> public key is very likely unique, we can assume no collisions (I can't prove that mathematically, though), i.e. no two different private keys will give you the same public key.

To get a legacy public address there's a hashing step with RIPEMD160 that gives you a 160bit hash, thus there are mathematically obvious at max. 296 public keys with the same RIPEMD160 hash aka same legacy address.

Therefore by the initial puzzle conditions (no public key was revealed first), puzzles #161 to #256 make not much sense. This didn't occur to the puzzle creator at first but when he was nudged to it, he realized his mistake and redistributed funds from the no-sense range to the makes-sense range.

AFAIR revealing public keys for puzzles of multiples of 5 came even later (I could be wrong, don't have it crystal clear from my memory's bottom area).
full member
Activity: 282
Merit: 114
Has anyone cracked the 256 key?
Nobody. The initial idea of ​​the puzzle was to include a prize on each range, but after a few years the creator transferred the funds from addresses 161-256 to the remaining unsolved addresses from 160 downwards, making the prizes more appealing. I think that because we won't even find that 160 in our lifetime :-)
?
Activity: -
Merit: -
Has anyone cracked the 256 key?
newbie
Activity: 2
Merit: 0
What if I found wallet 69, initiated the transaction, and then replaced the transaction myself (by stealing from myself), would it work?
How many times can a transaction be "stolen" before it is mined?
You apparently don't quite understand how RBF and Full-RBF work. As RBF is in the interest of miners/mining pools because it increases the transaction fee, you can safely assume that basically every miner/mining pool has Full-RBF enabled. Therefore you can't prevent RBF even when you flag your transaction as non-RBF.

Didn't you read at least past few pages? Your only chance would be to queue your transaction to be mined non-publicly, e.g. via https://slipstream.mara.com. I searched this thread and below citation is the first hit of it here (page 51 of this thread, so not too far in the past). I took the liberty to shrink the picture in the quoted snippet a bit.


The only way to do that is by using the MARA Pool Slipstream. The transaction will be mined before the public key enters the mempool.

It won't actually be seen at all through the mempool.

https://i.postimg.cc/pTmPGBWN/2024-08-04-10-01.png

Thank you. It really works. I tested it by creating a "fragile 69bit" wallet with $50 and made the transfer and the public key was not listed in the mempool.
Now I can continue my code using FPGA. Thank you very much for your kindness.
newbie
Activity: 18
Merit: 0
The entered phrase with a request to send the solution to PM is the only thing I can do to be able to learn the solutions... at least for statistical purposes... because this is probably the MAX of what you can be happy about today in the subject of this challenge.
Yes, i am also interested in knowing the private keys to these solved wallets, but when a year ago I asked to share 120 workfiles to possibly find out the private key, no one shared them.

There are actually a few solutions!!

I am not a super mathematician, but I am someone who loves details on statistics and probability calculations.

I had stopped statistical studies due to some problems. But now, the growth of the reward from wallet 66 has caught my attention.

In this regard, I made some probability calculations based on the source of the n=nP formula and verified some parts because my hardware power is low.
Actually, this event is about a very thought-provoking mathematics and probability calculations.

I know that wallets like 67-68-69... will be found in a short time with high hardware power that gradually increases with Vanitysearch(--keyspace).

The important thing is that n=? np=? the rest automatically shortens the time.
member
Activity: 110
Merit: 61
The entered phrase with a request to send the solution to PM is the only thing I can do to be able to learn the solutions... at least for statistical purposes... because this is probably the MAX of what you can be happy about today in the subject of this challenge.
Yes, i am also interested in knowing the private keys to these solved wallets, but when a year ago I asked to share 120 workfiles to possibly find out the private key, no one shared them.
newbie
Activity: 18
Merit: 0
Quote
If a pool is properly developed this should never be a problem, the users will no have way to use the server as oracle, and the users can't lie about what they scan or what they don't scan.

Yes, you are right.

1- It will be written directly on the screen of the person who finds the wallet. Surprise Smiley

2- The pool will not have any profit, it will only be supported by the person who finds it and the donation method by other users.

3- It does not matter how powerful the hardware is, who scans it, they will know that they did this for themselves and their luck.

After telling Chris the reasons and reasons about this issue, TTD (ttsdsales) put the reward system. Smiley

My hardware is low but I found the wallet, I just entered the system. Thanks to my luck and knowledge, someone else will get 300k dollars but I will get 300 dollars.  Huh
hero member
Activity: 862
Merit: 662
For example, what if he wants to get information by lying about the range he did not scan?

If a pool is properly developed this should never be a problem, the users will no have way to use the server as oracle, and the users can't lie about what they scan or what they don't scan.
newbie
Activity: 18
Merit: 0
Quote
I don't think we lost it, but we got screwed over. Another pool and another unknown finder of the key who didn't brag about the win personally. I think both 66 and 64 were solved by TTD.

I advise you not to get involved in anything group-based in the future that is supposed to bring financial benefits and that over the internet, because you know... they will screw you over again. They certainly won't screw me. I congratulate those who made withdrawals through trickery on their ingenuity... and I hope it works out for you and affects your families.


I completely agree with ziealer on this. He may be right about finding TTD in 64 and 66 wallets.

Zielar, who has had TTD before, I don't know what problem he has with Chris Zahrt.

I don't trust places like this from the beginning. Actually, I have a different idea in mind, but everyone's opinion may be needed.

what is TTD?

ttdsales /66bit/ ??

ttdsales/67bit It's open, let's become a member now. Smiley

a community of people who waste their time and hardware.

Because the system is a closed circuit system, no one can prove anything. You find the money, but my server informs me. You can't see the background. Smiley


-----------------------------------------------------
Zielar, one of the people closest to Chris (TTD), also made a statement along these lines. I wonder what happened between them?

Zielar, who put a lot of effort into the system at first, now doesn't like the system?
I hope this will answer the question and other users will understand that it is not a correct system.



One of the system ideas is,

I scan a few ranges, the other person scans the range at the same level and we share information with each other.
There will be many things like system vulnerabilities etc.

For example, what if he wants to get information by lying about the range he did not scan?
User, IP, MAC address. BAN!! Smiley
full member
Activity: 297
Merit: 133
How puzzles could have been generated:

Code:
#!/usr/bin/env python3

import random
from tqdm import tqdm

i=2

def go(i, x):
random.seed(a=x, version=1)

while i<=2**160:
l=i
h=i*2-1
print(hex(random.randrange(l,h)), end=' ')
i=i*2

for j in tqdm(range(0,1000001)):
go(i, j)
newbie
Activity: 1
Merit: 0
Quote
I don't think we lost it, but we got screwed over. Another pool and another unknown finder of the key who didn't brag about the win personally. I think both 66 and 64 were solved by TTD.

I advise you not to get involved in anything group-based in the future that is supposed to bring financial benefits and that over the internet, because you know... they will screw you over again. They certainly won't screw me. I congratulate those who made withdrawals through trickery on their ingenuity... and I hope it works out for you and affects your families.


I completely agree with ziealer on this. He may be right about finding TTD in 64 and 66 wallets.

Zielar, who has had TTD before, I don't know what problem he has with Chris Zahrt.

I don't trust places like this from the beginning. Actually, I have a different idea in mind, but everyone's opinion may be needed.

what is TTD?
newbie
Activity: 18
Merit: 0
Quote
I don't think we lost it, but we got screwed over. Another pool and another unknown finder of the key who didn't brag about the win personally. I think both 66 and 64 were solved by TTD.

I advise you not to get involved in anything group-based in the future that is supposed to bring financial benefits and that over the internet, because you know... they will screw you over again. They certainly won't screw me. I congratulate those who made withdrawals through trickery on their ingenuity... and I hope it works out for you and affects your families.


I completely agree with ziealer on this. He may be right about finding TTD in 64 and 66 wallets.

Zielar, who has had TTD before, I don't know what problem he has with Chris Zahrt.

I don't trust places like this from the beginning. Actually, I have a different idea in mind, but everyone's opinion may be needed.
newbie
Activity: 23
Merit: 2
I meant stolen computing resources. By the owner of 3Emiwzxme7Mrj4d89uqohXNncnRM15YESs. It's not a business...

Maybe they've been cracking keys using stolen credit cards to squat as many GPU's as possible, who knows. See this blog, it's a good read: https://modal.com/blog/catching-cryptominers
full member
Activity: 282
Merit: 114
***UNKNOWN*** Please finder to send solution by PM anonyumously

I don't know if such person/people is reading us but...

A clever way to disclose the private key is the next:

Take all the inputs to your address but leave some dust input behind (all those wallets has always some dust inputs)
Then once that you cleared all the balances in all chains except one dust, make a special TX where you manually chose a repeated Nonce value or one with some difference small to be solvable with some math.
Broadcast that TX and someone should notice that repeated or weak R value and the key should be solved easily.




Higher school of driving :-D but as one of the few I have to admit that you contribute a lot of valuable issues to the topic. I haven't been here for some time because occasionally somewhere on the side I "cooperated" with ttd with free funds. Somewhere there, at the beginning at pool 64 I had concerns as to whether the creation of this pool was really for the purpose of "mutual benefit", but later I dispelled my concerns due to good contact with the owner. It became distasteful when, convinced by the recent successes of pool 66, I was focused on part of the prize - I finally dispelled my concerns in a negative way. Once again, someone has developed a twice as difficult range with positive results - and once again no one has flaunted it either before or after finding a solution... Well, yes - the simplest. Who is going to prove anything to whom when the results of the work have always been sent to the server. All you have to do is receive the key, withdraw it and announce that someone from outside has done it, right? Besides, tell me honestly - do you think that anyone ALONE is trying to break larger and larger ranges?? since even for me level 64 already seems so high that I gave up. And here you go - the last two low-level levels (for which pools were created) - the finder of the key unknown and the pool is not the finder...? And for credibility, it was enough to create some newbie account and post with the key and it would immediately look different... besides, for a profit of a million dollars - during these two years I would be able to develop even this account well and come up with a good story about how I got to this key)... but oh well... not every person acts the same. Personally, I completely give up on this type of "cooperation" and I strongly advise against it to others.. It's a waste of your money to pump it into others. If you think otherwise - you can deposit it into my wallet without deluding yourself that you will gain anything except my gratitude:
=============
bc1qv5a3urpj3fszalsuw0r4dlafxel68aaypqxxqlzhl8ygnehw6k9s8d3sm2
============
To be honest - what pissed me off was not even that I was disappointed in my opinion, but that despite spending free funds on some contribution to a previously trusted pool - in the end it turned out that I spent $4,000 on the scale of the entire contribution, so not a small amount. I know that there are those who spent much more and I sympathize with you very much. I know that life will return it to you in a double positive form. As I promoted earlier - I currently RECOMMEND NOT cooperating with you in any projects related to this challenge, because as statistics have shown - since I found with JLP and published solutions to the found ranges - each subsequent level has been discovered by an UNKNOWN PERSON in an UNKNOWN WAY... the solution is UNKNOWN for most, and the costs and requirements are much greater. There is no point in hiding - this challenge has already become only a matrix for creating the perfect idea for how to get rich by walking over dead bodies... and with today's technology - the chances are slim... and this was probably also the idea of ​​the creator, who paid so much BTC additionally to wallets. The entered phrase with a request to send the solution to PM is the only thing I can do to be able to learn the solutions... at least for statistical purposes... because this is probably the MAX of what you can be happy about today in the subject of this challenge.
hero member
Activity: 862
Merit: 662
***UNKNOWN*** Please finder to send solution by PM anonyumously

I don't know if such person/people is reading us but...

A clever way to disclose the private key is the next:

Take all the inputs to your address but leave some dust input behind (all those wallets has always some dust inputs)
Then once that you cleared all the balances in all chains except one dust, make a special TX where you manually chose a repeated Nonce value or one with some difference small to be solvable with some math.
Broadcast that TX and someone should notice that repeated or weak R value and the key should be solved easily.


full member
Activity: 282
Merit: 114
full member
Activity: 282
Merit: 114
As we can see this is a fact. 120,125,130 were withdrawn to the same wallet - 3Emiwzxme7Mrj4d89uqohXNncnRM15YESs


This is Zellar wallet.

Who is he? Or what does it mean?


he

https://bitcointalksearch.org/topic/m.51803085

and he in cooperation

https://bitcointalksearch.org/user/jeanluc-2550169

together take 120,125,130

You are a serious idiot. I feel sorry for you, my son.

Since 130 has been solved and the key has not been provided again, the same as 66, in which I invested quite a bit of effort, and the super honest ttd pool perfectly hid the fact that the key was found - I am completely disinterested in this crap. Higher wallets lose their meaning, because it is not known who guessed what and how much they ripped off, so it does not contribute anything at all, while lower addresses are stolen by pseudo-smart guys. Here it is no longer fun and striving to find a solution, but a fight for who will be the first and how cunningly will rob the wallet. Good luck. And I greet those wimps like COBRAS who have a lot to say about their unfucked egos.




Hello, I noticed something.

66. Wallet transfer time: 9/13/2024, 01:59:39
Your message: 09/13/2024, 01:57:12

I guess you found the wallet?
Why haven't you had any messages since you became a member in January 2024?
It's very interesting, I was curious about your hardware and what software did you use? (Unless you're the creator, of course?)

I wish it was me but unfortunately not. I was part of the 66bit pool trying to find the key but we lost it. The hex private key was posted in telegram. All I did was input the hex key into a python script that spits out all the address info.
I am more of a reader than writer so I never posted before.

I don't think we lost it, but we got screwed over. Another pool and another unknown finder of the key who didn't brag about the win personally. I think both 66 and 64 were solved by TTD.

I advise you not to get involved in anything group-based in the future that is supposed to bring financial benefits and that over the internet, because you know... they will screw you over again. They certainly won't screw me. I congratulate those who made withdrawals through trickery on their ingenuity... and I hope it works out for you and affects your families.
hero member
Activity: 714
Merit: 1010
Crypto Swap Exchange
What if I found wallet 69, initiated the transaction, and then replaced the transaction myself (by stealing from myself), would it work?
How many times can a transaction be "stolen" before it is mined?
You apparently don't quite understand how RBF and Full-RBF work. As RBF is in the interest of miners/mining pools because it increases the transaction fee, you can safely assume that basically every miner/mining pool has Full-RBF enabled. Therefore you can't prevent RBF even when you flag your transaction as non-RBF.

Didn't you read at least past few pages? Your only chance would be to queue your transaction to be mined non-publicly, e.g. via https://slipstream.mara.com. I searched this thread and below citation is the first hit of it here (page 51 of this thread, so not too far in the past). I took the liberty to shrink the picture in the quoted snippet a bit.


The only way to do that is by using the MARA Pool Slipstream. The transaction will be mined before the public key enters the mempool.

It won't actually be seen at all through the mempool.


hero member
Activity: 862
Merit: 662
I meant stolen computing resources.

Well that is a possibility? But unless you provide some evidence, all it a pure speculation.

It's not a business...

Same, he/they can be a single person, a group of people, we DON'T KNOW.

How many times can a transaction be "stolen" before it is mined?

Many Replacements can be done until almost 100% of the balance become in a Fee for the miner.

But this depends of how many time a miner takes to mine that specific block, it can be 1 second from your TX or some hours from IT, that is something that we don't control.
Pages:
Jump to: