noble-ed25519 VS tweetnacl-js

[For reference, see section 7.8](https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.186-5-draft...).

I've also been looking for Ed25519ph support for other languages. [Paul Miller](https://github.com/paulmillr), who is the author of the noble libraries for Javascript has just added support in his newly released [curves](https://github.com/paulmillr/noble-ed25519/issues/63) library. Paul has suggested on Twitter holding off on using "curves" until an audit, but most of his other work has already been audited and all his works are highly polished.

Also, for all readers, we wrote an [online Ed25519 tool](https://cyphr.me/ed25519_applet/ed.html), which is useful for testing and verifying. Previously the top result on Google, which has now been taken down, was sending the keys off to a server, which motivated us to write a tool that didn't openly phone home.

(Git hashes the repo and provides version history. It's not "super secure", but it is much better than nothing. I could also sign releases, but I'm not doing that at the moment, since I don't think the marginal benefit is there, especially since Paul is signing the crypto part already.)

This is great, finding NaCl (libsodium) has been a godsend, specifically the JS lib.

1 - https://nacl.cr.yp.to/

2 - https://github.com/dchest/tweetnacl-js

On cryptography, our whitepaper shares information on the general cryptography choices - login, authentication, keypairs, etc. It's quite similar to password managers or encrypted communication apps. In the actual product (code here https://github.com/skiff-org/skiff-mail), we use the library TweetNaCl (https://github.com/dchest/tweetnacl-js) which is designed to be fast, trustworthy, and performant

Working with encryption more broadly will equip you to understand the fundamentals that underpin the web3/crypto world: hashes, asymmetric crypto, signatures, signature chains, etc. And it also has many uses, of course, outside the web3 realm.

If you're working with Node, tweetnacl.js (https://github.com/dchest/tweetnacl-js) gives you secure defaults and a nice API to start learning and building with.

Once you're familiar with this stuff, blockchains/cryptocurrency/web3 loses a lot of its mystery. They're essentially all just different takes on using key management and signature chains to verify identities and

Those things are not the same. With the Berne Convention Implementation Act of 1988 (and the earlier Copyright Act of 1976, which went into effect in 1978), all works were by default copyright protected. In the absence of a legal notice, nobody can reliably use this for anything at all. Most jurisdictions don't even have a way of reliably dedicating anything to the public domain, hence the existence of permissive licenses. Please at least consider adding the ISC or MIT or Unlicense text or similar to a LICENSE or NOTICE file in your repository. An example: https://github.com/dchest/tweetnacl-js/blob/master/LICENSE