Feature or Enhancement?

• (x) New feature
• ( ) Enhancement of existing feature

Description

When I adapted the TweetNaCl library and included it in the micropython runtime, it took over a second to make or validate an ed25519 signature. For reference, ordinary PyNaCl takes a few dozen microseconds for either (29 μs for sign and 58 μs for verify on my machine; just now benchmarked it). A millisecond is probably the most latency that can be tolerated without making the router logic into its own denial-of-service.

I can currently see a few possible paths forward:

1. Test the ucrypto micropython library.
2. Fork libsodium; pair it down to just the minimum logic necessary for ed25519 signatures; adapt for the micropython runtime; add to the micropython fork; test on esp32
3. Adapt the micro-ecc library for the micropython runtime; add to the micropython fork; test on esp32
4. Support only the ESP32-H2 and the curves it accelerates.

Additional context

Already started the fork of libsodium here but have not gotten very far with it.