Abdel on Nostr: Yep mate you are right. I had this in mind. The reason i did not do it yet is because ...
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.
https://github.com/AbdelStark/askeladd/issues/11
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.
https://github.com/AbdelStark/askeladd/issues/11