Bitcoin puzzle transaction ~32 BTC prize to who solves it

[bibilgin]

#67 6d6exxxxxxxxxxxxx

Can I ask how you came to this conclusion? Because I came to a similar conclusion. But not that close.

(There is a close conclusion in my range.) That's why I asked.

[mabdlmonem]

#67 6d6exxxxxxxxxxxxx

its not there

Could you please share the tool you are using for scan that range?

[cctv5go]

Puzzle 67: The private key is likely to be in the range of 50000000000000000 to 60000000000000000.

[kosiosl]

Puzzle 67: The private key is likely to be in the range of 50000000000000000 to 60000000000000000.

Based on what??

[WanderingPhilospher]

I have at least 64 each DP 32s, in each 68 bit range, starting from 135s public key.

So, public key +100000000000000000, all the way up to:

......
12BB7400000000000000000
12BB7500000000000000000
12BB7600000000000000000

Current distance:
1837dd00000000000000000
1837de00000000000000000

[bibilgin]

Hello everyone. let's say I found a solution
is there any chance to safely withdraw money please anyone who understands answer. Thanks in advance
I've been working on this puzzle for 9 months now.

You create a btc address and withdraw some and take it to Binance, there you invest in other currencies or you can withdraw it.
I would take it to Binance to settle a small portion.


For those looking for the solution, I'm doing decrement and using Hash 160 to scan, any other method I've been looking at may leave the key behind.
Am I good at this? I don't know, but I'm saying at the tip of 0x77a... there's nothing up, I believe it's at 0x6f... but as I'm stubborn I decided to start at the tip to be safe, I'm sure with this run before Christmas someone will find it.


I have a disability, so if I've spoken nonsense, disregard it and don't insult me, I'd be grateful if anyone has advice, thank you.

My friend, you misunderstood. @fahri.hk did not say that.

During the transfer, the password of the 67th wallet will be revealed within 30 seconds in the slightest transaction, during this time someone else (THIEF) will steal the money by paying more fees than you.

I advise you to be careful about this.

It is not only a problem to find the 67th wallet, but also to transfer it to your own account.

Good Luck..

[citb0in]

Did you seriously expect to find what you were looking for?

Did you seriously think there is a solution?
Seems you seriously think that there is no privatekey for 67?

Lets me say this..
Any scan on range of 73786976294838206464 - 147573952589676412927 ,
is just waste of time?
There is only one correct value and you are an idiot if try to scan any else value?


citb0in just proved to be the most idiot.

You have just impressively demonstrated who the idiot is. Applause

[mcdouglasx]

Nobody talks about https://github.com/RetiredC/RCKangaroo, has anyone tested it? What is the difference between speed and success rate compared to other algorithms?
It is a topic that could be of interest here.

[b0dre]

Nobody talks about https://github.com/RetiredC/RCKangaroo, has anyone tested it? What is the difference between speed and success rate compared to other algorithms?
It is a topic that could be of interest here.

I've already tested it on Linux with an RTX 3060 and was able to find 66 in less than a second.

[b0dre]

You create a btc address and withdraw some and take it to Binance, there you invest in other currencies or you can withdraw it.
I would take it to Binance to settle a small portion.


For those looking for the solution, I'm doing decrement and using Hash 160 to scan, any other method I've been looking at may leave the key behind.
Am I good at this? I don't know, but I'm saying at the tip of 0x77a... there's nothing up, I believe it's at 0x6f... but as I'm stubborn I decided to start at the tip to be safe, I'm sure with this run before Christmas someone will find it.


I have a disability, so if I've spoken nonsense, disregard it and don't insult me, I'd be grateful if anyone has advice, thank you.

My friend, you misunderstood. @fahri.hk did not say that.

During the transfer, the password of the 67th wallet will be revealed within 30 seconds in the slightest transaction, during this time someone else (THIEF) will steal the money by paying more fees than you.

I advise you to be careful about this.

It is not only a problem to find the 67th wallet, but also to transfer it to your own account.

Good Luck..

How will they know that you discovered the private key without you making a transfer?

Now my question is, how?

I trade on Binance, I don't know of a better exchange.

This is because as soon as a transaction is published from the wallet, the public key is revealed, and bots use the public key to obtain the private key, which is almost instantaneous for a 67-key with the public key exposed.

[karrask]

You create a btc address and withdraw some and take it to Binance, there you invest in other currencies or you can withdraw it.
I would take it to Binance to settle a small portion.


For those looking for the solution, I'm doing decrement and using Hash 160 to scan, any other method I've been looking at may leave the key behind.
Am I good at this? I don't know, but I'm saying at the tip of 0x77a... there's nothing up, I believe it's at 0x6f... but as I'm stubborn I decided to start at the tip to be safe, I'm sure with this run before Christmas someone will find it.


I have a disability, so if I've spoken nonsense, disregard it and don't insult me, I'd be grateful if anyone has advice, thank you.

If you find 67, use the binance pool, they also speed up the transaction. Good luck, friend, may you be lucky!

[fotosdecapa]

You create a btc address and withdraw some and take it to Binance, there you invest in other currencies or you can withdraw it.
I would take it to Binance to settle a small portion.


For those looking for the solution, I'm doing decrement and using Hash 160 to scan, any other method I've been looking at may leave the key behind.
Am I good at this? I don't know, but I'm saying at the tip of 0x77a... there's nothing up, I believe it's at 0x6f... but as I'm stubborn I decided to start at the tip to be safe, I'm sure with this run before Christmas someone will find it.


I have a disability, so if I've spoken nonsense, disregard it and don't insult me, I'd be grateful if anyone has advice, thank you.

Did you scan from 0x77a... to 0x7fff...? How long did it take to scan?

[kTimesG]

So are there any providers with Blackwell GPUs yet?

NB regarding RCKangaroo - it runs 1.5x slower than my kernel, it's obviously not optimized other than tweaking usage of the fast caches to minimize memory latencies. Inversion is a performance killer, using old SafeGCD. You'll get better speeds and faster solve times if running a normal 3-kang algorithm (with no cycles headaches) instead, with low-level optimizations. Why? Because the faster speed of simpler code compensates for the slightly higher algorithm complexity (which is already around 1.4 - 1.5 in secp256k1 specific case, not 1.7, and definitely not 2.08 like in 2-kang case).

[Etar]

You say:

I can currently squeeze out 6.2 Gk/s on a RTX 4090, but some users here claim they can obtain 8 Gk/s or more

RetiredCoder say:

Note that I have not included all possible optimizations because it's public code and I want to keep it as simple/readable as possible.

Git RCKangaroo say:

Code:

about 8GKeys/s on RTX 4090.

You say:

NB regarding RCKangaroo - it runs 1.5x slower than my kernel.

How can this be understood? You were able to reach 12GKeys/s on RTX 4090?

[mcdouglasx]

This issue with Rc needs to be tested.
- integrate other kangaroo methods apart from SOTA into RcKangaroo.
While users may see improvements, this may be due to the cuda implementation and not the Sota algorithm itself.

[b0dre]

This issue with Rc needs to be tested.
- integrate other kangaroo methods apart from SOTA into RcKangaroo.
While users may see improvements, this may be due to the cuda implementation and not the Sota algorithm itself.

While RCKangaroo might have a slower overall runtime compared to other methods, it consistently finds the solution (or "keys") much faster. It achieves results in a remarkably short time.

[kTimesG]

You say:

I can currently squeeze out 6.2 Gk/s on a RTX 4090, but some users here claim they can obtain 8 Gk/s or more

RetiredCoder say:

Note that I have not included all possible optimizations because it's public code and I want to keep it as simple/readable as possible.

Git RCKangaroo say:

Code:

about 8GKeys/s on RTX 4090.

You say:

NB regarding RCKangaroo - it runs 1.5x slower than my kernel.

How can this be understood? You were able to reach 12GKeys/s on RTX 4090?

Apples and oranges... I use a lame RTX 3050 Laptop GPU for development, and only test once in a while on high-grade GPUs.

JLP code: 280 MK/s
RCKang: 441 MK/s
My kernel: 690 MK/s (with a much less memory usage and much less total kangaroos)

However, my focus was always on optimizing the computations. RTX 3050 only has 1 MB of L2 cache, while RTX 4090 has 100 MB, so his tweaks don't do wonders for lower-end GPUs.

However, I did not yet added any L2 memory tweaks like in RCKang, so I will try to do that when I have some time and test again on RTX 4090 to see whether there is an improvement. FYI my use-case is squeezing in as much kangaroos as possible WITHOUT having to thrash any variables up to global memory, and this means relying much more on utilizing the L1 cache as most optimal as possible.

[bibilgin]

Yes friends, this place is starting to become very strange.

1- New users started coming in large numbers and started to touch on very interesting topics.

2- Someone says they scanned from 77a to 77ff, another new user asks did you do that? First message?

3- When the 67th wallet is found, there are talks about transferring it with methods like binance, btc import priv key. (They are not aware of the danger, because they did not look at the old posts and what happened to the 66th wallet.)

4- There are many new friends, but it is interesting that instead of getting information, they say do it like this, do it like that, as if they are familiar with the subject.

Either these friends are someone's 2nd or 3rd user accounts, they are creating a perception of change in society.

Or all of these friends started coming at the same time. (We are having a lot of fun..

[karrask]

Yes friends, this place is starting to become very strange.

1- New users started coming in large numbers and started to touch on very interesting topics.

2- Someone says they scanned from 77a to 77ff, another new user asks did you do that? First message?

3- When the 67th wallet is found, there are talks about transferring it with methods like binance, btc import priv key. (They are not aware of the danger, because they did not look at the old posts and what happened to the 66th wallet.)

4- There are many new friends, but it is interesting that instead of getting information, they say do it like this, do it like that, as if they are familiar with the subject.

Either these friends are someone's 2nd or 3rd user accounts, they are creating a perception of change in society.

Or all of these friends started coming at the same time. (We are having a lot of fun..

I don't know about the others, but I'm still kind of real, not a bot... about the binance, I read that you can sort of make a mara. Well, I won't say anything for the rest (real, not real).

[cctv5go]

It seems that few people here have started researching and solving puzzles using Bitcoin private key WiFiI tested a great program, but I haven't made it public yet.