This proposal aims to improve development coordination within the Synthetix protocol, ensuring that decentralization does not lead to disorganization. By introducing a more structured approach to coordination and governance, this proposal increases clarity of responsibility and accountability for development work. The proposal takes lessons from traditional organizations, like singular responsibility and accountability to external stakeholders.
\nThis proposal introduces changes to protocol governance and organization; (a) the election of a Contributor Lead (CL) by the Spartan Council in place of the Core Contributor Committee to improve accountability, (b) assigning responsibility for protocol roadmap maintenance to the CL to ensure clear direction and focus, (c) instituting a regular funding schedule for Core Contributors (CCs) to maintain operational continuity, and (d) formalizing a dedicated support role to assist the SC and CL.
\nThe current governance and operation of Synthetix development faces challenges of clear accountability, and effective distribution of decisions and feedback. The creation of a roadmap, the election of core contributor leadership and how core contributors are funded and supported need clear ownership.
\nThe process for the creation of a protocol roadmap, currently managed by the Spartan Council following SIP-232, has not been effective. The protocol does not currently have a working and accountable governance structure to create milestones and deliver against them.
\nGovernance of Core Contributors is currently isolated from token holder influence, resulting in a disconnect between the protocol's largest capital allocation and token holder interests. Despite committed seat holders, the governance structure of internally elected Core Contributor Committee seats obscures accountability and diffuses responsibility.
\nThe funding process for Core Contributors, initiated by SIP-155, lacks a formal schedule, leading to an unclear cadence and adds unnecessary uncertainty.
\nCL Appointment:\nThis proposal changes the structure of Core Contributor governance; transition from a Core Contributor Committee (CCC) to a single Contributor Lead (CL) role, elected by the Spartan Council, in order to clarify accountability. The CL will be responsible for coordinating protocol development efforts with the roadmap approved by the Spartan Council, and ensuring that the incentives of contributors align with the long-term success of the protocol.
\nProtocol Roadmap:\nThe CL will take responsibility for drafting, maintaining, and updating the protocol roadmap, at the direction of the Spartan Council, to reflect the collective priorities of Synthetix governance. The CL is a facilitator, as decision-making for the roadmap content rests with the SC, and funding with the TC.
\nCC Funding:\nThe CL will prepare and maintain a detailed budget aligned with the roadmap, for TC review and funding. Funding will be provided each governance epoch, ensuring a minimum operational runway of three months.
\nCC Support:\nFormalize a support role to the CCs, responsible for implementing SC and CL decisions, and coordinating with the other governance bodies. This role exists informally already, but will be expanded to include coordination with SC and TC on budget and roadmap.
\nCL Appointment:\nA CL elected by the Spartan Council addresses the diffusion of responsibility and the lack of clear accountability that arises in decentralized systems of governance.\nRemoving shared responsibility for executing SC decisions makes accountability clear, as shared responsibility is a slippery slope to no one being responsible. Clear responsibility is how effective organizations operate, and decentralized organizations are no different in this regard.\nAppointment of leadership by an external body, rather than internal, is a well demonstrated model of corporate governance, and allows for the appointment of a replacement in instances of poor performance.\nThe CL will coordinate development effort, while ownership and delivery of SIPs will continue to reside with CCs.
\nProtocol Roadmap and CC Funding:\nBy assigning the roadmap development and funding responsibilities to the CL, there is a direct linkage between the strategic direction of the protocol and its operational execution and funding. This structure encourages a proactive, rather than reactive, approach to development.
\nCC Support:\nFormalizing the support role acknowledges the complexities of decentralized governance and the need for efficient coordination and execution of decisions by the SC and TC.
\nProtocol Roadmap: The CL is responsible for maintaining the roadmap determined by the SC in a public place, to be updated in the first month and reported against in the final month of each epoch.
\nCC Funding:\nEach governance epoch, the CL prepares a structured funding schedule and criteria for budget, to be reviewed and approved by the Treasury Council. CC funds are to be held in a 3/4 multisig, with the CL, the CC Support Role, and 2 TC members as signers.
\nCL Appointment:\nOn passing of this proposal, and then at the end of September and March, voting for the CL will take place via snapshot or similar tool. As a result, the expected tenure of CL epochs is 6 months. Any current CCs can nominate themselves in the second last week of the term, and one CL is elected by the SC in a single appointment, in the final week of the term.
\nCC Support:\nThe existing operational role with the CCs will become part of governance operations, and takes part in implementing the decisions of the SC, TC and CL.
\nN/A
\nN/A
\nCopyright and related rights waived via CC0.
"}},"pageContext":{"id":"26b0d270-c7f6-50f2-ae54-65dfde61b91a","frontmatter__sip":353,"__params":{"frontmatter__sip":"353"}}},"staticQueryHashes":[]}