Skip to content
This repository has been archived by the owner on Dec 30, 2024. It is now read-only.

Consider refactoring into ~4 contracts (or more) #48

Open
GriffGreen opened this issue May 1, 2017 · 0 comments
Open

Consider refactoring into ~4 contracts (or more) #48

GriffGreen opened this issue May 1, 2017 · 0 comments

Comments

@GriffGreen
Copy link
Member

I think that some of these features may not want to be used by all users...

We might consider refactoring the code to have the core functionalities that are mandatory (I would suggest keeping the whitelistTimeLock as the most basic contract, the childVault stuff as an extension, the limits as an extension, and the open close time as an extension.

I know this is much easier said than done... but it would make the contracts much easier to understand and would allow people that don't want to include certain features to avoid deploying the extra code

This is a major design change. I expect a good healthy debate in this thread :-D

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant