Presently all ferveo-generated objects are handled as bytes. Instead, ferveo types can be implemented directly in dks.rs as well as the python/wasm bindings. This implies that ferveo provides a crate exporting it's python and wasm bindings for consumption in nucypher-core (nucypher/ferveo#87).

targets

• ThresholdDecryptionRequest.ciphertext -> ferveo.api.Ciphertext
• ThresholdDecryptionResponse.decryption_share-> ferveo.tpke.api.DecryptionShareSimple||DecryptionSharePrecomputed
• NodeMetadataPayload.ferveo_public_key -> ferveo.common.keypair.PublicKey