Post
Topic
Board Bitcoin Discussion
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
by
lmajowka
on 19/07/2024, 13:16:51 UTC

Pub:  0x02DC28EF701BB67EB35C759CCA511CD522A598EDAC322FD073A2C0A0BD4CC8C910
Priv:  0x3CB359F64B27EF00

But why you are giving wrong range its not 66 bit its 62 bit.. lets try another Cheesy


Orig TX     https://www.blockchain.com/explorer/transactions/btc/2ee4f5155390a888a22b1417d35bd9023a1005b171b97615f4532d207e581c24
New TX     https://www.blockchain.com/explorer/transactions/btc/098fec25954faad5571bb81234658228c888cd428a2531538ed1d40e278af9e3


Orig Fee  : 0.00001786 BTC
New Fee  : 0.00003764 BTC

ADDRESS:      1DWQHdi1mh27vcUyrN5NYB1kWrs3BBKUXA

No one seems to have taken his BTC



INFO.log

INFO:root:Fri Jul 19 06:22:18 2024
INFO:root:Extracted Public Key: 025b2fb64f70afceded779f874ce13407698e406037e0bcd406c1ecec9d1d92880
  • Version 0.2.230519 Satoshi Quest, developed by AlbertoBSD
  • Quiet thread output
  • Stats output every 10 seconds
  • Threads : 128
  • K factor 4096
  • Mode BSGS sequential
  • Opening file 66.txt
  • Added 1 points from file
  • Bit Range 66
  • -- from : 0x20000000000000000
  • -- to   : 0x40000000000000000
  • N = 0x100000000000
  • Bloom filter for 17179869184 elements : 58890.60 MB
  • Bloom filter for 536870912 elements : 1840.33 MB
  • Bloom filter for 16777216 elements : 57.51 MB
  • Allocating 256.00 MB for 16777216 bP Points
  • Reading bloom filter from file keyhunt_bsgs_4_17179869184.blm .... Done!
  • Reading bloom filter from file keyhunt_bsgs_6_536870912.blm .... Done!
  • Reading bP Table from file keyhunt_bsgs_2_16777216.tbl .... Done!
  • Reading bloom filter from file keyhunt_bsgs_7_16777216.blm .... Done!
End


That man is clown...Another address that is not in the range of 66...

I am the creator. No,, not god man. I am the creator of this puzzle! I apologize, I had a bug in my script that generates WIF and ADDRESS so I was 100% sure it was using a 66 bits key but in fact it was using 62 Sad. Well the money is still with me, so bug have been fixed, we will try again Tomorrow