*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 of xGov council 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.
note: This meeting took place instead of regular council meeting #8 in light of upgrade to xgov framework (batch 2) going live.
note2: There was a council meeting #7 on December 12th, which was focused on working group pilot by Michael & Urtho and was as such not recorded. There was no general council meeting at that date, due to no new developments with xgov platform which was still being upgraded (batch 2).
xGov Council & AF Meeting - December 16th 2025 
Meeting Date: December 16, 2025
Attendees: xGov Council members and representatives from the Algorand Foundation (AF)
Recording/Transcript: The meeting was recorded, and this summary serves as the public transcript (with any off-the-record parts redacted if requested).
Key Discussion Points & Outcomes:
-
Meeting Structure and Moderation
A very detailed agenda was presented and strictly followed, with time allocations moderated by the Council. This ensured the joint portion of the meeting concluded on time after one hour as planned, allowing clear outcomes and assigned CTAs before AF representatives departed. -
Recurring Meetings
Agreed to establish monthly recurring calls between the xGov Council and Algorand Foundation for better ongoing coordination. -
xGov Platform Updates (Batch 2)
AF provided updates on sliding quorum implementation, increased maximum ask amounts, and overall flexibility/limitations in the updated platform. -
Delegation Platform & Working Groups
Council updated on the ongoing development of the xGov delegation platform (built by Valar). Emerging ideas around pilot working groups were discussed—these would focus on specific ecosystem segments, maintaining and supporting them through the xGov grant process. Potential risks of delegation (e.g., voting power concentration, sybil attacks) were also raised. Brief revisit of working groups concept, highlighting potential for their future role in targeted ecosystem support and development. -
Greater Inclusion in Internal Discussions
Council expressed frustration over lack of inclusion in internal discussions on major xGov platform changes and feeling that their feedback wasn’t adequately respected. Discussions touched on ownership boundaries—who “owns” different parts of xGov and decision-making authority. AF conceded these concerns and explicitly agreed to include the xGov Council more proactively in future “internal” discussions and to better respect and incorporate Council feedback going forward. -
Shared/Public Product Backlog
Proposal for a public/shared TODO list or product backlog for xGov features (currently managed internally by AF via Jira). Challenges identified around access, syncing with internal tools, ownership, and prioritization. No final resolution; agreed to revisit in the next call with proposed solutions from both sides. -
Open-Sourcing xGov Frontend Repo
Discussion on the immediate need to open the frontend repository to allow community-driven UI/UX improvements without waiting on AF’s slower iteration process. AF emphasized producing best practices, refactoring, and updates of the code to latest AlgoKit. Council suggested temporary limited access for trusted developers. Consensus reached: AF committed to open-sourcing the xGov frontend repository by end of year (EOY) or early January 2026, pending ongoing development work. -
Inactive xGov Removal Mechanism
Debated approaches to removing inactive xGovs. AF suggested flagging/removing based on not voting in the past X proposals. Council argued for more flexibility and preferred a previously discussed lockstep mechanism (for predictability and habit-building). Common ground found: these aren’t mutually exclusive. A frontend-enforced lockstep could be added to guide voting timing, independent of the purge backend logic. Discussion to continue asynchronously on Discord for deeper exploration. -
Future Engagement Ideas
Ideas floated for improving xGov participation, including Progressive Web App (PWA) support, gamification (e.g., NFT rewards for engagement, percentage shares of approved proposal rewards). Recognized that no new engagement features were added in Batch 2. Council stressed that current notification systems (transactions, wallets, socials) are unsustainable and reiterated their support of aggressive inactive purge to boost active participation. -
Increasing Max Ask Further
Brief discussion on potentially raising max ask limits again. AF noted new budget details will be available in January 2026, so this can be revisited then. -
Post-Meeting Council Discussion
After AF representatives left, Council members stayed to debrief. Overall positive view on the concessions made by AF and the progress achieved, though there were mixed feelings regarding the pace and longer-term expectations. Strong agreement that these public meetings and transparent notes significantly enhance accountability on both sides.In light of the unresolved discussion on a shared/public product backlog, Michael proposed launching a Council-maintained public TODO board as an interim measure—this would allow the community to visibly track and prioritize requested xGov improvements while a proper synced solution with AF’s internal tools is worked out. However, this idea sparked mixed feelings within the Council: some members expressed concern that it effectively means the Council/community would be doing backlog management work that properly belongs to AF, potentially setting an unwanted precedent.
The group also reviewed active and pending proposals (e.g., split views on the C# SDK proposal—high ask relative to delivered work vs. recognition that funds are available), along with general impressions on all active proposals quality. Finally, it was decided there would be no additional Council call this year (the next scheduled one would fall near Christmas), with focus shifting to observing Batch 2 performance over the coming weeks.
Action Items 
:
- AF: Complete ongoing development work and open-source the xGov frontend repository by EOY or early January 2026.
- AF: Proactively include xGov Council in future internal discussions on major platform changes.
- Both sides: Prepare proposed solutions for a shared/public product backlog (e.g., public TODO list options, syncing mechanisms) to discuss at the next monthly call.
- Council & Community: Continue asynchronous discussion on Discord regarding inactive xGov removal mechanisms, incorporating AF’s latest suggestion and exploring hybrid approaches (e.g., frontend lockstep + backend purge logic).
- AF: Share new xGov budget details in January 2026 to enable further discussion on increasing max ask limits.
- Council: Monitor Batch 2 performance over the coming weeks; schedule and prepare for the next monthly recurring call in January 2026.
The meeting ended positively, with clear CTAs assigned and owners identified. These regular dialogues mark a significant step forward in collaboration between Council and Foundation.
Looking forward to the next call in January! 