str4d / bls Goto Github PK

I just wanted to clarify the "yes, I know" comment in the README:

"It currently supports the BLS12-381 (Barreto-Lynn-Scott) (yes, I know) construction."

Is there something wrong with BLS12-381? :)

See also the TODO on whether to use projective or affine coordinates for the public key.

xxx@debian: cargo build
Updating git repository https://github.com/mmaker/pairing
Updating crates.io index
Downloading rand v0.3.22
Downloading libc v0.2.44
Downloading digest v0.7.6
Downloading blake2 v0.6.1
Downloading generic-array v0.9.0
Downloading typenum v1.10.0
Downloading digest v0.6.2
Downloading byte-tools v0.2.0
Downloading crypto-mac v0.4.0
Downloading generic-array v0.8.3
Downloading constant_time_eq v0.1.3
Compiling typenum v1.10.0
Compiling libc v0.2.44
Compiling nodrop v0.1.13
Compiling constant_time_eq v0.1.3
Compiling byte-tools v0.2.0
Compiling byteorder v1.2.7
Compiling rand v0.4.3
Compiling generic-array v0.8.3
Compiling generic-array v0.9.0
Compiling digest v0.7.6
Compiling crypto-mac v0.4.0
Compiling digest v0.6.2
Compiling blake2 v0.6.1
Compiling rand v0.3.22
Compiling pairing v0.14.0 (https://github.com/mmaker/pairing?branch=feature/hashing#69fe215d)
Compiling bls v0.0.1 (/home/mirco/Algorithms/bls)
error[E0061]: this function takes 1 parameter but 2 parameters were supplied
--> src/lib.rs:26:17
|
26 | let h = E::G1Affine::hash(HASH_KEY, message);
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected 1 parameter

error[E0061]: this function takes 1 parameter but 2 parameters were supplied
--> src/lib.rs:44:17
|
44 | let h = E::G1Affine::hash(HASH_KEY, message);
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected 1 parameter

error[E0061]: this function takes 1 parameter but 2 parameters were supplied
--> src/lib.rs:101:21
|
101 | let h = E::G1Affine::hash(HASH_KEY, input.1);
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected 1 parameter

error: aborting due to 3 previous errors

For more information about this error, try rustc --explain E0061.
error: Could not compile bls.

To learn more, run the command again with --verbose.

Section 4.2 of the BLS paper outlines how to use the x-coordinate of the "signature point" as the signature itself. It requires reconstructing the point during validation, and then an additional pairing check.