chore(protocol-contracts): remove ProtocolOperatorRegistry #1535
+0
−149
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
🧪 CI InsightsHere's what we observed from your CI run for 536145f. 🟢 All jobs passed!But CI Insights is watching 👀 |
Collaborator
|
Was about to comment about this in #1482. Is there a plan on how to associate operators with their staking contracts? Is having that hardcoded somewhere acceptable long-term? |
Contributor
Author
@arr00 internally we've said we're not going to do this at first, but we can always add something later if needed ! |
melanciani
deleted the
melanciani/716/protocol-contracts/staking/remove_protocol_operator_registry
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
following work done in #1482 with respect to the owner changes, we believe the registry does not make much sens anymore
refs https://github.com/zama-ai/fhevm-internal/issues/716