Skip to content
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.

[Starkcheck] - Ensure amount/tokenId supports felt/Uint256 format #7

Open
CremaFR opened this issue Jan 24, 2023 · 1 comment
Open

Comments

@CremaFR
Copy link
Member

CremaFR commented Jan 24, 2023

Without having to store for each contract address the way it is supported

@CremaFR
Copy link
Member Author

CremaFR commented Jan 26, 2023

the way Uint256/felt coexist is painful to tracks Id or amount because there is no standard way to express a value.
Uint256 is specified as low and high but it is seens in the wild either as base10 integer or base16integer without context to tell how it should be interpreted in the trace.

This post on shaman talks a bit about it

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants