Dice to Seed - comprehensive guide

[dkbit98]

I found a very nice guide how to use dice to correctly generate strong entropy for your seed words.
This was written by developer Keith Mukai who is one of the meain developers for Seedigner projects.
He is trying to standardize dice seed generation for all wallets, as alternative for using mess combination used by many wallets.

This should be a good reading material even for people who think they know how to use dice for see generation:
https://kdmukai-bot.github.io/seedsigner-ai-analysis/dice/standard.html

[LoyceV]

That was a good read. But still, I'd feel more confident (and less paranoid) if I combine the randomness of this dice seed with a Trezor seed:

This way, even if one of the random inputs is compromised, adding them together ensures it's still completely random.
Real random + flawed random = real random.
Real random + real random = real random.

[BlackHatCoiner]

The dice paranoia is really unjustified. Any dice is fine if you roll it enough times; in SeedSigner, that is 99 times, and even with a completely flawed dice that returns '5' 75% of the times, you're still getting above 128 bits.

Just to understand how flawed this is, you'd be getting roughly 75 times a '5' and roughly five times '1', '2', '3', '4' and '6', each. You'd notice it, and you could just change dice. But even with that flawed dice, you're getting enough entropy.

[LoyceV]

99 times, and even with a completely flawed dice that returns '5' 75% of the times, you're still getting above 128 bits.

Can you show the math on this? My gut feeling tells me this should produce much less than 128 bits entropy, but my statistics is rusty.

[bitmover]

99 times, and even with a completely flawed dice that returns '5' 75% of the times, you're still getting above 128 bits.

Can you show the math on this? My gut feeling tells me this should produce much less than 128 bits entropy, but my statistics is rusty.

Here in the post . He mentions a 50% flawed dice , but looks solid still

https://kdmukai-bot.github.io/seedsigner-ai-analysis/dice/standard.html#quality

I think the point is that the attacker doesn't know that your seed used a flawed dice, and which number is repeating.

The problem is when you created a wallet with a flawed method used by thousands of people and the flaws are known (like coldcard)

[notocactus]

Here in the post . He mentions a 50% flawed dice , but looks solid still

It only looks and is solid till it is compromised, and I only want to try with dice method without flaws. So if it is 50% flawed dice, and I know that from reports, I will never hesitate to abandon that wallet and instantly move my bitcoins to another wallet without flawed dice.

I think the point is that the attacker doesn't know that your seed used a flawed dice, and which number is repeating.

The problem is when you created a wallet with a flawed method used by thousands of people and the flaws are known (like coldcard)

That's true but it also says about a fact that is not comfortable at all because non technical people only can trust technical guys, companies, manufacturers about security and quality of a wallet.

Like I trust Bitcoin Core, trust Electrum because they are very old wallet brands and people technically reviewed those wallets as top notch. I don't know how to do technical things, code reviews and I have no other choice than trusting them while they all can make mistakes from developments, QA/QC to community reviews.

It's stressful during this AI era.