[dicekeys]

And if you can demonstrate that there are functions are computable by a user community that would benefit from them, it would make a fantastic submission to the Symposium on Usable Privacy and Security (SOUPS).

But, most people are trusting software at some point. We're making sure our software is small and relatively simple so that you can audit it. That's one of the reasons why we don't take dependencies on Google's Tessearact OCR engine, or on frameworks like React. (The one big dependency we haven't removed is OpenCV.)

[ViViDboarder]

One of my concerns would be durability of the software over time. In 20 years from now, will the site still be running? Will I need to hunt down old hardware or dependencies to regenerate my key?

[sliken]

The mapping seems pretty straight forward, I don't see why it couldn't be manually done.

[dicekeys]

You can, in fact, do it manually. T4r means letter T, digit 4, facing right. The directions are 't', 'r', 'b', 'l' (top, right, bottom left), which makes for a mnemonic you can follow with "right here in river city".)

Before you transcribe, just rotate the box so that the first letter in the alphabet appears in the top left, than read in English order (left to right, then top to bottom).

The crypto library: cpp: https://github.com/dicekeys/seeded-crypto ts/js: https://github.com/dicekeys/seeded-crypto-js

[ViViDboarder]

Neat! Thanks for sharing.