Post 9jYCGGbBzOTYdnb4We by cryptocoderbob@bitcoinhackers.org
 (DIR) More posts by cryptocoderbob@bitcoinhackers.org
 (DIR) Post #9jYCGGbBzOTYdnb4We by cryptocoderbob@bitcoinhackers.org
       2019-06-05T22:34:36Z
       
       0 likes, 0 repeats
       
       Anyone manually generated a bech32 bip39 wallet? Trying to follow what is layed out in the BIP39 page, not having success when comparing with this tool: https://iancoleman.io/bip39/@402PaymentRequired @art_vandelay @btcFUD @Sosthene
       
 (DIR) Post #9jYCfFR9RjpgHDoQQi by cryptocoderbob@bitcoinhackers.org
       2019-06-05T22:39:08Z
       
       0 likes, 0 repeats
       
       @402PaymentRequired @art_vandelay @btcFUD @Sosthene I generated 256 bits, ran it into sha265, converted the hash back to binary, appended the first 8 bits of hash onto the tail of my 256 bits (now a total of 264 bits). Then I put these bits into the "Entropy" field in the tool and I cannot figure out how it generated the word list. Splitting my 264 bits into 24 11-bit  chunks then converting these binary chunks into decimal and matching the number with the word list doesn't yield the same words
       
 (DIR) Post #9jYnsnbrOutuKX97wG by Sosthene@bitcoinhackers.org
       2019-06-06T05:36:10Z
       
       0 likes, 0 repeats
       
       @cryptocoderbob @402PaymentRequired @art_vandelay @btcFUD never tried that sorry, but looks interesting I'll try that eventually
       
 (DIR) Post #9jjtjLEiGA16Bnkg0O by btcFUD@bitcoinhackers.org
       2019-06-11T14:03:30Z
       
       0 likes, 0 repeats
       
       @cryptocoderbob @402PaymentRequired @art_vandelay @Sosthene When you converted to sha256, did you avoid encoding the newline character that you get by default?