Arbitrary custom data that can be stored on-chain
The token IDs corresponding to the URI.
The URI where to fetch the token metadata from.
Deep copies the object and returns a new instance.
Converts the object to a different NumberType equivalent.
Optionaloptions: ConvertOptionsCompares this object's fields to another object's fields for equality. Equality is determined by comparing the JSON representations of the objects.
If normalizeNumberTypes is true, then all number types will be compared as strings (i.e. "1n" === "1" === 1). Else, they will be compared as their native types (i.e. 1n !== 1 !== "1").
OptionalnormalizeNumberTypes: booleanInternal helper method to convert the number fields of the object to a different NumberType equivalent.
Checks if the object has number fields.
Converts the object to a JSON object with all primitive types.
Converts the object to a JSON string.
StaticfromOptionaloptions: Partial<JsonReadOptions>StaticfromOptionaloptions: Partial<JsonReadOptions>StaticfromStaticgetGet first matches for the token metadata (i.e. if there are duplicated token IDs, we take the first match in a linear search).
TokenMetadata is used to represent the metadata for a range of token IDs. The metadata can be hosted via a URI (via uri) or stored on-chain (via customData).
We take first-match only for the token IDs. If a token ID is in multiple TokenMetadata, we take the first match in a linear search.