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
The acir artifacts are currently being base4 encoded because they are included in the ABI.json file.
For backend end to end tests, they don't need to have a base64 encoded file since they just get the raw bytecode and not the json file.
base64 decode file before saving it in .bytecode
No response
No
The text was updated successfully, but these errors were encountered:
rebuild.sh
cc Tooling @kobyhallx @TomAFrench @jonybur @phated
Is base64 encoding no longer needed for the E2E workflow with barretenberg (bb.js)?
Sorry, something went wrong.
Nope, we're passing just the circuit rather than the full JSON artifact so we can pass binary.
Successfully merging a pull request may close this issue.
Problem
The acir artifacts are currently being base4 encoded because they are included in the ABI.json file.
For backend end to end tests, they don't need to have a base64 encoded file since they just get the raw bytecode and not the json file.
Happy Case
base64 decode file before saving it in .bytecode
Alternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
No
Support Needs
No response
The text was updated successfully, but these errors were encountered: