Hey everyone,
Continuing from this thread: https://this forum/topic/1305887
While messing around with my bot, I stumbled upon this intriguing transaction:
https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15
So, there’s around 32.896 BTC that were sent to various addresses, and it looks like the private keys for these addresses were generated using some sort of formula.
Check this out:
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:
KwDiBf89QgGbjEhKnhXJuH7L
Solving a Bitcoin puzzle transaction with ~32 BTC reward
19 replies 90 views
As BurtW also pointed out the transaction values increase from from 0.001 to 0.256, according to the address position.
here are the other pvk decimal values I was able to find:
Address 15: 26867
Address 16: 51510
Address 17: 95823
Address 18: 198669
Address 19: 357535
Address 20: ?
I don't know why but I'm smelling a big scam. Because a newbie that offer more than 12 000 to solve a following of numbers this is strange...
wallet2018Member
Posts: 53 · Reputation: 235
#4May 20, 2023, 12:57 AM
Any info on who published this puzzle and what's their goal? Also, how would one go on about calculating those pvk decimal values and covert them to the private keys?
The OP is not offering anything
More details of the new values, including pvks and publics
Address 15:
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFY5iMZbuRxj
1QCbW9HWnwQWiQqVo5exhAnmfqKRrCRsvW
pvk decimal value: 26867
pvk hex value: 68F3
Address 16:
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFbjHrFMWzJp
1BDyrQ6WoF8VN3g9SAS1iKZcPzFfnDVieY
pvk decimal value: 51510
pvk hex value: C936
Address 17:
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFiHkRsp99uC
1HduPEXZRdG26SUT5Yk83mLkPyjnZuJ7Bm
pvk decimal value: 95823
pvk hex value: 1764F
Address 18:
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFyWkjT5fywW
1GnNTmTVLZiqQfLbAdp9DVdicEnB5GoERE
pvk decimal value: 198669
pvk hex value: 3080D
Address 19:
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rGP2jMrxCfX3
1NWmZRpHH4XSPwsW6dsS3nrNWfL1yrJj4w
pvk decimal value: 357535
pvk hex value: 5749F
Oh, in that case I'm sorry. I thought it was him who was offering this. So who's offering it ?
I have no idea about who created this transactions, I was just playing around with the bot and stumbled upon it.
After reviewing a bunch of pvks found by the bot I noticed that many of the addresses were on the same transaction, after checking closely I found those kind of sequence patterns.
Looks tempting to crack
One thing I noticed:
The first address in the transaction is tagged on blockchain.info with "1st Bitcoin Address Compressed".
So probably this transaction was done by the Bitcoin devs? or even... satoshi?
looks really easy to crack
why would reward be so high
The transactions seem to originate from address 173ujrhEVGqaZvPHXLqwXiSmPVMo225cqT which had a Total received amount of 56,457.80848111 BTC and a Final Balance of 312.04932734 BTC
Definitely a very big player of some kind.
Well spotted.
Also it looks active, there are daily transactions there.
Probably some exchange?
It's not easy, trust me.
But go ahead, maybe you can crack it.
wallet2018Member
Posts: 53 · Reputation: 235
#12May 21, 2023, 04:37 AM
It does, but I still haven't understand the method/how does one go to attempt and find the solution to the puzzle
This hardly has anything to to with any of them.
Suggestions are always welcome.
I see a pattern but I do not think it will help much.
My conjecture is that the sequence number (the BTC amount) simply states the number of random bits in the private key.
Check it out:
The 0.001 BTC output used a 1 bit key (already claimed obviously)
The 0.002 BTC output used a 2 bit key
The 0.003 BTC output used a 3 bit key
etc...
The 0.019 BTC output used a 19 bit key
So I would claim the next unclaimed output uses a 51 bit key.
The brute force way: Start @ ~607809 (multiplied the last known value by 1.7) convert to hex, create addresses, check if one address matches the next in turn.
BEFORE you comment on this thread
1) Carefully READ the thread
2) Think
Then please comment.
We don't need any off topic comments unrelated to the puzzle at hand.
So, there is no pattern? Its just getting more and more difficult to find a solution? Might be time to get something written for GPUs.
wallet2018Member
Posts: 53 · Reputation: 235
#17May 23, 2023, 07:33 AM
What would be the best tool to attack this in a brute force way while we all think on something better or discover a easier way?
Some GPU bot would be the best to brute force it, like shorena was saying.
Need to code one, but I'm not in the mood now
Anyone out there doing it? Or maybe there is something existing?
wallet2018Member
Posts: 53 · Reputation: 235
#19May 25, 2023, 12:42 AM
That was the aim of my post, such a tool probably already exists.
I think the best existing tool currently is yours or otherwise private. I would think the best way would be to modify (ocl)vanitygen according to BurtW's suggestion. You would need to limit the random number generator to a certain amount of bits and keep the rest.