TIP-30 Native Token Metadata Standard

[lzpap]

Defines a JSON schema for token metadata format and validation.

Rendered version

[nicole-obrien]

We currently have the following additional properties on the base token metadata for the network:

• subunit: the unit of the smallest decimal value
• useMetricPrefix: determines if this token can be displayed with prefixes for the multiples of a 1000.

Are these something we also want to have in this standard?, and then we can also make the base token adhere to this standard too.

[lzpap]

We currently have the following additional properties on the base token metadata for the network:

• subunit: the unit of the smallest decimal value
• useMetricPrefix: determines if this token can be displayed with prefixes for the multiples of a 1000.

Are these something we also want to have in this standard?, and then we can also make the base token adhere to this standard too.

The base token of the network is distinct from native tokens in many respects:

• different utility in the core protocol
• different representation in outputs
• even different resolution (64bit vs 256bit)
• unit and subunit are special for the bas token because we want to give the smallest possible denomination a name, while with native tokens this is not usually the case

Therefore, I don't think we need to use the Native Token Metadata Standard explicitly for describing the Base Token of the network. With TIP-30 we were inspred by ERC20 and ERC1155 metadata conventions, let's not make our custom one mandatory. You may add these fields to your metadata if needed, at least IRC30 let's you define additional fields.