The Community Council is one of three councils elected by Pyth token holders. Its mandate is the community side of the network: ratifying grant programs, approving incentive campaigns, funding ecosystem growth initiatives, and managing the operational details of community engagement that don't touch the protocol's technical parameters.
What it decides
- Grant programs — size, criteria, and application process
- Incentive campaigns — developer bounties, growth programs
- Operational spend on community infrastructure
- Reporting and accountability for funded initiatives
How it differs from the other councils
The Pythian Council handles oracle parameters and the publisher set. The Price Feed Council handles feed listings. The Community Council handles the people side — onboarding new builders, supporting open-source contributors, growing developer relationships. The mandates are deliberately separate; the Constitution is the canonical source for each council's specific powers and limits.
Spend authority and limits
Routine community spend within the council's mandate is handled through OP-PIPs and executed via the council's multisig. Check the Constitution for the current member count, multisig threshold, and any spend caps that apply. Anything beyond that scope — large treasury allocations, structural changes — requires an EXC-PIP and a stake-weighted DAO vote.
Where to follow it on Pythscan
The /councils/community page has the current member roster, including any operations seat, and cycle history. /governance mirrors the Community Council section of the forum.