Bitcoin puzzle transaction ~32 BTC prize to who solves it

[Akito S. M. Hosana]

No. In my case, I only verify whether the WIF (Wallet Import Format) is correct. The output displays only checksum-validated WIFs. The second script computes the corresponding public key and address.

How many verified WIFs do you have in the output generated by the GPU? 

It depends on how many characters are missing in the WIF and their exact positions. For example, if 10 characters are missing at the beginning, the recovery speed would be approximately 2,000 valid WIFs per minute.

So you need 30 - 50 GPUs to have 1000 valid WIfs/s ?   

[Bram24732]

Thanks, there is still one flaw :
By counting only "wins" you miss one very important piece of data : how fast was a method compared to the other on each simulation ? A win 5x faster does not have the same value as a win 1.2x faster.
This can be changed by summing the number of checks made over all the simulations, like this :

Code:

results = {"sequential": {"wins": 0, "checks": 0}, "precise": {"wins": 0, "checks": 0}, "ties": 0}
...
results["sequential"]["checks"] += seq_result["checks"]
results["precise"]["checks"] += pre_result["checks"]
.....
Sequential: {results['sequential']['checks']}
Prefix: {results['precise']['checks']}

Just as the script commonly handles it, it's fine, because the important thing here was to demonstrate that prefixes are more efficient in the majority of attempts. It does not include computational load, because that's unfair, as we omit the entire Bitcoin process, and besides, it's not the same to omit 1000 keys out of 5000 as to use a 16**12 setup to give an example... but the basic aspect has already been demonstrated, which was the probabilistic success rate.

I think being first without taking into account how much faster you are is not reflecting the stastistical reality.
But it's ok to disagree

[nomachine]

So you need 30 - 50 GPUs to have 1000 valid WIfs/s ?   

Yes, but you'll need much more if you want to solve it in a reasonable amount of time—though still less than what's required for Puzzle 69. 

[Akito S. M. Hosana]

So you need 30 - 50 GPUs to have 1000 valid WIfs/s ?   

Yes, but you'll need much more if you want to solve it in a reasonable amount of time—though still less than what's required for Puzzle 69. 

What will you do if you solve this?

[nomachine]

So you need 30 - 50 GPUs to have 1000 valid WIfs/s ?   

Yes, but you'll need much more if you want to solve it in a reasonable amount of time—though still less than what's required for Puzzle 69. 

What will you do if you solve this?

Hahaha, take it easy... It’s not that simple... But... Every member in this topic will get 0.2 BTC—if they have a BTC address in their signature. Satisfied? 

[fantom06]

=== FINAL RESULTS ===
Wins:
Sequential: 2105
Prefix: 2688
Ties: 207

[Bram24732]

-- Sim results

If you sum the number of checks over 10k simulations you get this :

Code:

=== FINAL RESULTS ===
Sequential: 495816995
Prefix: 496059807

This is a bias since the prefix method wins most of the time, meaning it is the best choice. When the prefix method loses, it obviously generates more keys because it is assumed that the target was omitted. And the goal is to find your best option to win and not who loses worse.

I think being first without taking into account how much faster you are is not reflecting the stastistical reality.
But it's ok to disagree

The times when the prefix method wins, it traverses fewer keys than the sequential method; therefore, by common sense, it saves computational power.

Statistically, prefixes are the best option most of the time.


Similarly, the overall statistics are more or less equal when considering total traversals, both won and lost. However, prefixes still yield the highest success rate. There's no need to overcomplicate it.

It not complicated. Nor is it a bias. Those are actual numbers out of your script.
On average, both methods require the same number of steps to reach a solution.

[Akito S. M. Hosana]

Hahaha, take it easy... It’s not that simple... But... Every member in this topic will get 0.2 BTC—if they have a BTC address in their signature. Satisfied? 

I'm not a full member yet. 

[fantom06]

-- Sim results

If you sum the number of checks over 10k simulations you get this :

Code:

=== FINAL RESULTS ===
Sequential: 495816995
Prefix: 496059807

This is a bias since the prefix method wins most of the time, meaning it is the best choice. When the prefix method loses, it obviously generates more keys because it is assumed that the target was omitted. And the goal is to find your best option to win and not who loses worse.

I think being first without taking into account how much faster you are is not reflecting the stastistical reality.
But it's ok to disagree

The times when the prefix method wins, it traverses fewer keys than the sequential method; therefore, by common sense, it saves computational power.

Statistically, prefixes are the best option most of the time.


Similarly, the overall statistics are more or less equal when considering total traversals, both won and lost. However, prefixes still yield the highest success rate. There's no need to overcomplicate it.

Wins:
Sequential: 39 (Average Win Margin: 55.95%)
Prefix: 899 (Average Win Margin: 3.37%)
Ties: 62

Total Checks:
Sequential: 494,958,197
Prefix: 502,727,060

[fantom06]

Simulation 10000: Sequential = 132246 | Prefix = 122826

=== FINAL RESULTS ===
Wins:
Sequential: 321 (Average Win Margin: 48.81%)
Prefix: 9033 (Average Win Margin: 3.21%)
Ties: 646

Total Checks:
Sequential: 5,216,987,277
Prefix: 5,224,672,888

[White hat hacker]

Can you tell me the difference between the prefix method and the random method? At the end of the day, the code is still random—there’s no magic to it and it's not surprising..


It's better to use both random and sequencial.

[Bram24732]

It not complicated. Nor is it a bias. Those are actual numbers out of your script.
On average, both methods require the same number of steps to reach a solution.

Noo,

If we take these metrics into account, it only means that, approximately within that key range, the prefix method achieved a higher success rate, which is highly significant.

dividing keys(avg) by wins, you'd determine the average success rate.

Code:

keys(avg)/wins  =  success_rate(avg)

I'm not sure what's unclear.
Over 10000 attempts, sequential method had to make 5,216,987,277 checks before finding 10000 solutions
Over 10000 attempts, prefix method had to make 5,224,672,888 checks before finding 10000 solutions
The average number of checks is similar for both methods ?

[fantom06]

=== Configuration ===
Total numbers: 1,048,576
Block size: 4,096
Prefix: 4 characters (16^4 combinations)
Simulations: 10000

=== FINAL RESULTS ===
Wins:
Sequential: 343 (Average Win Margin: 51.00%)
Prefix: 9054 (Average Win Margin: 3.23%)
Ties: 603

Total Checks:
Sequential: 5,283,346,262
Prefix: 5,306,416,800




=== Configuration ===
Total numbers: 2,097,152
Block size: 4,096
Prefix: 3 characters (16^3 combinations)
Simulations: 10000

=== FINAL RESULTS ===
Wins:
Sequential: 3736 (Average Win Margin: 42.57%)
Prefix: 6244 (Average Win Margin: 36.55%)
Ties: 20

Total Checks:
Sequential: 10,472,126,509
Prefix: 10,548,477,557


Simulation 10000:

Range= 0x7783106664cade9ef313deb9c088f05841f3c274a4661258f96e00da053d8d4e:0x7783106664cade9ef313deb9c088f05841f3c274a4661258f96e00da053f13ee

Target= 4f27af87ce608fbb0a02b8c601ec9e8a9e44db86
Checks: Sequential = 66881 | Prefix = 41959

=== FINAL RESULTS ===
Wins:
Sequential: 4085
Prefix: 5484
Ties: 431

