Skip to content
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

Change proof encoding from an array of uint256 values to a bytes value #450

Open
corydickson opened this issue Jun 8, 2022 · 2 comments
Labels
question Further information is requested

Comments

@corydickson
Copy link
Contributor

No description provided.

@ctrlc03 ctrlc03 added the question Further information is requested label Nov 17, 2023
@ctrlc03
Copy link
Collaborator

ctrlc03 commented Dec 15, 2023

@corydickson Would you mind expanding on the benefits of this please?

@corydickson
Copy link
Contributor Author

I believe the intention behind this issue was to discuss the gas savings of using converting some of the proof inputs that are stored in the contracts to no longer use uint256 to byte arrays. The limitations would be to be sure those conversions are handled in the toolchain when generating proofs or validating the state of the contracts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants