-
Notifications
You must be signed in to change notification settings - Fork 3
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
Evaluate which contracts / files are to be deprecated #46
Comments
Fuse safe liquidator can be primarily seen as backup liquidator that we use for niche assets that may have patterns such as unstaking before liquidating, in the event that our typical liquidators don't have ready made patterns. I think this would be good in an |
Clear, are there any other files you can think of that would be in a similar situation? Are we still supporting all the oracles in Edit: I did find https://github.com/Rari-Capital/RariSDK/blob/master/src/Fuse/addresses/mainnet.ts so I'll check there |
I went through all the files in |
In Marked as unused / not deployed
Unknown (not listed in addresses)
|
I still think all of these should remain where they are, all of the "unknown" are in use |
Clear, would it be a good idea that we would add these missing oracles to the list on https://github.com/Rari-Capital/RariSDK/blob/master/src/Fuse/addresses/mainnet.ts just to make sure we don't lose track of them? I think other than that we can close this ticket as there are no actionable items that I can see. |
We should evaluate how we ought to go about deprecating deployed contracts.
We need to make sure the contract in question has no roles, isn't an admin of any contract, and will definitely not be accidentally used / referenced in the future.
I suggest we create a
deprecated
directory to hold any contracts that are deprecated. If files merely serve as an example I suggest we put them in anexamples
directory with some documentation. If the file is part of the codebase but never deployed to mainnet we could evaluate whether to remove it from the codebase.Once we have this sorted we should update the documentation to reflect the changes.
The text was updated successfully, but these errors were encountered: