dorgtech/homebase-indexer

homebase-indexer's Issues

Better Token Metadata Fetching

Context

Sometimes, BCD's API won't properly serve token metadata. This causes some DAOs to be lost or not indexed.

Take for example, this FA2 contract: KT18quSVkqhbJS38d5sbRAEkXd5GoNqmAoro

If you take a look at its tokens: https://better-call.dev/mainnet/KT18quSVkqhbJS38d5sbRAEkXd5GoNqmAoro/tokens, it properly shows a token with its metadata. However, if you query for it, through its API: https://api.better-call.dev/v1/contract/mainnet/KT18quSVkqhbJS38d5sbRAEkXd5GoNqmAoro/tokens, it comes back empty.

I discovered in their repo that they have multiple API URIs, and their website probably uses this one: https://white.better-call.dev/v1 which actually works (https://white.better-call.dev/v1/contract/mainnet/KT18quSVkqhbJS38d5sbRAEkXd5GoNqmAoro/tokens).

So I temporarily hotfixed this by querying the regular API first, and if the response is empty, query the second one as backup.

TODOs

• Research what's the best way to fetch the governance token's metadata. The best case scenario is a general one-case-fits-all solution
• Look into BCD's APIs and reach out to their team to see why this is happening

DAOs should return an "latestUpdate" key

Each DAOs should have a "latestUpdate" timestamp key in order to know when was the latest updated of given DAO.

• Update the field each time the DAO is being updated
• Return the Field in DAO details and DAOs list