feat: add resolver tracking for MOOV2 early resolver support #108
Conversation
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
- Update ABI with new contract interface - Add Resolver and ResolverHistory entities - Add handlers for RoleGranted/RoleRevoked events (RESOLVER_ROLE only) - Add tests for resolver permission tracking State handling unchanged - getState() already calls on-chain, so past-liveness requests will return Proposed instead of Expired after the contract upgrade.
Reinis-FRP
reviewed
Feb 2, 2026
| "internalType": "uint256" | ||
| }, | ||
| { | ||
| "name": "proposalTime", |
Contributor
There was a problem hiding this comment.
This field would be added to the upgraded implementation, would that create issues in getRequest calls before the upgrade payload is executed?
Contributor
Author
There was a problem hiding this comment.
Yes, we need to upgrade the subgraphs after the contract upgrade
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.
State handling unchanged - getState() already calls on-chain, so past-liveness requests will return Proposed instead of Expired after the contract upgrade.