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

1e+12  is just 10**12   same as 1 000 000 000 000   (twelve zeros) 
1 BTC = 1e+8 satoshi = 100 000 000   (eight zeros)
so
1e+12 = 10 000 BTC

this wallet 183hmJGRuTEi2YDCWy5iozY8rZtFwVgahM holds 8.59473e+12 = 85 947 BTC
This wallet has no withdrawal.
it was created on this date 2018-07-01 and received all this amount from 1KAt6STtisWMMVo5XGdos9P7DBNNsFfjx7

hi!!

 Prism switches to scientific notation when the values are very larger or very small. For example:

2.3e-5, means 2.3 times ten to the minus five power, or 0.000023
4.5e6 means 4.5 times ten to the sixth power, or 4500000 which is the same as 4,500,000
This is a standard notation used by many computer programs including Excel. Entering a value in this form is not the same as entering the logarithm of a number. This is simply a shortcut way to enter very large values, or tiny fractions, without using logarithms

Note that in other contexts, e = 2.71828183, the base of natural logarithms. But when used in displaying large or small numbers, e means "times ten to the power of...".

That one must be an exchange cold wallet. Transaction happened within the last 12 months also. I bet it's Coinbase. Or Bitfinex.
 
Btw
 

not familiar with these kind of numbers that begin with "e", what does it mean?
I'm stupid I know. I'm also not very good at math. Would be happy to have explained why you wrote those "e"-numbers behind the addresses. Thanks!

edit I just went through the BTC Top 100 Rich list and found some that had over 1million BTC transacted. That's heavy.
Also sorry for pushing this thread slightly Off Topic.

check those if they still have their BTC
16rCmCmbuWDhPjWTrpQGaU3EPdZF7MTdUk;1.07203e+13
183hmJGRuTEi2YDCWy5iozY8rZtFwVgahM;8.59473e+12
1FeexV6bAHb8ybZjqQMjJrcCrHGW9sb6uF;7.99572e+12
1HQ3Go3ggs8pFnXuHVHRytPCq5fGG8Hbhx;6.93701e+12
18rnfoQgGo1HqvVQaAN4QnxjYE7Sez9eca;6.36e+12
1LdRcdxfbSnmCYYNdeYpUnztiYzVfBEQeC;5.38801e+12
1JCe8z4jJVNXSjohjM4i9Hh813dLCNx2Sy;5.3e+12
1AC4fMwgY8j9onSbXEWeH6Zan8QGMSdmtA;5.18304e+12
12YygZpCEC8VED2oSMQdWCq5xBnHo9ts1Z;4.85001e+12
18mkjbVaHAcMauL6iiy7zm9VjMYCjy4UU1;4.5e+12
17hf5H8D6Yc4B7zHEg3orAtKn7Jhme7Adx;3.6e+12
13JQwoSLLR3ffXwswe2HCTK9oq4i8MWK3q;3.101e+12
12ib7dApVFvg82TXKycWBNpN8kFyiAN1dr;3.10001e+12
12tkqA9xSoowkzoERHMWNKsTey55YEBqkv;2.81511e+12
1AnwDVbwsLBVwRfqN2x9Eo4YEJSPXo2cwG;2.32276e+12
14eQD1QQb8QFVG8YFwGz7skyzsvBLWLwJS;2.22112e+12
16FSBGvQfy4K8dYvPPWWpmzgKM6CvrCoVy;2.16986e+12
17rm2dvb439dZqyMe2d4D6AQJSgg6yeNRn;2.0008e+12
1Cr7EjvS8C7gfarREHCvFhd9gT3r46pfLb;1.95169e+12
1PeizMg76Cf96nUQrYg8xuoZWLQozU5zGW;1.94144e+12
18x5Wo3FLQN4t1DLZgV2MoAMWXmCYL9b7M;1.62524e+12
1GR9qNz7zgtaW5HwwVpEJWMnGWhsbsieCG;1.57456e+12
1FaUfrUhv37aqFAZ9ij595587wtnGWBFKS;1.5724e+12
1HLsDiYE8P61Z3mwqVuq1xtuoZkJZ8rX7P;1.5e+12
1DWsHCjeekCe3tRzMuJktHhFrtLQDeodcP;1.5e+12
1PfceCKGraSPEvx6nfjw5ZCLLy8Ct23Qd5;1.49999e+12
15xZvLJLAgxh8cxEmAbpx1H35oibHo5cLA;1.44498e+12
1BZaYtmXka1y3Byi2yvXCDG92Tjz7ecwYj;1.4e+12
1GKztam9D8ZWK9GxsNoNZbVSVs9Pk1nAXp;1.30001e+12
1KKiEAkpnQR2FH5kpkGP6442ZDkd6ZdrRS;1.28e+12
18hRPy5sTzoYAfX18qn8eK1SdwbxU3YHpD;1.2322e+12
1HBM45n214sV9yXoizBwTksUgEysTPpk46;1.20003e+12
13sixi6TGPoWvbi2e93wdQSyJPPN7vNhx3;1.19272e+12
1CMbVZV7xbAiFFauuAf3tgZRhwLKXmMUZL;1.1837e+12
15NQthxeLSwMtEaXJFM7YUCf59LzmFjkeH;1.18e+12
1aXzEKiDJKzkPxTZy9zGc3y1nCDwDPub2;1.15e+12
1DWxysF7GPRYGShNxL5ux2N2JLRa9rbE6k;1.13891e+12
1923qxU74HWWz75LgWTsPE4FT9Zyd6n6bv;1.13368e+12
19G5kkYvjawZiYKhFeh8WmfBN31pdP94Jr;1.1102e+12
1F34duy2eeMz5mSrvFepVzy7Y1rBsnAyWC;1.07705e+12
1f1miYFQWTzdLiCBxtHHnNiW7WAWPUccr;1.00093e+12
187Nqgq3WoKihPNMtWYfRe6z2CFUJhbgFh;1.00017e+12
1ucXXZQSEf4zny2HRwAQKtVpkLPTUKRtt;1e+12
1P1iThxBH542Gmk1kZNXyji4E4iwpvSbrt;1e+12
1LfV1tSt3KNyHpFJnAzrqsLFdeD2EvU1MK;1e+12
1Kx4QFupZ9vKFmUDhsptfSBPEKXJKV5MuN;1e+12
1Ki3WTEEqTLPNsN5cGTsMkL2sJ4m5mdCXT;1e+12
1KbrSKrT3GeEruTuuYYUSQ35JwKbrAWJYm;1e+12
1EU2pMence1UfifCco2UHJCdoqorAtpT7;1e+12
1CPaziTqeEixPoSFtJxu74uDGbpEAotZom;1e+12
1BAFWQhH9pNkz3mZDQ1tWrtKkSHVCkc3fV;1e+12
14YK4mzJGo5NKkNnmVJeuEAQftLt795Gec;1e+12
12tLs9c9RsALt4ockxa1hB4iTCTSmxj2me;1e+12
1DBwffK5gAsL7axG6idGFRXNWMxuUZTcE5;9.73011e+11
1Kd6zLb9iAjcrgq8HzWnoWNVLYYWjp3swA;9.70713e+11

the first one has been emptied on january 2019 it held 223 705 BTC

the last one has 9.70713e+11 = 9 707 BTC  not active since October 2018 and no withdrawal since last year (Feb 2018)
 
you can check how many are still unspent

these few wallets hold more than 1 000 000 BTC 

Woah that https://www.blockchain.com/en/btc/address/1FeexV6bAHb8ybZjqQMjJrcCrHGW9sb6uF?offset=250&filter=6 address is filled with $300 million!
I thought this whole riddle was about 32 BTC?
Btw I am not into this cracking kinda stuff enough to participate into this. Just clicked through the posted addresses in this thread and found this HUGE wallet which a user above me posted.
 