[moderator's note: consecutive posts merged]

[zahid888]

Hahaha, take it easy... It’s not that simple... But... Every member in this topic will get 0.2 BTC—if they have a BTC address in their signature. Satisfied? 

Are you talking about that key?

Code:

KyDi5tDzUCEN5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KyDi5tFNbmN45bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KyDi5tJzYm5M5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KzDiBk1GeGqp5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KzDiBk2nLZCk5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KzDiBk377UHr5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
L2Die4KeEMng5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
L3DiBgEqot9K5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob

That’s probably a scam. I’ve bunch of WIFs with partial matches in sequence, be careful not to waste your time there.



For those who think searching for WIF has some magical twist—let me tell you, it's much slower compared to generating an address directly from a private key (hex, bytes or dec).

@nomachine, maybe let the curious minds DM you directly -: this thread’s starting to feel like a rerun marathon. Let’s save the scrolls for fresh stuff!

-- Sim results

If you sum the number of checks over 10k simulations you get this :

Code:

=== FINAL RESULTS ===
Sequential: 495816995
Prefix: 496059807

WHICH IS ALMOST 50-50!

And maybe I have conducted the most experiments on prefixes, whether it be in the form of base58 or hash160.
Through these experiments, I have consistently encountered a 50-50 probability of outcomes.

but the basic aspect has already been demonstrated, which was the probabilistic success rate.

Well done! But let’s be real—if we’re talking probabilities, I Still remember, how you got yourself stuck in this argument when you trying to defend someone. Your heroic moment, huh? Maybe now’s a good time to snap out of that mess and chase some actual probability breakthroughs.

=== Configuration ===
Total numbers: 2,097,152
Block size: 4,096
Prefix: 3 characters (16^3 combinations)
Simulations: 10000

=== FINAL RESULTS ===
Wins:
Sequential: 3736 (Average Win Margin: 42.57%)
Prefix: 6244 (Average Win Margin: 36.55%)
Ties: 20

Total Checks:
Sequential: 10,472,126,509
Prefix: 10,548,477,557

Bro demonstration is over now! lets reduce the talk in this forum that we can easily read important posts And thanks for searching all 10 digit seeds for me 

[nomachine]

Are you talking about that key?

Code:

KyDi5tDzUCEN5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KyDi5tFNbmN45bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KyDi5tJzYm5M5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KzDiBk1GeGqp5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KzDiBk2nLZCk5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KzDiBk377UHr5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
L2Die4KeEMng5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
L3DiBgEqot9K5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob

That’s probably a scam. I’ve bunch of WIFs with partial matches in sequence, be careful not to waste your time there.

It's possible... but I have a match like '1PfNh5' in the address, for example, so I’m not sure what to think. The problem is that the range is huge—larger than life 

[kTimesG]

Your script has a problem. It's running all simulations on the same numbers (1 -> 100000) - You can see that line 17.

Oh no. This was a feature not a bug: "same initial conditions". Did you miss the AI response that clarifies everything?

I'm sorry, but I can only mock you now; your downfall is already too evident.

Let's make a bet, to find out who's right and who's wrong.

If I prove to you that I can find some arbitrary range distribution where the sequential method is better, with your exact code as it is, will you leave the forum forever? If not, I will. How's that for a bet?

Lol,   ,

I guess it was too risky for you?

Anyway, everyone knows you'll return again tomorrow and start again with the prefix probability dementia, like nothing ever happened. It's part of your routine here for a too long time.

[Akito S. M. Hosana]

I have a match like '1PfNh5' in the address, for example

I have up to "1Pf" at the most.  I can imagine how many millions of addresses need to be searched to find a significant match...

[fantom06]

Hahaha, take it easy... It’s not that simple... But... Every member in this topic will get 0.2 BTC—if they have a BTC address in their signature. Satisfied? 

Are you talking about that key?

Code:

KyDi5tDzUCEN5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KyDi5tFNbmN45bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KyDi5tJzYm5M5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KzDiBk1GeGqp5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KzDiBk2nLZCk5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KzDiBk377UHr5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
L2Die4KeEMng5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
L3DiBgEqot9K5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob

That’s probably a scam. I’ve bunch of WIFs with partial matches in sequence, be careful not to waste your time there.



For those who think searching for WIF has some magical twist—let me tell you, it's much slower compared to generating an address directly from a private key (hex, bytes or dec).

@nomachine, maybe let the curious minds DM you directly -: this thread’s starting to feel like a rerun marathon. Let’s save the scrolls for fresh stuff!

-- Sim results

If you sum the number of checks over 10k simulations you get this :

Code:

=== FINAL RESULTS ===
Sequential: 495816995
Prefix: 496059807

WHICH IS ALMOST 50-50!

And maybe I have conducted the most experiments on prefixes, whether it be in the form of base58 or hash160.
Through these experiments, I have consistently encountered a 50-50 probability of outcomes.

but the basic aspect has already been demonstrated, which was the probabilistic success rate.

Well done! But let’s be real—if we’re talking probabilities, I Still remember, how you got yourself stuck in this argument when you trying to defend someone. Your heroic moment, huh? Maybe now’s a good time to snap out of that mess and chase some actual probability breakthroughs.

=== Configuration ===
Total numbers: 2,097,152
Block size: 4,096
Prefix: 3 characters (16^3 combinations)
Simulations: 10000

=== FINAL RESULTS ===
Wins:
Sequential: 3736 (Average Win Margin: 42.57%)
Prefix: 6244 (Average Win Margin: 36.55%)
Ties: 20

Total Checks:
Sequential: 10,472,126,509
Prefix: 10,548,477,557

Bro demonstration is over now! lets reduce the talk in this forum that we can easily read important posts And thanks for searching all 10 digit seeds for me 

I'm always happy to help! Contact me if you have any questions!

[fantom06]

Simulation 100000: Sequential = 47098 | Prefix = 75928

=== FINAL RESULTS ===
Wins:
Sequential: 40727
Prefix: 55067
Ties: 4206

[paulllex]

Hi guys,

In continuation to this thread: https://bitcointalk.org/index.php?topic=1305887.0

While playing around with my bot, I found out this mysterious transaction:

https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15

those 32.896 BTC were sent to multiple addresses, all the private keys of those addresses seem to be generated by some kind of formula.

For example:

Address 2:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU74sHUHy8S
1CUNEBjYrCn2y1SdiUMohaKUi4wpP326Lb
Biginteger PVK value: 3
Hex PVK value: 3

Address 3:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU76rnZwVdz
19ZewH8Kk1PDbSNdJ97FP4EiCjTRaZMZQA
Biginteger PVK value: 7
Hex PVK value: 7

Address 4:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU77MfhviY5
1EhqbyUMvvs7BfL8goY6qcPbD6YKfPqb7e
Biginteger PVK value: 8
Hex PVK value: 8

Address 5:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU7Dq8Au4Pv
1E6NuFjCi27W5zoXg8TRdcSRq84zJeBW3k
Biginteger PVK value: 21
Hex PVK value: 15

Address 6:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU7Tmu6qHxS
1PitScNLyp2HCygzadCh7FveTnfmpPbfp8
Biginteger PVK value: 49
Hex PVK value: 31

Address 7:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU7hDgvu64y
1McVt1vMtCC7yn5b9wgX1833yCcLXzueeC
Biginteger PVK value: 76
Hex PVK value: 4C

Address 8:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU8xvGK1zpm
1M92tSqNmQLYw33fuBvjmeadirh1ysMBxK
Biginteger PVK value: 224
Hex PVK value: E0

Address 9:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUB3vfDKcxZ
1CQFwcjw1dwhtkVWBttNLDtqL7ivBonGPV
Biginteger PVK value: 467
Hex PVK value: 1d3

Address 10:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUBTL67V6dE
1LeBZP5QCwwgXRtmVUvTVrraqPUokyLHqe
Biginteger PVK value: 514
Hex PVK value: 202

Address 11:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUGxXgtm63M
1PgQVLmst3Z314JrQn5TNiys8Hc38TcXJu
Biginteger PVK value: 1155
Hex PVK value: 483

Address 12:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUW5RtS2JN1
1DBaumZxUkM4qMQRt2LVWyFJq5kDtSZQot
Biginteger PVK value: 2683
Hex PVK value: a7b

Address 13:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUspniiQZds
1Pie8JkxBT6MGPz9Nvi3fsPkr2D8q3GBc1
Biginteger PVK value: 5216
Hex PVK value: 1460

Address 14:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFVfZyiN5iEG
1ErZWg5cFCe4Vw5BzgfzB74VNLaXEiEkhk
Biginteger PVK value: 10544
Hex PVK value: 2930

and so on...

until the addresses 50 (1MEzite4ReNuWaL5Ds17ePKt2dCxWEofwk) it was already cracked by someone.

Any ideas what's the formula behind the generation of these addresses?

Address 2, pvk decimal value: 3
Address 3, pvk decimal value: 7
Address 4, pvk decimal value: 8
Address 5, pvk decimal value: 21
Address 6, pvk decimal value: 49
Address 7, pvk decimal value: 76
Address 8, pvk decimal value: 224
Address 9, pvk decimal value: 467
Address 10, pvk decimal value: 514
Address 11, pvk decimal value: 1155
Address 12, pvk decimal value: 2683
Address 13, pvk decimal value: 5216
Address 14, pvk decimal value: 10544
Address 15 and after, pvk decimal value: ?

The prize would be ~32 BTC

EDIT: If you find the solution feel free to leave a tip 1DPUhjHvd2K4ZkycVHEJiN6wba79j5V1u3

It is impossible to deduce the private key from the address, that is what the Bitcoin white paper is about, that the possibility of doing that is almost zero, however, could Satoshi have left another route? Maybe he knew perfectly well that it was impossible so he kept his Bitcoin in a place where it is possible to enter knowing certain clues and that is also in the white paper, any ideas, about the vault??? satoshin@gmx.com