fix: use blst backend to avoid conflict with FVM

Author: karlem

Cargo.toml

@@ -14,8 +14,12 @@ ahash = "0.8"
 anyhow = "1"
 base32 = "0.5.1"
 base64 = "0.22"
-blake2 = { git = "https://github.com/huitseeker/hashes.git", branch = "blake2x-pr", features = ["blake2x"] }
-bls-signatures = { version = "0.15" }
+blake2 = { git = "https://github.com/huitseeker/hashes.git", branch = "blake2x-pr", features = [
+    "blake2x",
+] }
+bls-signatures = { version = "0.15", default-features = false, features = [
+    "blst",
+] }
 bls12_381 = "0.8"
 cid = { version = "0.10.1", features = ["std"] }
 fvm_ipld_bitfield = "0.7.1"

blssig/Cargo.toml

@@ -12,7 +12,8 @@ rust-version.workspace = true
 [dependencies]
 blake2.workspace = true
 bls-signatures.workspace = true
-bls12_381.workspace = true
+blstrs = "0.7"
+group = "0.13"
 filecoin-f3-gpbft = { path = "../gpbft", version = "0.1.0" }
 hashlink.workspace = true
 parking_lot.workspace = true

blssig/src/bdn/mod.rs

@@ -13,7 +13,8 @@ use crate::verifier::BLSError;
 use blake2::Blake2xs;
 use blake2::digest::{ExtendableOutput, Update, XofReader};
 use bls_signatures::{PublicKey, Serialize, Signature};
-use bls12_381::{G1Projective, G2Projective, Scalar};
+use blstrs::{G1Projective, G2Projective, Scalar};
+use group::Group;
 
 /// BDN aggregation context for managing signature and public key aggregation
 pub struct BDNAggregation {
@@ -106,7 +107,7 @@ impl BDNAggregation {
             bytes_32[..16].copy_from_slice(chunk);
 
             // BLS12-381 scalars expects little-endian byte representation
-            let scalar = Scalar::from_bytes(&bytes_32);
+            let scalar = Scalar::from_bytes_be(&bytes_32);
             if scalar.is_some().into() {
                 coefficients.push(scalar.unwrap());
             } else {