Yep mate you are right. I had this in mind. The reason i did not do it yet is because for my POC the Job request kind is very specific to a single example which is the proving of a Fibonacci sequence. The parameters don't really make sense for a generic scheme. I need to think about how to make a standard format for a Job kind that would be `ZK_GENERATE_PROOF` or something like this. Or maybe it's better to have different kinds depending on the type of proof and implementation, so for my case it would be more: `ZK_GENERATE_CIRCLE_STARK_PROOF`. Anyway, i am open to feedback and advise on this question.

GitHub

feat: Implement NIP-89 for DVM to Advertise ZK Proof Generation Services · Issue #11 · starkware-bitcoin/askeladd

Description We need to implement NIP-89 (Recommended Application Handlers) for our Data Vending Machine (DVM) to advertise its Zero-Knowledge (ZK) ...

No stress about it, just a general hint once you feel it's ready. I guess it could make sense to have single kinds for each proof, but it's also not my expertise. Would still be nice to see an example in markdown so it's easy for other implements (like my python framework) to communicate with your DVMs in a meaningful way :)