Mint and Token Confusion

[CyberCyclone]

The way the queries and tables were created is causing confusion in what they do.

E.g, When using Hasura I can see that there's a table called "Mint" which shows all the tokens that have been minted. Can we please have this exposed to GraphQL? As far as I can see, there isn't a reliable way of retrieving all the minted tokens with the correct quantities while using the "token" interface/table. E.g, you can do a distinct, but you can't order it by includedAt, so any selected "distinct" isn't guaranteed to be the minted transaction. Exposing "Mint" would solve this.

GraphQL has the "tokens" table exposed however this isn't a unique set of tokens and is actually all the transactions that have happened against a token. I feel like it would be more appropriate to call it token_transactions and token_transactions_aggregate.

[rhyslbw]

Yes you're right @CyberCyclone , the mint table holds the information we need to determine the supply.

I feel like it would be more appropriate to call it token_transactions and token_transactions_aggregate.

I'll sleep on it and work something out. We may be better off removing this query since it's associated via the transactions
directly, and the most natural way to know what tokens are in existence is via the UTxO set. Having access to a query that can aggregate the mint table data is the key improvement here.

Thanks again

[CyberCyclone]

The approach in the release of 4.0.0 works a lot better now. Thanks!