-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create utilities and governance contract folders #418
Conversation
33ced49
to
f9cd3f8
Compare
c3ddc1f
to
cc7e07f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment about adding an additional generic utilities
folder, but otherwise LGTM. Also, I know that lowercasing the directory names was mentioned in the issue, but did we come to a conclusion on that? If we decide to move forward with that, we should do the same in avalanche-interchain-token-transfer
.
It was brought up in #404 and I think it makes sense overall. FWIW OZ uses lower cased directory names and ProperCase contract file names. I agree that if we did it here we should do the same in Overall LGTM. I just have one minor question below. |
@@ -1,6 +1,6 @@ | |||
## Utility Contracts |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that it makes sense to separate different logical groups in sub-directories but I'm not sure about the validators
name. Does anyone have a better idea? Maybe governance
? I think we are more likely to have another governance type contract that would make sense to group this with than a validator related one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
governance
sounds pretty good to me. Anyone else have any thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i like governance
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the original directory mockup on the #404 we agreed to keep Upgradeable files inside the teleporter
folder. Apologies for not copying it properly into the issue. I'm not opposed to keeping them here though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I do think it makes sense to keep TeleporterRegistry
and TeleporterUpgradeable
in the same spot. Would love to hear other opinions if anyone has one :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree we should keep them together, especially if we rename TeleporterUpgradeable
as discussed here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was originally thinking we'd put the registry contract under utilities
but keep the TeleporterUpgradeable
, etc under Teleporter
. Names aside, the registry is a standalone contract that isn't inherently tied to Teleporter itself (could be used a general account versioning mechanism controlled by the validator set). The TeleporterUpgradeable
contracts OTOH are abstract contracts that are tied to Teleporter in the sense that they import Teleporter interfaces and provide helpers specifically for sending and receiving Teleporter messages (by leveraging a registry instance).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I overall still feel it's a bit strange to classify TeleporterRegistry
and the other upgrades
contracts under utilities
, and the same for governance
files. Thinking if those can sibling directories to teleporter
or under teleporter
. That way we can also remove the need to have another utils
folder under utilities
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally looks good to me. I agree with some of the name change suggestions made by others, such as validators->governance.
I'd be okay having |
Definitely agree for |
48bcf29
to
633109e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Why this should be merged
closes #410
How this works
Reorganized directory structure.
How this was tested
Existing tests
How is this documented
Edited existing documentation.