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
Naming wise, this is misleading, because the return value is actually the signature itself, not the hash that is being signed over. A better return type would be Hex. Technically both Hash and Hex are implemented as the template literal type 0x{string} , but their naming carries additional connotation.
How to reproduce:
Relevant code or sample repro:
The text was updated successfully, but these errors were encountered:
Thanks for filling out this bug report. Please provide as much detail as possible.
If your issue is with our RPC APIs and not the SDK please report your issue on (discord)[https://alchemy.com/discord].
[REQUIRED] Environment
[REQUIRED] Describe the problem
The return type of
signTypedData
is aPromise<Hash>
, where Hash is the type defined by viem. https://accountkit.alchemy.com/packages/aa-accounts/light-account/signTypedData#promisehashNaming wise, this is misleading, because the return value is actually the signature itself, not the hash that is being signed over. A better return type would be Hex. Technically both Hash and Hex are implemented as the template literal type
0x{string}
, but their naming carries additional connotation.How to reproduce:
Relevant code or sample repro:
The text was updated successfully, but these errors were encountered: