Skip to content

Consolidate TrBFV params #991

Description

@ryardley

In enclave we have various specifications of TrBFV params:

here: https://github.com/gnosisguild/enclave/blob/418e42feceb5596a50f4f039f45d0f102fb7d50b/tests/integration/base.sh#L56-L62

here: https://github.com/gnosisguild/enclave/blob/418e42feceb5596a50f4f039f45d0f102fb7d50b/tests/integration/persist.sh#L52-L58

here: https://github.com/gnosisguild/enclave/blob/418e42feceb5596a50f4f039f45d0f102fb7d50b/examples/CRISP/crates/zk-inputs/src/lib.rs#L35-L37

here: https://github.com/gnosisguild/enclave/blob/418e42feceb5596a50f4f039f45d0f102fb7d50b/packages/enclave-sdk/src/types.ts#L325-L354

These all should ONLY come from a single place:

here: https://github.com/gnosisguild/enclave/blob/418e42feceb5596a50f4f039f45d0f102fb7d50b/crates/bfv-helpers/src/lib.rs#L36-L73

For typescript we need a wasm function that gets the params based on the identifier we request that way a user can use whever params they like but they are tokenized.

In most instances we need something like:

build_bfv_params_from_set(params::SET_8192_1000_4)

Or in typescript:

encodeBfvParamsFromSet("SET_8192_1000_4")

which should use wasm to reach into rust and get the param set.

Metadata

Metadata

Assignees

Labels

ciphernodeRelated to the ciphernode package

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions