We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@AbdelStark In this PR #23, I have started a generic job request to prove something into a different Internal program of Askeladd.
Let's continue, I think to have a basic implementation for the MVP we need:
TODO:
Continue proposal of the architecture of a different kind of the ZK DVM (5600, 6600 and few coming).
Add JOB_LAUNCH_PROGRAM Kind 5700 or 5XXX. Needed for a developer to launch their program with a good structure to be handled by Nostr users as a DVM.
JOB_LAUNCH_RESULT of ASKELADD DVM for a program: verify the program, upload, endpoint, test inputs and config, and save and approve if it's ok.
NIP 78 and NIP-94 and 96 to launch your program: Endpoint, Ipfs, HTTP FILE in Nostr... Checking and iterating between different options possibles
Add others parameters required on the JOB_REQUEST to prove, and also on the JOB_LAUNCH to setup the program need and upload it
Change the NIP-89 for Askeladd DVM Marketplace. Add NIP-89 for Program of the Marketplace too.
Program params: Input types and Input encrypted need to be added to fix some issue.
An IP for STWO program WASM to be easily integrated into ASKELADD
Documentation with Markdown and on the frontend to:
Request a prove/verify
Launch your program
Interact with ASKELADD
The text was updated successfully, but these errors were encountered:
No branches or pull requests
@AbdelStark
In this PR #23, I have started a generic job request to prove something into a different Internal program of Askeladd.
Let's continue, I think to have a basic implementation for the MVP we need:
TODO:
Continue proposal of the architecture of a different kind of the ZK DVM (5600, 6600 and few coming).
Add JOB_LAUNCH_PROGRAM Kind 5700 or 5XXX. Needed for a developer to launch their program with a good structure to be handled by Nostr users as a DVM.
JOB_LAUNCH_RESULT of ASKELADD DVM for a program: verify the program, upload, endpoint, test inputs and config, and save and approve if it's ok.
NIP 78 and NIP-94 and 96 to launch your program: Endpoint, Ipfs, HTTP FILE in Nostr... Checking and iterating between different options possibles
Add others parameters required on the JOB_REQUEST to prove, and also on the JOB_LAUNCH to setup the program need and upload it
Change the NIP-89 for Askeladd DVM Marketplace. Add NIP-89 for Program of the Marketplace too.
Program params: Input types and Input encrypted need to be added to fix some issue.
An IP for STWO program WASM to be easily integrated into ASKELADD
Documentation with Markdown and on the frontend to:
Request a prove/verify
Launch your program
Interact with ASKELADD
The text was updated successfully, but these errors were encountered: