Still skeptical on things like that.
I don't know if attesting is needed is you already know I'm **using** (or interacting in other ways with) specific events → Specs in this case.
We're starting with specifying the Specs we use in our App Releases and App events, for example.
What is my incentive to then also attest for them?
Yeah, one is emergent based on observations of given events. An app could harvest that info for sure.
Attestation approach more formal I guess, without the need for git.
Git repos for protocol specs looking pretty stoneage right now.
To boost the signal.
But signal has to mean something by definition.
Like for app releases, I want a 3rd party dev I trust to Attest to it the release of another dev. Not just hash of the image, but actually read the code.
