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
Describe the bug
I believe a bug was introduced in #1143 for v6.10.
bigints no longer validateAndParseAddress due to the change in addAddressPadding and always throws Invalid Address Format. i believe this was due to the toHex being done after adding a hexprefix
Describe the bug
I believe a bug was introduced in #1143 for v6.10.
bigints no longer
validateAndParseAddress
due to the change inaddAddressPadding
and always throwsInvalid Address Format
. i believe this was due to the toHex being done after adding a hexprefixhttps://github.com/starknet-io/starknet.js/pull/1143/files#diff-ca62a13994aae3c545ad2d796d272f3ee8c0ab33b83bb3d5c023dc553b55f984
To Reproduce
validateAndParseAddress(2368576823837625528275935341135881659748932889268308403712618244410713532584n)
throws
Expected behavior
return 0x053c91253bc9682c04929ca02ed00b3e423f6710d2ee7e0d5ebb06f3ecf368a8
Screenshots
NA
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: