-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
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
Frontend marketplace #6
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
…bed to all relayers
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Draft PR to close #5
@AbdelStark
ETA for later today when I fix the last bug I hope.
WIP: STWO WASM Proof verification after receiving the Stark Proof.
Error encountered in the verification of the StarkProof and the run_verify_exemple I wrote.
Error: Proof generation failed: OodsNotMatching
Even looping with all StarkProof gives me this error. Maybe not a fetchEvent issue but a fib.verify(stark_proof) issue.
What I have now as an error:
Nostr Integration
[V] Install and set up the @rust-nostr/nostr-sdk package
[V] Initialize the Nostr client in the application
[V] Implement connection to Nostr relays
[] Handle Nostr client errors and connection status
NIP-90 Job Request Submission
[V] Implement the submitJob function to create and publish a NIP-90 Job Request event
[V] Use the correct event kind (5600) for Job Requests
[V] Include necessary tags (log_size, claim, output) in the Job Request event
Job Result Retrieval
[V] Implement the waitForJobResult function to listen for Job Result events
[V] Use the correct event kind (6600) for Job Results
[V] Parse the Job Result event content to extract the proof
STWO Proof Verification
[V] Integrate STWO WebAssembly module for proof verification
[X] Implement the verifyProof function using STWO WASM:
Verify error with every StarkProof on the Nostr relayer.
WIP using StarkProof as a string serialize, can't send it as an input on wasm_bindgen function.
[X] Handle the verification result and update the UI accordingly
Error: Proof generation failed: OodsNotMatching
UI Enhancements
[] Add error handling and display error messages to the user
[] Improve loading states and transitions between different stages of the process
[] Enhance the display of the proof and verification result
Additional Notes
[] Ensure proper error handling throughout the application
[] Consider implementing a more robust state management solution (e.g., React Context or Redux) as the application grows
[] Add unit tests for critical functions, especially those interacting with Nostr and STWO WASM
[] Document any configuration steps required for setting up the development environment