Insane.  
I guess if this key is crackable, the reward is so insanely high because it is nearly impossible to crack.
I'd love to know the guy knowing the result to this riddle and get to know how to solve this lol. That'd be awesome.
Like "Hey dude you heard about this riddle I made with Bitcoin? You aren't into BTC anyway, so here's how to solve it...."
"Oh that sounds fun! No worries I won't participate in solving it. *Opens Bitcoin wallet and imports priv key*"  
 
By the way: Ever thought of where this huge stack of Coins might come from? Could the source be some illegal hacking stuff offering the coins for grabs via a riddle because they can't sell them anyway? (IF it is related to any riddle at all.) Could it be an exchange wallet not related to a riddle at all? Would be really interested in seeing some blockchain analysis here to get to know who owns/owned these coins and how they have been acquired. 2011 is a long long time ago.  
Or did Mark Karpeles forgot a paper wallet sitting in between his couch again?

 

hhh
this guy "1LuckyTJHcLLTnmeDZFbc1E18ZW87k36tk" has been hitting on this one https://www.blockchain.com/fr/btc/address/1FeexV6bAHb8ybZjqQMjJrcCrHGW9sb6uF
I guess he is getting desperate now 

Shit !!! unconfirmed

the BTC are back !!!!     

I don't understand, I thought I saw and empty wallet for a few seconds .. maybe I am too tired hhhhhh

Whoever got address 61: AVJKwzs9AskraJLGHAZPiaZcrpDr1U6AB

is hittng on address 160: 1NBC8uXJy1GiJ6drkiZa1WuKn51ps7EPTv

it is 1LuckyTJHcLLTnmeDZFbc1E18ZW87k36tk

address 61: AVJKwzs9AskraJLGHAZPiaZcrpDr1U6AB
Spent just now

https://www.blockchain.com/fr/btc/tx/cdae2da8fe4b18dc264e568a29e804f2b32529b8018a9d28e271ac7e9077c718

I think that sending anything to these addresses won't get you what you want.

Getting Spending scripts from these addresses is the only way   baby step or giant step trick will work.

So, if you get the pvk, spend everything at once ... whatever you leave can be swept very quickly afterwards

I think this guy just woke up  and is talking about some other puzzle solved a while ago : https://www.chepicap.com/en/news/4306/somebody-just-won-310-btc-bitcoin-challenge-solved-within-8-days.html
 

Yes that would be great. I have enabled issues for the repository.

Hidden in what picture?? I never saw a picture lol just the string of data. Is that what you mean?

Ok.

I have made other tests you may want to look into. I suppose it is better to open issues on github rather than here?

Yes you are right. This is not covered yet. I forgot continuation-file was a thing so this will get fixed with next update too.

I tried this (I am not sure if it does what I think it should )

./clBitCrack -r 61 -d 1 -b 72 -t 256 -p 2048 --continue hup.txt -o res.txt 1AVJKwzs9AskraJLGHAZPiaZcrpDr1U6AB


And this is what I get in my continue file hup.txt

start=0000000000000000000000000000000000000000000000000000000000000001
next=00000000000000000000000000000000000000000000000000000004A4000001
end=FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
blocks=72
threads=256
points=2048
compression=compressed
device=1
elapsed=344463
stride=0000000000000000000000000000000000000000000000000000000000000001

I suppose that in this context, continue file just tell me how many cases I ran .. right?

Next update will get rid of the parameter and just generate random values in specified keyspace start:end if -r is specified.
This will also optimize key initializing hopefully so it will start faster.

Nice

What prevents solve 61 puzzle puzzles with a little trick and baby step giant step?
The trick will be as follows...we know the approximate closed keys at the edges of the puzzle ,we also can compute and plot of 2^60-2^61 divide them into equal shares ,and then send to these addresses small Satoshi ,since Satoshi come we do the reverse translation with the new address back ,thus we learn from these addresses, public keys ,and all of it will be possible to calculate the private key 61 of the puzzle.