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
We currently parse all token types the same. This results in a merged entity that doesn't follow standards, e.g. ERC-721 tokens should have 0 decimals, but are returned as null.
We should have explicit validation schemas and associated entities based on the token type. These should have the correct fallback values, should anything be returned as null, e.g. native token having 18 decimals, ERC-721 having 0 decimals, etc.
Requirements
TokenSchema should be split into three: NativeTokenSchema, Erc20TokenSchem, Erc721TokenSchema with correct fallback values.
Swagger-specific entities created for each of the above, tagged correctly.
Description
We currently parse all token types the same. This results in a merged entity that doesn't follow standards, e.g. ERC-721 tokens should have 0 decimals, but are returned as
null
.We should have explicit validation schemas and associated entities based on the token type. These should have the correct fallback values, should anything be returned as
null
, e.g. native token having 18 decimals, ERC-721 having 0 decimals, etc.Requirements
TokenSchema
should be split into three:NativeTokenSchema
,Erc20TokenSchem
,Erc721TokenSchema
with correct fallback values.Additional information
The text was updated successfully, but these errors were encountered: