# Quantus post-quantum crypto, compiled to WASM for the browser. # # Deliberately a separate crate from `wasm-crypto` rather than more files inside # it: that package is built with `nightly-2022-06-24` (see scripts/rust-version.sh) # against a 2019-era dependency set, and the ML-DSA crates use inline `const {}` # blocks that need Rust >= 1.79. The two cannot share a Cargo graph, and bumping # the older one would mean rewriting upstream's sr25519/ed25519 build — which is # the thing we most want to leave alone so rebases stay boring. See quantus/wasm#1. [package] authors = ["Quantus Network Developers "] description = "WASM bindings to the Quantus chain's post-quantum crypto crates." edition = "2021" license = "Apache-2.0" name = "quantus_crypto" publish = false repository = "https://git.lair.cafe/quantus/wasm" resolver = "2" version = "0.0.0" [lib] crate-type = ["cdylib", "rlib"] [dependencies] # The crates the runtime itself uses. Versions match quantus-apps/quantus_sdk's # rust bridge, which is the other non-Rust consumer of exactly this surface. qp-poseidon-core = "3.1.0" qp-rusty-crystals-dilithium = { version = "4.1.1", default-features = false, features = ["ml-dsa-65", "ml-dsa-87"] } qp-rusty-crystals-hdwallet = { version = "4.1.1", default-features = false, features = ["ml-dsa-65", "ml-dsa-87"] } wasm-bindgen = "0.2" [dev-dependencies] # The chain's own nullifier, for known-answer tests only. It pulls in plonky2, # which has no place in the shipped WASM: the port in rs/hdwallet.rs has to # agree with it, and these tests are how that is shown rather than asserted. qp-wormhole-circuit = { version = "=4.3.0", default-features = false, features = ["std"] } qp-zk-circuits-common = { version = "=4.3.0" } [profile.release] codegen-units = 1 debug = false debug-assertions = false incremental = false lto = true opt-level = "z" panic = "abort" rpath = false