MPC Framework Wishlist

Hey there! In [MPC Framework](https://github.com/voltrevo/mpc-framework) we currently primarily use [`emp-toolkit`](https://github.com/emp-toolkit/emp-agmpc) for a malicious secure backend. We're super interested in using `mpz` instead in the future, and we already have [`mpz-ts`](https://github.com/voltrevo/mpz-ts) utilizing an old version of mpz for not-malicious-secure garbling.

I'm not sure whether having a wishlist issue is compatible with your process, but please consider the following and feel free to split up/capture these in a way that makes more sense for you.

- [ ] Authenticated garbling
- [ ] N-party authenticated garbling
- [ ] wasm compatibility
- [ ] possibly avoid simd
- [ ] possibly avoid openssl (when porting emp-toolkit I had to replace it with mbedtls)
- [ ] option to not use threading (or figuring out why that was an issue in the past and possibly fixing it)
- [ ] Incremental/streaming preprocessing
- Doing this all upfront consumes a lot of memory. Much larger circuits should be possible if this can be done as-needed instead.

The issue names no files, tests, or entry points. Start by reviewing the linked MPC Framework, emp-toolkit, and mpz-ts projects, then separate authenticated garbling, WASM compatibility, and streaming preprocessing into scoped tasks. Done requires agreed acceptance criteria for the selected capability.

Written by the indexing model from the issue text.