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

Because all the funds from 161 through 255 were redundant (Bitcoin addresses only use 160 bits) the author of the puzzle moved all the funds from the 160-255 ranged down into the 1-160 range.  It is explained up thread.

65 000000000000000000000000000000000000000000000001a838b13505b26867 18ZMbwUFLMHoZBbfpCjUJQTCMCbktshgpe 

It's done. Bch cashed too. I did'nt have enough RAM to get to  the key  from the tx signature ....

By the way, and you know why their puzzle addresses were removed from the 161st?
My thought is that this is the limit of public addresses. That is the further search in the theory goes on a circle.

If the owner needed the funds, he would spend them, and so they were transferred to a null multi-address address and hung there.

Cheater

            the most interesting thing is that the cache is not touched ,which means that it is not found the key ,and the owner came and took it.  https://www.blockchain.com/ru/bch/address/18ZMbwUFLMHoZBbfpCjUJQTCMCbktshgpe 

I agree. difficulty 2^61
the gpu that eats 150 watts and gives 150Mkey/s  to go through all the keys 2^61 eats 640000 kilowatt = 19000$(cost 0.03$/kWh)-64000$(0.1$/kWh )

01 0000000000000000000000000000000000000000000000000000000000000001 1BgGZ9tcN4rm9KBzDn7KprQz87SZ26SAMH
02 0000000000000000000000000000000000000000000000000000000000000003 1CUNEBjYrCn2y1SdiUMohaKUi4wpP326Lb
03 0000000000000000000000000000000000000000000000000000000000000007 19ZewH8Kk1PDbSNdJ97FP4EiCjTRaZMZQA
04 0000000000000000000000000000000000000000000000000000000000000008 1EhqbyUMvvs7BfL8goY6qcPbD6YKfPqb7e
05 0000000000000000000000000000000000000000000000000000000000000015 1E6NuFjCi27W5zoXg8TRdcSRq84zJeBW3k
06 0000000000000000000000000000000000000000000000000000000000000031 1PitScNLyp2HCygzadCh7FveTnfmpPbfp8
07 000000000000000000000000000000000000000000000000000000000000004c 1McVt1vMtCC7yn5b9wgX1833yCcLXzueeC
08 00000000000000000000000000000000000000000000000000000000000000e0 1M92tSqNmQLYw33fuBvjmeadirh1ysMBxK
09 00000000000000000000000000000000000000000000000000000000000001d3 1CQFwcjw1dwhtkVWBttNLDtqL7ivBonGPV
10 0000000000000000000000000000000000000000000000000000000000000202 1LeBZP5QCwwgXRtmVUvTVrraqPUokyLHqe
11 0000000000000000000000000000000000000000000000000000000000000483 1PgQVLmst3Z314JrQn5TNiys8Hc38TcXJu
12 0000000000000000000000000000000000000000000000000000000000000a7b 1DBaumZxUkM4qMQRt2LVWyFJq5kDtSZQot
13 0000000000000000000000000000000000000000000000000000000000001460 1Pie8JkxBT6MGPz9Nvi3fsPkr2D8q3GBc1
14 0000000000000000000000000000000000000000000000000000000000002930 1ErZWg5cFCe4Vw5BzgfzB74VNLaXEiEkhk
15 00000000000000000000000000000000000000000000000000000000000068f3 1QCbW9HWnwQWiQqVo5exhAnmfqKRrCRsvW
16 000000000000000000000000000000000000000000000000000000000000c936 1BDyrQ6WoF8VN3g9SAS1iKZcPzFfnDVieY
17 000000000000000000000000000000000000000000000000000000000001764f 1HduPEXZRdG26SUT5Yk83mLkPyjnZuJ7Bm
18 000000000000000000000000000000000000000000000000000000000003080d 1GnNTmTVLZiqQfLbAdp9DVdicEnB5GoERE
19 000000000000000000000000000000000000000000000000000000000005749f 1NWmZRpHH4XSPwsW6dsS3nrNWfL1yrJj4w
20 00000000000000000000000000000000000000000000000000000000000d2c55 1HsMJxNiV7TLxmoF6uJNkydxPFDog4NQum
21 00000000000000000000000000000000000000000000000000000000001ba534 14oFNXucftsHiUMY8uctg6N487riuyXs4h
22 00000000000000000000000000000000000000000000000000000000002de40f 1CfZWK1QTQE3eS9qn61dQjV89KDjZzfNcv
23 0000000000000000000000000000000000000000000000000000000000556e52 1L2GM8eE7mJWLdo3HZS6su1832NX2txaac
24 0000000000000000000000000000000000000000000000000000000000dc2a04 1rSnXMr63jdCuegJFuidJqWxUPV7AtUf7
25 0000000000000000000000000000000000000000000000000000000001fa5ee5 15JhYXn6Mx3oF4Y7PcTAv2wVVAuCFFQNiP
26 000000000000000000000000000000000000000000000000000000000340326e 1JVnST957hGztonaWK6FougdtjxzHzRMMg
27 0000000000000000000000000000000000000000000000000000000006ac3875 128z5d7nN7PkCuX5qoA4Ys6pmxUYnEy86k
28 000000000000000000000000000000000000000000000000000000000d916ce8 12jbtzBb54r97TCwW3G1gCFoumpckRAPdY
29 0000000000000000000000000000000000000000000000000000000017e2551e 19EEC52krRUK1RkUAEZmQdjTyHT7Gp1TYT
30 000000000000000000000000000000000000000000000000000000003d94cd64 1LHtnpd8nU5VHEMkG2TMYYNUjjLc992bps
31 000000000000000000000000000000000000000000000000000000007d4fe747 1LhE6sCTuGae42Axu1L1ZB7L96yi9irEBE
32 00000000000000000000000000000000000000000000000000000000b862a62e 1FRoHA9xewq7DjrZ1psWJVeTer8gHRqEvR
33 00000000000000000000000000000000000000000000000000000001a96ca8d8 187swFMjz1G54ycVU56B7jZFHFTNVQFDiu
34 000000000000000000000000000000000000000000000000000000034a65911d 1PWABE7oUahG2AFFQhhvViQovnCr4rEv7Q
35 00000000000000000000000000000000000000000000000000000004aed21170 1PWCx5fovoEaoBowAvF5k91m2Xat9bMgwb
36 00000000000000000000000000000000000000000000000000000009de820a7c 1Be2UF9NLfyLFbtm3TCbmuocc9N1Kduci1
37 0000000000000000000000000000000000000000000000000000001757756a93 14iXhn8bGajVWegZHJ18vJLHhntcpL4dex
38 00000000000000000000000000000000000000000000000000000022382facd0 1HBtApAFA9B2YZw3G2YKSMCtb3dVnjuNe2
39 0000000000000000000000000000000000000000000000000000004b5f8303e9 122AJhKLEfkFBaGAd84pLp1kfE7xK3GdT8
40 000000000000000000000000000000000000000000000000000000e9ae4933d6 1EeAxcprB2PpCnr34VfZdFrkUWuxyiNEFv
41 00000000000000000000000000000000000000000000000000000153869acc5b 1L5sU9qvJeuwQUdt4y1eiLmquFxKjtHr3E
42 000000000000000000000000000000000000000000000000000002a221c58d8f 1E32GPWgDyeyQac4aJxm9HVoLrrEYPnM4N
43 000000000000000000000000000000000000000000000000000006bd3b27c591 1PiFuqGpG8yGM5v6rNHWS3TjsG6awgEGA1
44 00000000000000000000000000000000000000000000000000000e02b35a358f 1CkR2uS7LmFwc3T2jV8C1BhWb5mQaoxedF
45 0000000000000000000000000000000000000000000000000000122fca143c05  1NtiLNGegHWE3Mp9g2JPkgx6wUg4TW7bbk
46 00000000000000000000000000000000000000000000000000002ec18388d544 1F3JRMWudBaj48EhwcHDdpeuy2jwACNxjP
47 00000000000000000000000000000000000000000000000000006cd610b53cba 1Pd8VvT49sHKsmqrQiP61RsVwmXCZ6ay7Z
48 0000000000000000000000000000000000000000000000000000ade6d7ce3b9b 1DFYhaB2J9q1LLZJWKTnscPWos9VBqDHzv
49 000000000000000000000000000000000000000000000000000174176b015f4d 12CiUhYVTTH33w3SPUBqcpMoqnApAV4WCF
50 00000000000000000000000000000000000000000000000000022bd43c2e9354 1MEzite4ReNuWaL5Ds17ePKt2dCxWEofwk
51 00000000000000000000000000000000000000000000000000075070a1a009d4 1NpnQyZ7x24ud82b7WiRNvPm6N8bqGQnaS
52 000000000000000000000000000000000000000000000000000efae164cb9e3c  15z9c9sVpu6fwNiK7dMAFgMYSK4GqsGZim
53 00000000000000000000000000000000000000000000000000180788e47e326c 15K1YKJMiJ4fpesTVUcByoz334rHmknxmT
54 00000000000000000000000000000000000000000000000000236fb6d5ad1f43  1KYUv7nSvXx4642TKeuC2SNdTk326uUpFy
55 000000000000000000000000000000000000000000000000006abe1f9b67e114 1LzhS3k3e9Ub8i2W1V8xQFdB8n2MYCHPCa
56 000000000000000000000000000000000000000000000000009d18b63ac4ffdf   17aPYR1m6pVAacXg1PTDDU7XafvK1dxvhi
57 00000000000000000000000000000000000000000000000001eb25c90795d61c 15c9mPGLku1HuW9LRtBf4jcHVpBUt8txKz
58 00000000000000000000000000000000000000000000000002c675b852189a21 1Dn8NF8qDyyfHMktmuoQLGyjWmZXgvosXf
59 00000000000000000000000000000000000000000000000007496cbb87cab44f  1HAX2n9Uruu9YDt4cqRgYcvtGvZj1rbUyt
60 0000000000000000000000000000000000000000000000000fc07a1825367bbe  1Kn5h2qpgw9mWE5jKpk8PP4qvvJ1QVy8su
61 00000000000000000000000000000000000000000000000013C96A3742F64906 1AVJKwzs9AskraJLGHAZPiaZcrpDr1U6AB

PoB (Paradox of Birthdays)
PoB as an average prvkey distribution (if believe the statistics), the next time (#62) it should not work.
That is, if #61 it was necessary to search in 30% already win, then now the opposite is true - in 60% never win.
And big problem is that it is not stable.
If you were waiting for the moment know it(#61) was
PoB as recurring characters more stable, it + ~50%.

But, see simple calculation
#55 had a ~50% profitability (use VanityGen) compared to the complexity of mining (end 2018, excluding electricity costs).
(if the seeker is unlucky, and he goes through the whole range and finds the key at the end - he will still receive ~50% of the profit, compared to the mining)
#58 had a ~50% profitability (use BitCrack) compared to the complexity of mining.
#59 had a ~50% profitability (use BitCrack) compared to the complexity of mining only if seeker is lucky and 0% if unlucky.
Suppose that BitCrack can work another 2x faster (in theoretically limit), according to information from this and other topics.
Than #60 - last puzzle, where profit was possible (in theory).
Conclusion - the puzzle is no longer profitable! (only if the author increases the award or mining will not be profitable by 4x+more)
Solve the puzzles for fame? Ok, why not?..
But having opened the blockchain, I don’t see any glory from #58, except for the simple draining of the address

They will not go for it. Because need to add BitCrack as a new algorithm and enter the payment rate. There are lots of programs to calculate, but they do not add them. I think they are simply not profitable. It's sad, because this project that has a great opportunity to consider not useless PoW, but something real.
What about Amazon? 4x-10x expensive vs mining.
What about FPGA? 10x expensive vs gpu, but how many X speedup? (some info 10x, gpus equal, but electricity costs 10x profit)

I see several people are pointing their GPUs at this
you can try and buy hashpower from nicehash , for example , or organize a syndicate
I'm extremely skeptical about the whole idea , but this seems like the right way to do it
otherwise it will take what , 100 years to solve ?

Wow, so you found 61st key after so many years

But what are the total addresses to reach the prize? And do you have a guess for when will that achieve?

O.K.   
To do to me it on my supercomputer it is possible also successfully how to try to spit up to the moon

My comment about you stealing my Bitcoins was a joke.  You can't steal them for the mathematical reasons I gave.

The only way to get the next prize is to brute force search the range of the prize.

You are correct that other people with much faster hardware will probably beat you to the prize.

There has been a lot of effort on this thread where people try to "calculate" (in other words guess) the expected sub-range withing the next prize range.

You could search their guess at the expected sub-range but again without faster hardware you will probably not win the next prize.

You could try to search randomly in the next range (or their guess at the expected sub-range).  You will probably still lose but hey, you just might get lucky.

I in a shock!!! On this forum it is possible to set questions? Or each man, who has set a question - thief and hacker?
You seriously think, what I such terrible hacker and my purpose in life - " Is that what you are thinking of doing? Stealing my Bitcoins? "
Any thief or hacker on this forum will not set questions - he simply were silent will make it!
Well it is simple a deviation(rejection) from a theme.
***
And now as a matter of fact of question.

Page 44 a post * 863
following here is
1Me6EfpwZK5kQziBwBfvLiHjaPGxCKLoJi
search range in hexadecimal
2000000000000000 to 4000000000000000
good luck

I understand so, that this address 1Me6EfpwZK5kQziBwBfvLiHjaPGxCKLoJi the man " has given back for all " as a prize.
Who can first find private key - that has the right to take away to itself BTC from this address.

It is possible to do(make) search private key different software, but I can use only clBitCrack (mine laptop - AMD)
For search private key software clBitCrack should process - keyspace in hexadecimal
from 2000000000000000 to 4000000000000000.
The maximal speed of search, which can apply mine laptop - AMD turns out 0.63 MKey/s
At such " of fantastic speed " after two day (for 48 hours) mine laptop - AMD has scanned "huge" quantity(amount) of variants - 19254d3801
If I shall continue search, mine laptop - AMD should work in a mode 24/7 more than 10 years!!!
How I can compete to other people, at which powerful computers and these computers reach(achieve) speeds 135 MKey/s - 850 MKey/s???!!!

Therefore I am compelled to search for other method.

I think you are asking "How do I calculate the private key from the public key?"

It is easy to calculate the public key from the private key.  The formula is PublicKey = PrivateKey * G where G is a specific point on the specified elliptic curve and * is the scalar multiplication defined over the finite group of the elliptic curve.

For all practical purposes it is impossible to calculate or even estimate the private key from the public key because there is no "division operation" defined for the group.

That is what makes Bitcoin work.

If you could calculate or even estimate the private key from the public key then anyone could calculate anyone's private key from their public key and anyone could steal anyone's Bitcoins.  Is that what you are thinking of doing?  Stealing my Bitcoins?  

If anyone ever figures out how to calculate or estimate the private key from the public key then Bitcoin and a plethora of other system worldwide would all be catastrophically broken.

I have no idea what you are asking.  What do you mean by "location"?
[/quote]

All space the private key in hexadecimal is located  - keyspace:
FROM - 0000000000000000000000000000000000000000000000000000000000000001:
TO - FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

To each position belongs two address: one - "ucompressed"; second - "compressed"

So, for example first position 0000000000000000000000000000000000000000000000000000000000000001 posesses two addresses
"ucompressed" - 1EHNa6Q4Jz2uvNExL497mE43ikXhwF6kZm
"compressed" - 1BgGZ9tcN4rm9KBzDn7KprQz87SZ26SAMH

And last position FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF posesses other two addresses

"ucompressed" - 12M4QznuNZH2BRVbLK8SKvNqGTPJpCpST7
"compressed" - 1PRWyFKTsQSJaUdX9VKgQNw8JERPw2kMFm

All other addresses are in space
FROM - 0000000000000000000000000000000000000000000000000000000000000001:
TO - FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

FOR EXAMPLE: what method it is possible to calculate the private key in hexadecimal keyspace for addresses 1HBtApAFA9B2YZw3G2YKSMCtb3dVnjuNe2
I know, that he is on a position 00000000000000000000000000000000000000000000000000000022382facd0
I have learned(found out) it casually from an open source.
But me interests as it is possible to calculate this position and with what minimal error (i.e. with the maximal accuracy).

All these addresses are taken casually only for an example

I have no idea what you are asking.  What do you mean by "location"?

Hi BurtW!

Can someone prompt as it is possible calculate location of the private key in hexadecimal (- keyspace FROM:TO)?

Possible write in P.M.