Frank Denis

Good call. Is there any implementation yet? Especially outside Rust?

What we currently have for signatures and symmetric operations is something that can be directly mapped to the traditional NIST `init()`/`update()`/`finalize()` APIs. But we can add `update()`/`absorb()`/`squeeze()` alternatives that accept...

> There is parsing support for the wit syntax in wit-bindgen, but the canonical ABI implementation is not complete yet. `witx-codegen` doesn't support streams either, so there is some preliminary...

Hi Steve! And sorry for the delay, I'm still in Tokyo for HACS. Running the Wycheproof test vectors is good. However this is testing the underlying crypto libraries (which should...

Hi Steve, That's a very good point. Not just for asymmetric operations, btw. Batch operations are also useful for hashes and ciphers (most notably Keccak-based constructions). Introducing new functions seems...

Hi Steve, That looks really good! We need to clarify what happens/what errors get returned when batches are inconsistent, for example when algorithms don't match. Waiting a bit for possible...

Shouldn't that context be added to *all* functions, maybe as the first parameter?

Got it. And if the root context is read-only, lock contention shouldn't be an issue. How do applications get that root context? Should some kind of `init()` function be added?

But how do libraries get that handle? Is it by looking for a specific path such as `/dev/crypto`?

Having these operations implemented as a distinct WASM module is very compelling. There will be some additional considerations, such as how to provide a universal API to convert an element...