fix: validate cached ancestor expiry - #69
Merged
Merged
Conversation
Co-authored-by: OpenCode <opencode-noreply@coinbase.com>
leopoldjoy
marked this pull request as ready for review
July 27, 2026 13:41
Co-authored-by: OpenCode <opencode-noreply@coinbase.com>
awilliams1-cb
approved these changes
Jul 30, 2026
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
notAftermetadata for every ancestor during the cached-chain walkAudit finding
Addresses external finding #14.
Tests
forge fmt --checkforge test --match-path test/CertManager.t.sol(39 passed, 1 skipped)forge test(205 passed, 1 skipped)Size note
Production
CertManageris 24,508 bytes, leaving 68 bytes under EIP-170. Test/demo harnesses may still exceed the limit; the production contract remains within it.