Closed jw-pyo closed 6 years ago
I think 2 is the most convenient way. However, we just have few deploying contracts which need ownership and they need different ownership. So, we should divide them strictly. IncentivePool : just controlled by address of Fund.sol ( X need Ownable, just local modifier) Tokens : doesn't need CrowdSale : developers Fund : developers VotingFactory : developers Votings : I think they don't need. Just make local modifier which controlled by Factory.
So, we just need one Ownable contract which controlled by on owner and developers. Perhaps, this contract would be created with their team wallet which could be multi-sig contract wallet.
Done new Members.sol : control dev members and owner Ownable.sol : just modifier, import Members members
In our current code work, we use the ownership contract(Ownable.sol) as follows.
However, I think we would fix this structure in our ICO2.0 system, using global ownership, not inheritance because of following reasons:
}