-
Notifications
You must be signed in to change notification settings - Fork 0
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
Initial version 1 #1
Conversation
- fix memory trace file error
README.md
Outdated
`trace.bin`: Execution trace of the Cairo program. | ||
`memory.bin`: Memory dump of the Cairo program execution. | ||
`proof.json`: The generated STARK proof. | ||
`pie.zip`: Cairo PIE (Program Independent Executable) that can be generated by running the program and can be used re run the file in standardised way without inputs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should add that this is only for debugging purposes or if you're using SHARP
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually, maybe we can remove it as well? how do you suggest to use the PIE for debugging?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sometimes, if you have errrors while running the pie, they could potentially debugged faster than facing that while prooving it with sharp. That happended once with me if I remember correctly.
- Added the note in readme
Co-authored-by: Apoorv Sadana <95699312+apoorvsadana@users.noreply.github.com>
Co-authored-by: Apoorv Sadana <95699312+apoorvsadana@users.noreply.github.com>
…enerator into currentChanges
add clap for args
…enerator into currentChanges
This adds initial version for the proof generator