The blst_derive_child_eip2333 function uses a fixed version of keygen. If you need the ability to derive child keys using blst_keygen_v3 for example, you have to manually invoke the parent_SK_to_lamport_PK function.
The issue is that bindings to parent_SK_to_lamport_PK are not present, so doing this from Rust is impossible without reimplementing the code (which would not be performant). This could be fixed by either exporting bindings for parent_SK_to_lamport_PK (simpler) and/or by making a blst_derive_child_eip2333 function for each version, similar to blst_keygen.
The
blst_derive_child_eip2333function uses a fixed version ofkeygen. If you need the ability to derive child keys usingblst_keygen_v3for example, you have to manually invoke theparent_SK_to_lamport_PKfunction.The issue is that bindings to
parent_SK_to_lamport_PKare not present, so doing this from Rust is impossible without reimplementing the code (which would not be performant). This could be fixed by either exporting bindings forparent_SK_to_lamport_PK(simpler) and/or by making ablst_derive_child_eip2333function for each version, similar toblst_keygen.