Goal
Explore in more detail how the metadata records on the profiles of named smart contracts look.
The fields we use in ENSAwards are:
- avatar
- docs
- compiled-metadata
- audits
You can look them up here → https://github.com/namehash/ensawards/blob/main/ensawards.org/data/protocols/contracts-types.ts#L26
I'd especially value some advice on the audits field as so far, I couldn't find any examples of the contract's profile having such a field defined.
Why
- Additional research requested by @lightwalker-eth here
- It would allow us to tighten our unit tests and thus have even more control over our contract-related data model.
Goal
Explore in more detail how the metadata records on the profiles of named smart contracts look.
The fields we use in ENSAwards are:
You can look them up here → https://github.com/namehash/ensawards/blob/main/ensawards.org/data/protocols/contracts-types.ts#L26
I'd especially value some advice on the
auditsfield as so far, I couldn't find any examples of the contract's profile having such a field defined.Why