This fixes #799 by updating the @zk-kit/eddsa-poseidon dependency and adds two methods to export/import encoded (base64) private keys.
The type of the private key in the Identity constructor has also been changed. Now, it must be one of the following: Uint8Array, Buffer, string, i.e. bytes or text, exactly the same as the types supported by @zk-kit/eddsa-poseidon.
This should eliminate the ambiguity of having a string that can be either text or hexadecimal, as it was before.
Related Issue(s)
Fixes #799
Checklist
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have run yarn format and yarn lint without getting any errors
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
Description
This fixes #799 by updating the
@zk-kit/eddsa-poseidondependency and adds two methods to export/import encoded (base64) private keys.The type of the private key in the Identity constructor has also been changed. Now, it must be one of the following: Uint8Array, Buffer, string, i.e. bytes or text, exactly the same as the types supported by
@zk-kit/eddsa-poseidon.This should eliminate the ambiguity of having a string that can be either text or hexadecimal, as it was before.
Related Issue(s)
Fixes #799
Checklist
yarn formatandyarn lintwithout getting any errors