xGov Council meeting #4

*This AI-generated summary covers xGov Council meetings, which are unofficial and independently organized by the council. It offers a transparent view of their work and initiatives to enhance the xGov program. These notes are provided as-is, and it’s understood that some topics may not be fully clear without prior context.

4*th council meeting Oct 29th 2025*

Progress Review

Meeting Notes and Public Transparency

  • There was consensus to start with a anonymized, concise, less wordy version to maintain clarity and ease of consumption by the community.

Funding Structure

  • Discussions with the Algorand Foundation reveal no major changes expected in funding policies in 2024, and a strong preference for dispersing funds efficiently.

  • The current max ask of 200k ALGO per proposal might be increased in the future.

  • Discussions with community suggest raising the ask cap to 500k ALGO and adding the condition of open sourcing the project after approval for large proposals.

  • Council members support this conditional open source model to encourage funding.

Proposal Buckets and Funding Categories

  • Current funding is restricted to retroactive open source projects.

  • To broaden ecosystem support, the idea of splitting into multiple funding buckets was discussed: existing retroactive open source bucket, a new bucket for maintenance costs that would not require projects to be open source, and a proposed but currently rejected proactive funding bucket without immediate open source requirements.

  • The council agreed on the usefulness of a maintenance bucket without open source demands while recognizing foundation reluctance to remove open source requirements outright.

Discussions on Open Source Requirement

  • Various members debated the merits of the open source requirement, highlighting that while open source is valuable, it is not always practical for funding ongoing or closed-source projects that still benefit the ecosystem.

  • council speculates that the foundation pushes open source largely due to metrics visibility to satisfy larger stakeholders.

  • There was support for a middle ground licensing model, with some members highlighting that open source doesn’t guarantee community maintenance.

  • Overall, the council expressed preference for flexibility in open source requirements, especially conditional post-approval open sourcing.

Micro Grant and Ecosystem Development Strategy

  • Proposal to request a monthly budget to be managed proactively by the council or a separate working group to fund small ecosystem improvements like microgrants, marketing, or liquidity improvements.

  • The approach aims to increase voter engagement by having a continuous flow of proposals and demonstrate the council’s ability to responsively allocate funds.

  • Idea supported by council to start with conservative allocations desiring progress proof before scaling up.

Quorum and Voting Process Challenges

  • Current system’s quorum challenges related to low voter turnout and possible malicious votes from a few entities controlling multiple addresses were discussed.

  • Proposed solutions include batching proposal submissions and votes into fixed monthly cycles to improve predictability and engagement.

  • The meeting stressed the importance of having regular voting cadence over arbitrary rollovers for fairness and efficiency as-well as coordinated marketing efforts.

Managing Active Xgov Membership and Risks

  • Concerns were raised about aggressive removal of inactive Xgov members possibly causing overly small governance pools, increasing risk of Sybil attacks.

  • A risk-benefit analysis showed the council leaning strongly towards pruning inactive Xgov members to maintain quality governance even if total numbers reduce.

  • Incentive ideas such as rewards for active Xgov members to encourage engagement were discussed.

Challenges and Pivots

Open Source Requirement as a Blocker

  • The foundation appears firm on requiring open source for funding, which may prevent important maintenance or closed-source projects from receiving funding.

  • Legal hurdles and prolonged approvals are expected for any attempt to remove or relax the open source constraint.

  • Council members suggest a pivot to conditional open sourcing post funding approval, which may be more acceptable.

Quorum and Voting Participation

  • Current quorum rules and asynchronous proposal voting presents coordination and governance challenges, allowing groups with multiple addresses to jeopardize quorum legitimacy.

  • Lack of proper UI visibility of quorum numbers and vote status complicates transparency.

  • There is a need to formalize stricter activity requirements, but caution about possible reduced governance participation must be balanced.

Funding Allocation and Management Expertise

  • Implementing a council-managed treasury fund or working group for proactive allocations is conceptually sound but complicated by the council’s self-proclaimed lack of asset management expertise and possible liability concerns.

  • Suggestions include gradual fund delegation with capped amounts and strong oversight before scaling.

Upcoming milestones

Funding Model and Proposal Process

  • Finalize and submit a proposal to the foundation advocating for multiple buckets of funding, particularly adding a maintenance bucket without open source requirement, and conditional open sourcing after approval.

Micro Grant and Ecosystem Development Strategy

  • Prepare and propose a council-managed or working group-managed monthly budget proposal for microgrants and ecosystem support.

Voting Process and Quorum Improvement

  • Formalize and document a fixed monthly voting cycle consisting of the first half of the month for proposal submission and discussion, and the second half for voting.

  • Propose disabling mid-cycle proposal submissions to enforce the voting window.

Meeting Notes and Public Transparency

  • Distribute an AI generated meeting summary format for broader community transparency.

Proposal Follow-Up

  • Clarify with Algorand Foundation the process and options regarding handling proposals that did not reach quorum or did not pass.

Action items

  • Finalize and distribute concise meeting notes with pseudonymous identifiers for community sharing

  • Lead drafting of proposal for multiple funding buckets including maintenance bucket without open source requirement to Foundation

  • Coordinate follow-up inquiry with Foundation on process for proposals that fail quorum or don’t pass

  • Develop a proposal for a council-managed monthly budget to fund ecosystem microgrants or initiatives

  • Lead drafting detailed suggestions for a fixed monthly voting cycle and inactivity rules, including delegation options

  • Advise on inactivity policy for Xgov members and suggest incentive mechanisms for active voters

1 Like