You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 9, 2024. It is now read-only.
add a method that takes an input (could be string, but probably will be bytes) then signs it using ECDSA method.
Motivation
Currently useInk WalletAccount class does not have a method that can generate a signature that can be verified using ink smart contract. Since ink only have ecdsa_recover method (as far as i know) to recover ecdsa siganture it will be nice to have a method that can make ecdsa signature that can be verified using ink's ecdsa_recover method.
Use Cases
meta transaction: user can sign for a transaction that can be run by another user, ex: address A signs a message/data for listing an nft at a marketplace (saved by backend), the user b can use that signature (given by backend) as a proof of listing A listing when buying that nft.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Feature Request
Suggestion
add a method that takes an input (could be string, but probably will be bytes) then signs it using ECDSA method.
Motivation
Currently useInk WalletAccount class does not have a method that can generate a signature that can be verified using ink smart contract. Since ink only have ecdsa_recover method (as far as i know) to recover ecdsa siganture it will be nice to have a method that can make ecdsa signature that can be verified using ink's ecdsa_recover method.
Use Cases
meta transaction: user can sign for a transaction that can be run by another user, ex: address A signs a message/data for listing an nft at a marketplace (saved by backend), the user b can use that signature (given by backend) as a proof of listing A listing when buying that nft.
The text was updated successfully, but these errors were encountered: