Bitcoin puzzle transaction ~32 BTC prize to who solves it

[citb0in]

it should be cool if the puzzle 66 will be in the halving block

The money for puzzle number 65 is at this address : 3GVSoQar7WnVMFjchpkNkh9UwkJbbdeCwM

Interesting even that it was moved in 2019 it still untouched

2019-06-08 00:39:02   BTC address:  3GVSoQar7WnVMFjchpkNkh9UwkJbbdeCwM

I think the person who solved #65 is very rich or has no interest in Bitcoin ...

 

HODL'ing

[Airfin Same]

it should be cool if the puzzle 66 will be in the halving block

The money for puzzle number 65 is at this address : 3GVSoQar7WnVMFjchpkNkh9UwkJbbdeCwM

Interesting even that it was moved in 2019 it still untouched

2019-06-08 00:39:02   BTC address:  3GVSoQar7WnVMFjchpkNkh9UwkJbbdeCwM

I think the person who solved #65 is very rich or has no interest in Bitcoin ...

 

HODL'ing

Bitcoin Cash here
https://www.blockchain.com/explorer/addresses/BCH/qz5q3kl2hlsgwadl7u8dzu9278k05kxs8s8p3raj3k

maybe the creator move them

[albert0bsd]

maybe the creator move them

like this or more retarded

The author doesn't have that necessity.

There are remainin 956.5 BTC in those puzzles near 61 Million USD at todays price on those puzzles if the author is driven by greed what stop him to take those ?

[nomachine]

what do you mean payout!

can you give me answer here, thank you

It means that he has a private key or knows someone who does. And that he is large miner who will include that transaction in the next block to be calculated.

In other words, the bots are screwed. 

[AliBah]

it should be cool if the puzzle 66 will be in the halving block

The money for puzzle number 65 is at this address : 3GVSoQar7WnVMFjchpkNkh9UwkJbbdeCwM

Interesting even that it was moved in 2019 it still untouched

2019-06-08 00:39:02   BTC address:  3GVSoQar7WnVMFjchpkNkh9UwkJbbdeCwM

I think the person who solved #65 is very rich or has no interest in Bitcoin ...

 

Or maybe he lost his private key hahaha

[wejiv15]

By which program you cracked that? and how to find thats in what range?

I use keyhunt the program that i develop:

https://bitcointalk.org/index.php?topic=5322040.0
https://github.com/albertobsd/keyhunt

But other programs can also be used like Kangaroo

https://github.com/JeanLucPons/Kangaroo

There is no way to know the range of an address.

But since we are talking here of puzzle 66 i did the test in the bit 66 just to check if that address was in that range, and actually the key is of that address is in that range!!

Other address besides of low bit puzzles aren't vulnerable to this.

As soon as the person who finds puzzle 66 sends the transaction to the network, pubkey will appear without requiring network approval. Once Pubkey appears it will take 1 second to find the private key. Then, someone else will spend again because the network approval has not yet occurred. The person with the highest network approval will own the bitcoins. Even if you send with a high transaction fee, the person who receives a higher transaction fee and network approval than you will win. For this reason, Low puzzles are problematic.

Exactly all the non-confirmed transacctions are public avaible in the mempool of each node.

Also there is sites to check them https://mempool.space/ also they offer some api to check for some values

https://mempool.space/docs/api/rest#get-address-transactions-mempool

Once that you get the TX id, you need to download the Raw transaction, decode it and extract the publickey and that is easy to do if you know what are you doing.

If find the Pkey by pubkey is so easy like this, then why puzzle 130 didnt solve yet?

Well for puzzle  66 is really easy (some minutes/seconds) but since the complexity is exponential it will take a lot of time do that for those bits ranges, months or years depending of hardware.

Here we are talking of low bit puzzles less than 80 bits are solvables by GPU almost in less than 10 minutes (in avarage the time needed to mine a block)

Hey Alberto, I want to know how to get private key for non-confirmed transactions if we get the Uncompressed Public key from the https://mempool.space/ Raw Txns, i decoded the public key but it was uncompressed public key and if we can't calculate private key from uncompressed public key how to mine the transaction??. Please reply asap.

[albert0bsd]

Please reply asap.

We only can know the  private key of the puzzles that are expected to be on low bit ranges. The method is that I already expose and you quoted if you don't know how to read is not my problem

[brainless]

Anyone have seen or experience with Bitcrack / fork for load starting points by file ?

[WanderingPhilospher]

Anyone have seen or experience with Bitcrack / fork for load starting points by file ?

Not sure what you are exactly wanting, but the easiest way is to create a Python script to feed the program starting ranges, and to keep track of said starting ranges. Not sure if starting ranges = starting points, but that is what I would do.

[brainless]

Anyone have seen or experience with Bitcrack / fork for load starting points by file ?

Not sure what you are exactly wanting, but the easiest way is to create a Python script to feed the program starting ranges, and to keep track of said starting ranges. Not sure if starting ranges = starting points, but that is what I would do.

Yes starting ranges by default is sequel,
One an other forked Bitcrack today I see in my system, where generated random starting points, onword it's start from each generated point to series
Thinking if we load by file starting points, then maybe betterment,
By python we can assign single starting point for go on, but only when we need to search in trillions keys
And start/stop action waste time for small ranges for million etc

Anyone have seen or experience with Bitcrack / fork for load starting points by file ?

Yes starting ranges by default is sequel,
One an other forked Bitcrack today I see in my system, where generated random starting points, onword it's start from each generated point to series
Thinking if we load by file starting points, then maybe betterment,
By python we can assign single starting point for go on, but only when we need to search in trillions keys
And start/stop action waste time for small ranges for million etc

Not sure what you are exactly wanting, but the easiest way is to create a Python script to feed the program starting ranges, and to keep track of said starting ranges. Not sure if starting ranges = starting points, but that is what I would do.

just see its forked name
url = https://github.com/pikachunakapika/BitCrack.git

pikachunakapika
its uses random ver

 [Info] Initializing GeForce GTX 460
 [Info] Generating 4,143,104 starting points (158.0MB)

these generating point could be load by file ?

ReadMe note
-r, --random    Each point will start in random KEYSPACE

[k3ntINA]

I removed the space between the private keys.
See how the first 4 digits of the private key are known?
Now guess 66!

https://www.talkimg.com/images/2024/04/23/jWRcT.gif

[albert0bsd]

I removed the space between the private keys.
See how the first 4 digits of the private key are known?
Now guess 66!

Bullshit

[supika]

I removed the space between the private keys.
See how the first 4 digits of the private key are known?
Now guess 66!

https://www.talkimg.com/images/2024/04/23/jWRcT.gif

So the private key is starting with 37 in hex?

[citb0in]

I removed the space between the private keys.
See how the first 4 digits of the private key are known?
Now guess 66!

So the private key is starting with 37 in hex?

Nope. It's starting with 34

[albert0bsd]

Nope. It's starting with 34

TBH this is also BS, There is no way to know that unless you already solved it.

[citb0in]

Alberto, of course it was BS. That's the point, just emphasizing it  

[nomachine]

Nope. It's starting with 34

And the public key starts with 03?   

[citb0in]

No, 05 because of its special compression level 

[albert0bsd]

Alberto, of course it was BS. That's the point, just emphasizing it  

Nice to know, in this kind of comment I am bad getting the sarcarm of it

[WanderingPhilospher]

I removed the space between the private keys.
See how the first 4 digits of the private key are known?
Now guess 66!

What is this sorcery?!