-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
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
Generate Secp256k1 #46
Comments
hey @stormeye2000 . Can you share a deploy hash for which the SDK behaves as described? Thanks. |
hi @stormeye2000 , the deploy is correct. I see the problem is in this assert:
Last assert is checking public key algorithm for the validator account that proposed the block. It's not the taking a public key from the approvals object of a deploy, which seems to be the target. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
A Secp256k1 account is created and funded via the faucet account
A transfer is deployed with the new account as the approver
The deploy result is returned and the approval account is analysed
The signer contains the algorithm type ED25519
What did you expect to happen?
The signer contains the algorithm type Secp256k1
Thanks
Carl Norburn
The text was updated successfully, but these errors were encountered: