Skip to content

FEAT: Update Explorer UI to show fourth parameter when a token is created #203

@ccornick

Description

@ccornick

We took a guess as to what was needed to define a unique token. We use 3 parameters:

Orguid
Project ID
Vintage
We need to have a 4th parameter to define a token. The token driver already has a 4th field that is hardcoded, but will be changed to use a different CADT field.

We need the UIs in our various tokenization apps to reflect this new parameter being added to a token. This includes the tokenization engine UI, the explorer UI, and the climate wallet.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions