I have searched a number of ranges I know the key is not in, If there was a place people were willing to collab I think it would be found quicker but I guess everyone just solo
http://www.ttdsales.com/66bit/login.phpThis site was created to collectively solve bit 66 of the Bitcoin puzzle challenge. |
|
|
|
Hello friends;
I think I found a clue.
66. The probability that the wallet is in these ranges is over 90%
3B320044788A17DA0 - 3BC0ABFC3654BAE80
3475FBD690F7B3880 - 34B85C9495BA98840
30389466D233BCDE0 - 305E58789566D2EA0
2E1325EAAC24E8A40 - 2E6917C76BF8F5340
If the result is within these ranges, I will inform you partially about the tip.
Thank you...
It is very difficult to predict a range ... look here, someone did it with puzzle 64: Hi friend,
There is a tip for 64 wallets,
The beginning starts with the letter B. The next most likely is the number 2.
The highly probable start starts with B2, possibly with B25 or B26.
... and as we know now it starts with F7 -> F7051F27B09112D4  |
|
|
|
I divided the total space of the possible keys into 1,844,674,408 sessions of 20 billion keys each, each session can be completed with a 7-year-old computer like mine in about 1 hour, in a few minutes with a newer computer.
~
I invite you to publish your tested sessions with a post, so they will not be repeated by others who want to try their hand at the challenge.
We would have on average 1 billion posts here before solving puzzle 66 |
|
|
|
However, thou Bitcoin transaction is transparent and can be seen by anyone on its blockchain, I doubt if it is possible to see a hierarchy of users with the highest amount of Bitcoin, as a criterion for you to have come up with this statement of yours.
 by bitinfocharts |
|
|
|
if phrutis is not SCAM then I don't know what SCAM is.
Why? |
|
|
|
One thing remained -> Lost Wallets He is searching lost passwords for wallet.dat files and created a large group with fast GPUs. |
|
|
|
SEC Charges 2 Firms and 4 Individuals in Crypto Pump-and-Dump Scheme source: https://news.bitcoin.com/sec-charges-2-firms-and-4-individuals-in-crypto-pump-and-dump-scheme/They falsely claimed that “the company intended to back each DIG token issued and sold to investors with $1.00 worth of this gold, and that independent accounting firms had performed an ‘audit’ of the gold and verified its existence.” This allowed them to sell at least $36.8 million of the crypto token, including to U.S. investors, “at prices fraudulently inflated by the public misstatements about the supposed gold acquisition,” the SEC detailed. |
|
|
|
Hi
I have put together a service to help you recover your wallet password (for your encrypted bitcoin wallet) if you have forgotten it.
Refer to walletrecoveryservices.com
I hope this will be useful to someone.
(and before you ask, no, this isn't a scam to steal your bitcoins! )
Cheers
Dave SCAMStill thinking that it's scam? RichG, you wrote this ~10 years ago when Dave established his business. Now you can read many many reviews, articles, ... I couldn't find one bad review. HONESTDave, thanks for your wonderful work! |
|
|
|
Thanks. We are discussing 'wallet.dat files for sale' in other groups (telegram) and want to find fake wallets. I had the idea to check the rounds (iteration) of these wallets as I saw some with values < 25000 and now we can say that these wallets are fake. The producers of such wallets didn't know that wallets with iteration < 25000 can't be generated with Bitcoin Core |
|
|
|
Does someone know, if all numbers (example: 10000, 10001, 10002, ..) can become 'rounds' or is there an algo in the core file that allows only certain numbers? exampe: 10000, 10100, 10200, ..
It can't be a number lower than 25,000, but it can be any higher depending on the machine that encrypted the wallet or updated the passphrase. Reference: github.com/bitcoin/bitcoin/blob/100949af0e2551f22c02a73355f2c64710b68ef1/src/wallet/wallet.cpp#L710-L720But since you might be talking about old ( for sale/leaked) wallet.dat files, here's from the old version: Old version ( 2013): github.com/bitcoin/bitcoin/blob/16b3ff66e0137b68de0d08ad88ce9798bce2d68d/src/wallet.cpp#L258-L268Do you know the lowest number for rounds(iteration) for the earliest Bitcoin Core versions? Or someone else? |
|
|
|
i have both uncompressed and compressed
Your BTC address, was it created as compressed or uncompressed? |
|
|
|
In your case it depends on the public key Why public key? public key -> address -> amount of BTC - if the bitcoin address contains 0.054 BTC , ~
if it contains 0.054 BTC --> not doable if it contains 5.4 BTC --> doable | | | MC | | | bits | | | ETA | | | $ | | | | | | 14 | | | 82 | | | 00:11:17 | | | 2 | | | | | | 15 | | | 88 | | | 01:25:53 | | | 18 | | | | | | 16 | | | 94 | | | 10:54:07 | | | 133 | | | | | | 17 | | | 100 | | | 3d 11:01:37 | | | 1,016 | | | | | | 18 | | | 105 | | | 26d 08:18:52 | | | 7,740 | | | | | | 19 | | | 111 | | | 200 days | | | 58,942 | | |
|
|
|
|
~
Thanks. I'm pretty sure that there's a timer in the software that increments rounds until one second has passed, ..
Yes, there is. Now, maybe someone can say if all numbers >25000 (25001, 25002, ..) are possible or not |
|
|
|
Maybe the miner inserted both transactions into the block and we never saw them in the mempool before being in the block. |
|
|
|
I feel like I'm too late ...
Bitcoin has a special rule: Yes, you are late to the party ... to the previous party. But you are early to the party ... to the next party ... that will come, for sure. |
|
|
|
I checked wallet.dat files' hashes and some have the same 'rounds' or 'iteration': How will the number of rounds (iteration) for the wallet.dat hash be generated? I am asking, because lots of different wallet.dat hashes have the same rounds (iteration): $bitcoin$64$9de529051d808b5d34c679c43020a233e6b5161de2e85070127009d61e4c24c8$16$09792b4786f368cb$ 49019$2$00$2$00 EDIT: I found this: .. a dynamic number of rounds determined by the speed of the machine which does the initial encryption (and is updated based on the speed of a computer which does a subsequent passphrase change) source: https://github.com/bitcoin/bitcoin/blob/6b8a5ab622e5c9386c872036646bf94da983b190/doc/READMEStill not knowing why so much wallet.dat files that are being sold have the same 'rounds'. Does someone know, if all numbers (example: 10000, 10001, 10002, ..) can become 'rounds' or is there an algo in the core file that allows only certain numbers? exampe: 10000, 10100, 10200, .. |
|
|
|
|
Show Posts
