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

Lydia/bugs in InternalFunctionCall4 (formerly named InternalFunctionCall2) #267

Merged
merged 24 commits into from
Jun 10, 2024

Conversation

lydiagarms
Copy link
Contributor

There are bugs due to the fact that non-secret parameters are input to internal function calls but interact with global secrets within the function call. For example the non-secret parameters are not input to the proof or nullified during orchestration.

… interact with a secret only within the internal function call are marked as not interacting with the secret and so not input to the proof in the orchestration
@lydiagarms lydiagarms requested a review from SwatiEY May 13, 2024 17:31
lydiagarms added 22 commits May 14, 2024 10:19
…t state variable in orchestration and circuits
…ifying same secret state - specifically in the statements array where statements from internal functions are combined
…circuit but only used in an internal function call - this means that the same variable is declared twice
…ecause the fuction only interacts with the secret in the internal function calls
…ith secret not being counted as interacting with secret
@SwatiEY SwatiEY merged commit 5ae4310 into master Jun 10, 2024
2 checks passed
Copy link

🎉 This PR is included in version 1.5.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

2 participants