feat: Add constraint =
attribute to #[light_accounts]
macro
#1217
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.
Similarly to Anchor's
constraint =
attribute, it can be used to ensure constraints for the given accounts. The constraint can use both regular and compressed accounts.The most common use-case for it is ensuring the equality of public keys across regular and compressed accounts for security checks.
DNS example is updated to use it for ensuring that compressed
NameRecord
accounts can be modified only by original signers, withconstraint = record.owner == signer.key()
.