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
the result contains a JSON with the asset information, here are the details about each prop:
19
+
| Property | Description |
20
+
|----------|-------------|
21
+
| assetId | Actual ID of the asset |
22
+
| contractId | Contract ID that minted the asset |
23
+
| subId | SubId used to calculate the assetId |
24
+
| name | Asset name |
25
+
| symbol | Asset symbol |
26
+
| decimals | Asset decimals configuration |
27
+
| suspicious | true if symbol matches any verified asset symbols |
28
+
| metadata | Key-value object with SRC7/SRC9 standard metadata |
29
+
| isNFT | true if asset is NFT ( [supply=1, decimals=0](https://docs.fuel.network/docs/sway-standards/src-20-native-asset/#non-fungible-asset-restrictions) )|
30
+
| verified | true if asset is in Fuel's verified assets list |
31
+
| owner | Current assetId owner (NFTs only) |
32
+
| uri | Parsed URL from “metadata.uri” or “metadata.URI”. Some [logic](https://github.com/FuelLabs/fuel-ex-demo/blob/ee73408a0ef0323eeb92414d5ed92d65e3f3f78f/packages/graphql/src/infra/gateway/AssetGateway.ts#L63-L95) is applied to try defining a reasonable uri for the API consumer |
0 commit comments