add Contract Requirements for Unsealing to Permits page#117
Open
add Contract Requirements for Unsealing to Permits page#117
Conversation
toml01
reviewed
Jun 26, 2025
Contributor
There was a problem hiding this comment.
@laurenmxv what is this PDF for? I think it is an exact copy of this?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new section to the Permits Management documentation explaining the contract-side requirement to call
FHE.allow(...)when returning encrypted values to users.Why
During the most recent hackathon, developers encountered
ACLNotAllowederrors when attempting to unseal data, not realizing that contracts must explicitly grant access to ciphertexts. This section adds clarification about contract-side obligations.Changes
Contract Requirements for Unsealingsection before "Sharing Permits"