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
If you a deploy a Kernel contract (e.g. Version 0.2.2) and then try to verify a message while using a new version (e.g. 0.2.3) then the verification fails. The original Zerodev SDK supports this behaviour.
If you a deploy a Kernel contract (e.g. Version 0.2.2) and then try to verify a message while using a new version (e.g. 0.2.3) then the verification fails. The original Zerodev SDK supports this behaviour.
The Zerodev SDK uses
accountMetadata
to fetch the actual Kernel Version before signinghttps://github.com/zerodevapp/sdk/blob/10839ec8d8fd2150c03af8362dc968adc516d324/packages/core/accounts/kernel/createKernelAccount.ts#L541
I created a PR, that fetches the actual Kernel version in a similar way, before signing the message:
#328
Here an example to replicate:
The text was updated successfully, but these errors were encountered: