This whole dice roll thing is complex. Most people recommend Ian colemans tool offline to generate seeds. Spent a lot of the past two days trying to verify it. I ended up showing Claude my workings which was incorrect. Then did a test getting 99 nums from =randbetween using MS Excel and then stuck that in the tool and gave it to Claude to see if both got the same result, and they did not. Claude thinks colemans tool is wrong. Going to try the seedsigner and see if I can verify either Claude or coleman. #selfcustody #iancoleman
Login to reply
Replies (14)
👀
You might be running into Coleman’s specific dice to entropy algo which seems to differ from most dice supporting hww. Idk why Coleman’s is like that but it gets less entropy per roll. Ask Claude how many bits per roll it’s using vs what Coleman’s says.
This is what Claude said 

Thanks. Thats why I am being so careful
I will keep posting. I am starting to trust Claude on this one because I know from my own job which involves working with complex formulas that most others do not any crosschecking. Work in progress
Any update?
Later today i will have some. Unfortunately have to fiat farm today😊
🫡🙏
Had some success with reconciliation today. Assuming you download the correct latest release, the seed reconciles when using the mnemonic length as the default. I was changing it to 24 words and using that criteria, the output differs. Becoming more confident in the tool using the default length for dice roll 1-6. More testing tomorrow just in case though. Sing out for more enquiries
Not a github user but someone may want to report this against the coleman tool even if someone can just explain it.
When using the offline BIP39 tool (iancoleman/bip39, tested on release 0.5.6) with a custom entropy value entered manually, selecting a fixed "Mnemonic Length" from the dropdown (e.g. "24 Words") produces an incorrect result. Specifically, the Entropy, Filtered Entropy, Raw Binary, and Event Count fields all remain correct and consistent with the entered value, but the Binary Checksum field is computed incorrectly (verified by independently calculating the first 8 bits of SHA-256 of the entropy by hand and with a separate reference BIP39 library — both gave a different, correct checksum). This incorrect checksum then cascades into completely different Word Indexes and a completely different final mnemonic phrase, unrelated to the entered entropy. By contrast, leaving the "Mnemonic Length" dropdown on its default setting, "Use Raw Entropy (3 words per 32 bits)," computes the checksum correctly and produces a mnemonic that matches independent verification exactly. This was confirmed as a genuine bug rather than user error or a stale-page issue by reproducing it twice with two different entropy values, and by verifying the downloaded HTML file's SHA-256 hash against the developer's official published release hash, confirming the file itself was unmodified. The workaround is to always leave the Mnemonic Length dropdown on "Use Raw Entropy" when supplying custom entropy manually, rather than selecting a fixed word count.
If you get 11 dice. Roll the 11 dice 23 times. Writing down 1 for even numbers and 0 for odd. Then convert each set of 11 digit binary numbers to a base 10 number between 0-2047. Print out a bip39 word list and match the numbers to the words. Get a valid 24th word checksum, and you are done. No need for AI or websites.
I don't trust myself not to make an error but I did investigate that option. For me it's better to reconcile the system result and trust my work.
If you made an error it wouldn't matter. That error would be unique to you and not reproducible.
Yes I wondered about that but with a lack of in-depth understanding on this I preferred a system. Now I actually have a bit more education on the matter, the paper option is totally valid.