Either a new NIP or a section within NIP-34 so the protocol is clear and it is easy for clients to implement if they wish. I see the 'release artifact set' in the 'Examples' section of NIP-51 but there is more to the protocol than that. There are three aspects: 1) application profile event, 2) release event 3) trust attestations I started to draft something and that process brought up some questions and scenarios it might be worth discussing.

Why is there overlap? relating releases to their underlying code repository is both logical and provides improved trust heuristics. Obtainium is a good example of this. It would seem odd to have duplicated and disconnected release events, for the same app for app stores and code repositories. It won't take much to relate application profile events to NIP-34 announcement events. There are a few ways it could be done. The beauty of nostr is that clients could make this connection front and centre or ignore it completely.

Want to join our telegram group and discuss it there?

Telegram

zap.store developers

Did you check out the sample events? App profile events are kind 32267 used in zap.store and will become a NIP! And for trust attestations, are you following the NIP-77 discussion?

Absolutely, they should be connected