Nip90 params are defined in the kind definitions on the nip90 repo.
The others haven't been defined. I made a PR to Nip90 with some meaningful ones recently but nothing happened so far with it. 😅
nostr:npub1nxa4tywfz9nqp7z9zp7nr7d4nchhclsf58lcqt5y782rmf2hefjquaa6q8 nostrdvm lets you specify 'params', but is this defined anywhere in nip-89? nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft I know vendata.io will show fields based on the 'params' of the nip-89 for a dvm? Did you just decide to do this or is it based on a NIP somewhere?
Discussion
Ah I totally confused myself, thought it would have been under nip-88; thanks!
Autocorrect… nip-89
when you say kind definition, do you mean they are defined in the job request event (kind 5xxx)?. Am I correct in understanding that there is no global 'params' structure per kind? The way nostrdvm does it is that in a DVM's nip-89 announcement, that DVM specifies their 'nip90Params' right?
I just want to confirm this. It's a huge plus for the protocol if DVMs define their own params and there is no global definition that is forced upon everyone.
I'm bringing this up because other decentralized AI approaches have tried to force input / output structure of ai services