diff --git a/src/App.tsx b/src/App.tsx index 2464b54..bc3ca3d 100644 --- a/src/App.tsx +++ b/src/App.tsx @@ -33,6 +33,7 @@ const Grants = lazy(() => import('./pages/Grants')); const CaseStudies = lazy(() => import('./pages/CaseStudies')); const Careers = lazy(() => import('./pages/Careers')); const About = lazy(() => import('./pages/About')); +const Governance = lazy(() => import('./pages/Governance')); const Vitals = lazy(() => import('./pages/Vitals')); const Security = lazy(() => import('./pages/Security')); const Status = lazy(() => import('./pages/Status')); @@ -138,6 +139,14 @@ export default function App() { } /> + + + + } + /> + maintainerRoles.includes(member.role) && + (!member.github || !optOutData.includes(member.github.replace('https://github.com/', ''))), + ); + + return ( +
+

Governance

+ +
+

+ Decision-Making Process +

+

+ Wraith Protocol operates on a Drips-funded contributor model. Decisions are driven by + community proposals, discussions, and consensus among core maintainers. Proposals are + drafted on our forums and refined before moving to implementation. Anyone can propose a + change, but significant protocol upgrades require rigorous review and consensus. +

+
+ +
+

+ Maintainer List +

+

+ Our core maintainers are responsible for reviewing pull requests, ensuring code quality, + and merging changes to the main branch. Maintainers have opted into this listing. +

+
+ {maintainers.map((maintainer) => ( +
+ {maintainer.name} +
+

{maintainer.name}

+

{maintainer.role}

+ {maintainer.github && ( + + GitHub + + )} +
+
+ ))} +
+
+ +
+

+ Wave Scoping Process +

+

+ Waves represent phases of funding and development focus. The scoping process involves + gathering input from contributors and institutional partners, prioritizing features based + on our roadmap, and allocating the Drips funding accordingly. Detailed wave scopes are + published before each development cycle begins. +

+
+ +
+

+ Dispute & Escalation Path +

+

+ In the event of a disagreement regarding technical decisions or wave scoping, issues are + escalated to a dedicated dispute resolution committee composed of senior maintainers and + advisors. The goal is always to reach a consensus, but if a deadlock occurs, the Lead + Protocol Architect has the final say to ensure project momentum. +

+
+ +
+

+ Mainnet Parameter Change Process +

+

+ [Placeholder] The process for changing mainnet parameters is currently under design. It + will likely involve a timelock and multi-sig authorization, transitioning towards more + decentralized governance as the protocol matures. +

+
+ +
+

Get Involved

+

+ Interested in contributing or applying for funding? Check out our{' '} + + Grants + {' '} + program and see our{' '} + + Contributors + {' '} + page. +

+
+
+ ); +}