-
Notifications
You must be signed in to change notification settings - Fork 316
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
Ensure sandbox/aztec.js errors are clear #1115
Comments
Sync with @rahul-kothari on the error codes page for circuits errors, we may be able to reuse efforts from there |
Ah thanks for adding me to this. @PhilWindle I added some common circuit errors here - https://github.com/AztecProtocol/aztec-packages/blob/master/docs/docs/aztec/protocol/errors.md includes stuff like "you have too many read requests/created too many commitments...." |
Closing this issue. The outstanding tasks are quite involved so I don't think we should rely on them being completed to release the sandbox. |
Look for obvious errors that will be made by developers (forgetting to add an account/public key for example) and ensure we give them as much help as possible.
Ensure errors are propagated out to aztec.js.
Tasks
AztecRpc
server never returns outdated info #1222compute_note_hash_and_nullifier
#1229send
method check whether origin address is registered #1230The text was updated successfully, but these errors were encountered: