-
Notifications
You must be signed in to change notification settings - Fork 208
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
Audit vaultFactory package for consistency #4415
Comments
This was filed at the request of @dtribble in late January when he had some thoughts on things to revisit.
I don't think that decision is in doubt. However "new information" on whether to make changes before Mainnet 1 is actually the output of this work, not the input. |
Example to come back to: fcdd7a0 |
Closing this because it seems to be done. |
Reopening because it's not done and it doesn't delay MN-1 because it's not scheduled for MN-1. |
What is the Problem Being Solved?
vaultFactory has grown somewhat organically and it's time to take a look holistically to tie it all together so that it's easy to comprehend and maintain.
Examples of things to look into:
-- invitations
-- AMM from vaultFactory to bootstrap
Description of the Design
Output of ticket will be proposal for design changes.
Security Considerations
n/a
Test Plan
n/a
The text was updated successfully, but these errors were encountered: