Quote from: chryptof on February 17, 2019, 12:00:52 AM

Quote from: greg007r on February 16, 2019, 11:48:33 PM

Quote from: chryptof on February 16, 2019, 11:21:54 PM

Quote from: greg007r on February 16, 2019, 07:21:41 PM

Quote from: runlola on February 16, 2019, 06:57:13 PM

Quote from: greg007r on February 16, 2019, 01:53:23 PM

My script has already processed 1/10 of the permutations based on BIP39 word list, nothing
Another script has already processed 1/5 of the permutations based on the transcript of the https://www.youtube.com/watch?v=AABkJ55Zz3A page, nothing

considering there are 2048^8 permutations of the bip39 list, i doubt that. The number of valid possibilities using that list is ~2000x smaller (161,735,049,399,563,309,103,078 - see this post for how it was derived). my program can check 100K phrases/s and it would take ~5B years to check 10% of those.

Yes, you are right but you can downsize drastically the amount of possible permutations by :

- Keeping 1/10 of the BIP39 list (from 2048 to 230), removing all not related words (eg: Drift,Fish and Fiscal) and keeping interrsting ones (eg : satoshi, million,coin,supply, tooth, one ...)
- Preventing permutations where two words are duplicated (eg: ThisThisOneToothThisThisThisThis symptom)
- Allowing only phrase of 8 words having 32 chars
- Preventing permutations where no more than 4 instances of a word having 4 letters
- For those who believe in the sequence W T C O N O H T would be even faster to check
- many more

Sample extract of last 10 lines of my logs :

Sat Feb 16 19:51:11 CET 2019 : 346/4830|3 3 5 4 7 4 3 3 FixUseWorthWillMillionCoinAllFit : 12YVLipqmKfPwNwoy1Wpemja89Jf2q1vxh
Sat Feb 16 19:51:11 CET 2019 : 346/4830|3 3 6 4 5 3 5 3 FitAllAnswerCoinWhaleUseMatchOne : 1CRgZoDGdTRfF679hdKXyZgbGuEMPaZXyF
Sat Feb 16 19:51:59 CET 2019 : 346/4830|3 3 5 4 7 4 3 3 OneCanFinalOnlySegmentThisAllFit : 1Fug6cBx487thwS1Zp5nSCJAaAJxWfXrqL
Sat Feb 16 19:52:47 CET 2019 : 346/4830|3 3 5 4 7 4 3 3 OneFixFinalCoinControlOnlyCanFit : 1PKHseF7iqNWMv5At1YdCDVCvUW9C9ados
Sat Feb 16 19:53:34 CET 2019 : 346/4830|3 3 6 4 5 3 5 3 CanFitExcessGoldWhaleAllThereOne : 12MdRtKqKsT8Tw2AyR6JZhmXL8ZJcsXGVw
Sat Feb 16 19:54:22 CET 2019 : 347/4830|4 4 4 3 3 4 5 5 WantSoonHaveOneUseThisFinalExact : 17bcNocTMuHksCbRVRcMiLMMLvaoTMGdSm
Sat Feb 16 19:54:22 CET 2019 : 347/4830|4 3 3 5 3 5 4 5 ThisFixCanWorthAllWhaleGoldThere : 1GwNvXvrbxgmmQY27YL4gwcjjJEyX42LKw
Sat Feb 16 19:55:10 CET 2019 : 347/4830|3 3 5 4 7 4 3 3 AllCanBuildWantControlHaveOneFit : 17azNQ3Z5GqpvrEgo4YemT9Rc7DCBnRi6n
Sat Feb 16 19:55:58 CET 2019 : 347/4830|4 3 3 5 3 5 4 5 WantUseOneTokenCanMimicLikeThere : 17oWja4HkduPeEsQSWC1bgdSLubdnT5pwk
Sat Feb 16 19:55:58 CET 2019 : 347/4830|3 4 4 3 4 3 3 8 UseLikeWaitCanWantFixAllProperty : 17uRQ63APaDNncu2cmKXiQsjff3kNKnXWB
Sat Feb 16 19:56:46 CET 2019 : 347/4830|4 4 4 3 3 4 5 5 LikeHaveWaitAllUseWillLimitExact : 1YuVK4QA2K44sycmF3hDFFy8DCi6ne7sF
Sat Feb 16 19:57:33 CET 2019 : 347/4830|4 3 3 5 3 5 4 5 SoonUseFitBuildCanWhaleOnlyThere : 16PMF61M6G8SQrXVAmgcRCZP2CcmsksnxC
Sat Feb 16 19:58:21 CET 2019 : 347/4830|3 4 4 3 4 3 3 8 CanWillCoinFixWaitUseAllRemember : 1JqCymN2wdVKM1zJUaiTgUTZPwkNXb1mVD
Sat Feb 16 19:59:09 CET 2019 : 347/4830|4 4 4 3 3 4 5 5 SoonThatOnlyAllOneLikeMimicExact : 15rrST9vDQhBwqE6XTcsUfixmZFDMVXpri
Sat Feb 16 19:59:57 CET 2019 : 347/4830|4 3 3 5 3 5 4 5 OnlyCanOneWorthFixExactThatThere : 1DiHHkHMTaQkSsbtV6To7YWF4LWuT329j
Sat Feb 16 20:00:45 CET 2019 : 348/4830|4 4 4 3 3 4 5 5 ThatGoldViewOneAllHaveProofExact : 18DWm63gZ9gYUS5ZnRP7Hp3J3tJGQps3yY
Sat Feb 16 20:01:29 CET 2019 : 348/4830|3 3 5 4 7 4 3 3 CanAllFinalThisSatisfyHaveOneFix : 1MaAgoj6AJ1T4NHoZLM3g5EohWwJ2n5MR2

Hope this help,

greg007r, I wonder how You Generate this addresses.
Should one not just hex output the text and use this as the ECDSA private key?

If I take for example your last example; CanAllFinalThisSatisfyHaveOneFix : 1MaAgoj6AJ1T4NHoZLM3g5EohWwJ2n5MR2
I get 1NSPwaCCTcA8JS99Em6nhyW1vHiX2F2pUg as the Address?

How do you get that 1MaAgoj6AJ1T4NHoZLM3g5EohWwJ2n5MR2 address?

Thanks in Advance

You can always validate your output on brain wallet : https://brainwalletx.github.io/

I use part of the api of bitcoinj :

Code:

import java.security.MessageDigest;
import org.bitcoinj.core.ECKey;
import org.bitcoinj.core.LegacyAddress;
import org.bitcoinj.params.MainNetParams;
byte[] hash = null;
try {
   MessageDigest md = MessageDigest.getInstance("SHA-256");
   md.update("CanAllFinalThisSatisfyHaveOneFix".getBytes("UTF-8"));
   hash = md.digest();
   ECKey key = new ECKey(hash, (byte[]) null);
   LegacyAddress address = LegacyAddress.fromKey(MainNetParams.get(), key);
   //if ("179sxfh6rw6bHSo5wVUhLP96k46QaEzVP".equals(address.toString())) {
   System.out.println("--------------------------------------------");
System.out.println("privkey hex :" + key.getPrivateKeyAsHex());
System.out.println("privkey wif :" + key.getPrivateKeyAsWiF(MainNetParams.get()));
   System.out.println("privkey int :" + key.getPrivKey());
   System.out.println("base58 :" + address.toBase58());
   System.out.println("string :" + address.toString());
   System.out.println("hex hash :" + Hex.encodeHexString(address.getHash()));
   //}
} catch (NoSuchAlgorithmException e) {
e.printStackTrace();
} catch (UnsupportedEncodingException e) {
   e.printStackTrace();
}

Ok, Thanks

I tried what you suggested and indeed the address fits the one you showed before.

But in an earlier post, someone suggested to take the 32 Char String, get the hex output for it (by for example paste it in https://www.online-toolz.com/tools/text-hex-convertor.php) and then use that HEX output as the ECDSA Private Key (for example paste it in https://gobittest.appspot.com/Address) and then it gives the answer I showed you before.

So, now are my questions:

- Which is the way to follow?
- Which of both VALID addresses is the one we search for?

Thanks In Advance

As far as I understand, a private key is a 256bit unsigned integer that can be represented as well as HEX, BASE64, WIF or PLAIN.
In the concept of BrainWallet, we want to use a phrase instead of 64 digits long number.
So you need to SHA256 hash the 32 char 'phrase' to get your 256bit unsigned integer or private key
From there, it will be possible to derive the public key and then the uncompressed Base58 Address.
Producing the uncompressed base58 address from the private key involves multiple sha256 and RIPEMD160 hashing in a specific sequence.

https://en.bitcoin.it/w/images/en/9/9b/PubKeyToAddr.png

And for https://www.online-toolz.com/tools/text-hex-convertor.php converts your text into the corresponding HEX representation of code point of the character. (eg : a=61,b=62 )
If you provide, a 32 letters long word to the converter, it will return a 64 long digit (32x2) exactly the same length as the return of sha256(phrase) but completely different !