Using this you can create your own wallets to store btc???
Yes, you can. But you should be very careful with the random entropy (use coin) and secure internet connection (or use the tool offline). PS. To be honest if you do not understand what you do, I do not recommend to use this tool. |
|
|
|
|
The private key for address 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa (received the reward from genesis block) could be not saved by Satoshi, and it does not matter is him/her alive or not. It just the test transaction with the initial purpose to have the balance FOREVER.
|
|
|
|
|
I remember I saw somewhere the benchmark table with the speeds for BitCrack with different nvidia cards (2080,3080,4080, .... ti versions, Tesla, etc). Can you please share it or write the current benchmarks (actual in 2024 with the most common hardware).
|
|
|
|
So it was you who renewed the domain, correct? And what do you mean by registrar saving the domain for you? is that something unusual?
Anyways thank you for such a great service, it really is one of the helpful tools I have ever seen. 😉👏👍
Yes, I renewed the domain. The auto prolongation was active with the registrar (if forget it saves the domain for you but you should pay more). Registrar renewed the domain however suspended to use it before payment. |
|
|
|
If it is really useful for you to have this tool, I can try to upload it and set it on one of my domains. edit: https://btckeygen.com/ is online again Of course it is useful, do you know of any other way/ tool, where you could generate any bit of key space with a single tap/ click? This tool is one of the most useful crypto tools in the world. Most of the things I have learned about cryptography is because of this 16×16 grid. Thanks for the offer though. Thank you so much for your feedback. Yes, there was a domain issue as I forget to renew it. However thanks to registrar for saving the domain for me  |
|
|
|
|
So, it is not some special knowledge (hidden from the public). It was a luck for #120 and #125 - by the luck I also mean that they used Kangaroo method and Jean's GPU code (it also need some luck). The #120 and #125 winners just have huge GPU power.
|
|
|
|
yeah, I'm not confident anymore about the security of Bitcoin and secp256k1, especially when the solvers of these large keys are not willing to share what methods they used to reveal the private keys, the whole purpose of this challenge is to prove the immunity of the math behind bitcoin from any attack, so when someone is able to solve the challenge and not coming out to explain the method, this is basically telling us that someone knows a backdoor.
For #120 and #125 puzzle addresses it was "random" luck, and not some special knowledge. So, keep calm and be confident in secp256k1 and bitcoin security. |
|
|
|
-snip-
2023-04-16 - The creator of the challenge paid rounded amounts of BTC to the remaining unguessed addresses - thus increasing the value of the prizes by a total of over 900 BTC. From this moment, for example - the reward value for address 66 is not 0.66BTC but 6.6BTC
-snip-
How do you know the source of the latest 900 btc and say that it was made by the creator? The transaction potentially could lead to the stolen funds...  |
|
|
|
A salt is used in order to protect the hash from pre-computed tables. A salt is random data that is used as an additional input to a one-way function that hashes data. The cry_rounds is the number of rounds used for hashing the password (together with salt). The general wallet encryption algorithm is described here: https://en.bitcoin.it/wiki/Wallet_encryption: "Wallet encryption uses AES-256-CBC to encrypt only the private keys that are held in a wallet. The keys are encrypted with a master key which is entirely random. This master key is then encrypted with AES-256-CBC with a key derived from the passphrase using SHA-512 and OpenSSL's EVP_BytesToKey and a dynamic number of rounds determined by the speed of the machine which does the initial encryption"So, the more cry_rounds you have - the more sha512 rounds you should perform while decryption the password (also, the better computer you use for wallet.dat encryption, the more cry_rounds you will have). In general, the encryption process could be represented as following: data = pasw+salt
for i in range(rounds):
data = sha512(data)
key = data[0:32]
iv = data[32:32+16]
dec = AES(key, CBC_MODE, iv).decrypt(cry_master) : hashcat forum https://hashcat.net/forum/thread-9521.html |
|
|
|
The private key of your wallet (a 256-bit number) is symmetrically encrypted with a random master key and that master key is subsequently encrypted with the user-defined password. The reason why your hashes are different for the same password is because the random master key, random salt and random number of iteration is used for every attempt. The hash you showed has the strict structure. Let me show what does mean each line from your first example (hope this will help you): $bitcoin // coin name (could be also litecoin, as the example)$64 // len of cry_master - master private key$9baaabed8bde61f4da580ff22905fd2dab69b6193bb365f0fdfbc540ff9f20fc // master private key - encrypted_key from wallet.dat$16 // len of salt$9d4164a034dfdb82 // cry_salt - salt from wallet.dat$307949 // cry_rounds - number of rounds, nDerivationIterations from wallet.dat$96 // len of encrypted_privkey$0497430f102ff66a1556910eb9b9f3277cc38f437fb79f1d78345c770ac918cba04e48e785e29cc169a4e3c0b88b39f5 // ckey - encrypted_privkey from wallet.dat$66 // len of public key$03fff614df1bd468aa061bec32eff7b14c42a0a3d0df7d984a7b74a30a99f0ec87 // public key - pubkey from wallet.dayFor more details, you can also examine the tool called bitcoin2john.py - this tool extracts hashes from bitcoin wallet.dat Sample bitcion2john.py code is here: https://github.com/sirrushoo/python/blob/master/bitcoin2john.pyPS. This type of hash from wallet.dat also is suitable for hashcat (-m 11300 mode). Have a look at it too in order to understand more. |
|
|
|
I received a DM about this thread.
bitaddress.org has never been hacked.
For many years it's been hosted on github.com
I have no indication that my github has been compromised.
I have no indication that my domain registrar account or DNSSEC has been compromised.
I have a script that monitors the checksum of bitaddress.org and received no alerts of any issue.
....
I remembered that 3+ years ago was confused why bitaddress.org generated wrong wallets. Here is my post: https://bitcointalk.org/index.php?topic=43496.msg52190779#msg52190779The issue was I used wrong web address: "Everybody should be very careful. The addresses above were actually generated not by bitaddress.org, but by biladdress.org ("l" instead of "t"). I do not know how did I go there... probably some fake link :-(" That time fake clone was working and provided wrong public addresses (so, users received incorrect public btc addresses, and actually they did not have private keys to btc addresses showed on their "paper wallets"). I just remembered that my case, cause OP also could face with the same fake clone web address while generating his paper wallet - fake clone in global WWW (with the similar spelling) or fake clone provided through DNS spoofing (OP saw bitaddress.org in his web browser, but actually visited completely different IP address). |
|
|
|
Hello!
...
I found saved kangaroo progress files that allowed me to find key 115 in the past!
...
So for interested groups/individuals - I have these progress files and I will sell them for 2ETH (upfront payment). If you are interested, please contact me via private message. To be fair - I sell files only once.
Regards
Just distribute these files for free and clean your disk space. No need to sale  |
|
|
|
I still want to find at least 2 different public keys (better different private keys within the bitcoin elliptic curve order) which lead to the same bitcoin addresses  |
|
|
|
You should not use API and check the wallets online. The only way to check your passphrases database is to compare the generated brain wallets with your local database (take it from daily blockchair dumps - https://gz.blockchair.com/bitcoin/addresses) or take from Loyce. |
|
|
|
|
Why is this shit coin (SQUID GAME) still trading with 1.5-2 million USD daily turnover?
|
|
|
|
Suppose I crack puzzle 64.. please suggest to me how can I avoid double-spending Until I take out all the coins.. like BTC, BTH, BTG ??
You should broadcast all the transactions at the same time. You also should turn off RBF options (replace-by-fee) |
|
|
|
|
Jean_Luc made his last post on October 11, 2020, and he was last active July 28, 2021 (more than 6 months ago). His last commits on github were also a year ago (February 2021)
Is everything ok with TC? (Jean_Luc)
|
|
|
|
I was using Bitcoincrack to randomly Bruteforce addresses that share the same 7 letters of 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN.
after bitcoincrack generated today 1000 addresses that share the same first 7 address characters ~ and indeed, i saw an addresses that ends with the last 3 characters "XQN" that the original puzzle 64 address have.
~
What are the odds that i find the last 3 characters address Each character has 58 possibilities, so if you have 1000 addresses, the chance of finding the same 3 characters at the end is about 0.5%. However, you need to find 24 more characters, and those aren't magically going to match once you find the last 3. He actually found 9 characters (10 characters including the 1st "1"): 16jY7qLJnxb7CHZyqBP8qca9d51gAjy XQN - #64 puzzle 16jY7qLHKTofWA2DYS9ZaWyvZ5qnjfS XQN - found by Alpaste But looks nice to have a vanity address with 10 characters and the same bit size. |
|
|
|
|
Show Posts
