We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We're planning to use Dirk KMS(which uses this crypto library) for Operator remote BLS signing for BN254 curve.
What is the map to curve algorithm this library support for BN254?
Currently, some AVSs are using the "try and increment" algorithm for mapping to curve as described/written in the code link below https://github.com/Layr-Labs/eigensdk-go/blob/dev/crypto/bn254/utils.go#L36
If the library does not support it, any guidance on how to quickly add it? if it supports it, how do we enable it?
The text was updated successfully, but these errors were encountered:
You can use mcl::ec::tryAndIncMapTo. I don't know the specification of SetBytes in the original code; I expect that setBigEndianMod corresponds to it.
mcl::ec::tryAndIncMapTo
SetBytes
setBigEndianMod
using namespace mcl; using namespace mcl::bn; Fp t; t.setBigEndianMod(digest); G1 P; mcl::ec::tryAndIncMapTo(P, t);
But the sign of P.y is not fixed either. Fp::neg(P.y, P.y) would be needed to match the ModSqrt specification in the original code.
P.y
Fp::neg(P.y, P.y)
ModSqrt
Sorry, something went wrong.
No branches or pull requests
We're planning to use Dirk KMS(which uses this crypto library) for Operator remote BLS signing for BN254 curve.
What is the map to curve algorithm this library support for BN254?
Currently, some AVSs are using the "try and increment" algorithm for mapping to curve as described/written in the code link below
https://github.com/Layr-Labs/eigensdk-go/blob/dev/crypto/bn254/utils.go#L36
If the library does not support it, any guidance on how to quickly add it? if it supports it, how do we enable it?
The text was updated successfully, but these errors were encountered: