Iāve enjoyed reading the discussion between you and @Amensch regarding āconflict of interestā, and I have to say I agree with both of you. Allow me to share how I see both sides of the issue, and how I believe the solution is already there.
I agree with @Amensch that we should not be overly restrictive regarding who we perceive as suitable candidates. Similar to the other two councils, we want individuals who can bring the most value to Pyth. Such individuals are often well-connected and likely to be involved in other projects in various capacities. As long as they are true believers in Pyth, I donāt think they should be excluded from our consideration. After all, strategic collaborations and partnerships (at the community level) seem to be one of the core functions of this council, and these individuals often have the necessary skillsets and connections to execute these functions well. As long as such initiatives/collaborations bring value to Pyth, such win-win situations are fine.
On the other hand, I understand the concerns highlighted by @N0name_trader. If a council member has a vested interest in another project, it becomes harder to discern their priorities and motivations. So for example, when proposing a possible partnership/collaboration, a council member may be tempted to āoversellā the benefits to Pyth, in order to secure a āgreater benefitā for that other project they represent, resulting in an inequitable or unbalanced arrangement. We want to avoid this, and I believe with certain mechanisms, this can be minimized and mitigated.
First, in the Code of Conduct H2, Para 2:
āEach Council Member shall promptly disclose in writing any actual, potential, or perceived Conflict of Interest to the Council, providing a detailed account of the facts and circumstances that raise the suspicion of such Conflict of Interest. Upon disclosure, the Council shall, by a simple majority vote of its remaining Council Members (excluding the disclosing Council Member), determine whether a Conflict of Interest exists.ā
As long as council members are held to this standard, it serves as a first layer of mitigation. The councilās plurality also prevents a single member from can acting against the best interests of Pyth. BUT this will only be achieved if we elect the right people - members who are able to think independently, critically and objectively, and genuinely seek the best interests of Pyth.
To make the system even more robust and decentralized, I would also suggest an additional consideration/restriction to the composition of the council, which could be something like this:
Out of the 7 council members, not more than two can hold key positions in the same external project, at any one time. (āKey positionsā could be defined as paid positions or any other way we want to define it.)
(cc: @Chop for my suggestion at the end)