Brian Min

this has nothing to do with the plugin

I’m guessing that’s due to the limitation of flow contract updatability. In that case, NFTViewV2 sounds like the way to go. Maybe there should be some further discussions on other...

> @bymi15 Can you open a PR with this update? That would be a good place to have this discussion Thanks for your response @joshuahannan I have just raised a...

@PeterBenc I think the `thumbnail` field was intended more for small-medium sized images that can be displayed on websites. Totally agree that there should be a field that allows one...

The problem is that this is all tied in with NFTCatalog which uses NFTView: https://github.com/dapperlabs/nft-catalog/blob/main/cadence/contracts/NFTRetrieval.cdc#L99 Perhaps this could be raised in NFTCatalog - so they can support other metadata views...

@bshahid331 yeah that's true but I think it would be nice to include other views in `getNFTViewsFromCap`. Otherwise, we would have to write our own custom script to get the...

@PeterBenc Great. I’m glad it’s all sorted out for you. So i guess i’m going to close this issue since there shouldn’t be any blockers due to this.

@bjartek I agree with you. There could also be multiple options here depending on how much flexibility we want. a) a more generic **Person / User** style view with a...

I think we could go for a generic **Users** view but having a **UserType** enum to specify the type of a user. Enumerations seem good to me as we can...

Perhaps we could remove the PII (Personal Identifiable Information) and just include the bare minimum: `type` and `walletAddress`. Because that information should already technically be available on chain, but I...