I always had a gut reaction against dice rolls.

原始 JSON

{
  "kind": 1,
  "id": "c278760bafbf59ccecf8ae7b62b14e8c82d254eeceb5ec5b26bfd3128f2c4db9",
  "pubkey": "675b84fe75e216ab947c7438ee519ca7775376ddf05dadfba6278bd012e1d728",
  "created_at": 1785562176,
  "tags": [
    [
      "client",
      "Primal Android"
    ]
  ],
  "content": "I always had a gut reaction against dice rolls.\n\nReflecting seriously, I have to reluctantly agree it's a solid concept.\n\nBut: why that gut negative reaction? Not because the number of bits is not exactly what you think because of some complex mathematical calculation.\n\nInstead, it's two related principles: 1/ complexity is the enemy of correctness. This is a lot of extra manual steps. 2/ I made up a \"law\" a long time ago: every time a user sees their secret key on a screen it cuts their security in half. This is a gray area: you may be entering the key material in chunks, and also a 'screen' on a hardware wallet is not the same as a computer screen.\n\nI've come round to it over the years, it's a sensible idea, but I'm still slightly suspicious.\n\nWe should be focused more on an audit step: however you generate the entropy, is there a way you can check the process is working? Dice rolls don't fit that idea so well (compared with machine-seeded).\n\nI'm reminded of an excellent point Gmax once made abou wallet dev: when you generate addresses for users, you should sanity check that you can actually sign against it, before giving it to the user, so they don't send their money to a black hole. \n\n",
  "sig": "6f401144d35e73e0e27b7939875e66a088daefcab8e66a63a9c8ad89217463a92d95fa02dfa43773634f6cc45c1ee27f335ea23259798dcaa36ea1bb725f4275"
}