Skip to content

Evaluate which contracts / files are to be deprecated #46

Description

@zerosnacks
  • Contracts that were never deployed
  • Contracts that are unused and should be deprecated
  • Contracts that are deprecated
  • Contracts that serve as examples

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 an examples 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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions