4 ms·

Well secp256k1 private keys are just 32 random bytes (with some minor exceptions) so I think you could arrange something with a plain dice and a little bit of t

Well secp256k1 private keys are just 32 random bytes (with some minor exceptions) so I think you could arrange something with a plain dice and a little bit of time.

EmielMols 9y ago
Of course, but it would be cool if you could also calculate the public component on paper (and ideally verify it computerless as well). You could really create your bitcoin/ether/etc wallet with the public key only, whilst having an extremely low attack surface (private key never touches computer memory).
- Shoothe 9y ago
  But remember the caveats about using the same key pair for multiple transactions: https://en.bitcoin.it/wiki/Address_reuse https://en.bitcoin.it/wiki/Address_reuse
- lotyrin 9y ago
  I wonder if a slightly more feasible solution of producing and verifying a solution out of simple TTL, so there's no "computer" just a application specific machine made of simple commodity parts which one could trust reasonably easily would be actually worth something.
remcob 9y ago
Generating the private key is the easy part; Just 77 rolls with a ten-sided die and re-try if it exceeds the prime. Or 256 coin flips, if you prefer binary. It is computing the public key that is so hard.
- Shoothe 9y ago
  For practical purposes I'd recommend an offline laptop, maybe running Tails OS and Electrum [0]. Public key is one thing and making transactions and signatures quite another. [0]: https://tails.boum.org/doc/anonymous_internet/electrum/index.pt.html https://tails.boum.org/doc/anonymous_internet/electrum/index...