FLOW-5 - Clean up existing capability before granting new beta access #145
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
_cleanupExistingGrantfunction that deletes old capability controllers before issuing new onesgrantBeta()before creating a new capabilityThis prevents storage bloat and maintains an accurate audit trail when
grantBeta()is called for an address that already has beta access.Quantstamp Audit Finding
FLOW-5: GrantBeta Overwrites Existing Capability without Cleanup (Low)
When
grantBeta()is called for an address that already has beta access, the function was creating a new capability and overwriting the entry inissuedCapIDswithout deleting the old capability controller.Test plan
grantBeta()twice for the same address properly cleans up the old capabilityBetaRevokedevent is emitted when cleaning up old capabilityCloses #136
🤖 Generated with Claude Code