*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.
xGov Council & AF Meeting - January 21st 2026 
Date: January 21, 2026
Attendees: xGov Council members & Algorand Foundation representatives
Overview
This meeting focused on three key operational and governance topics:
- Open-sourcing the xGov platform UI
- Mitigating chronic absenteeism in xGov voting
- Open-source requirements for xGov-funded proposals
The discussion was candid and, at times, tense, reflecting growing concern over delays, unclear ownership, and structural limitations within the current xGov framework. At the same time, it built on ongoing collaboration between the xGov Council and the Algorand Foundation, with shared acknowledgment of both progress made and gaps that remain.
Participants aligned on several short-term corrective actions, particularly around tooling and participation enforcement. However, it was also explicitly recognized that broader governance and process questions remain unresolved and will require escalation beyond the council. The council emphasized that, alongside near-term fixes, greater predictability and reduced effort for xGov participation are necessary to sustainably improve governance effectiveness.
Key Topics Discussed
1. Open-Sourcing the xGov Platform UI
-
The council reiterated that open-sourcing the xGov platform UI was previously promised by the Algorand Foundation, with an initial target of end-of-year delivery.
-
Foundation representatives explained that delays were driven by:
- Migration to a newer SDK version
- Repository cleanup and security review
- Competing internal priorities
-
The Foundation confirmed that:
- The SDK migration is near completion
- Repository preparation is underway
- The UI repository is expected to be open-sourced by the end of the following week
-
The council emphasized that a closed-source UI remains a major blocker to:
- Improving proposal discoverability and comparison
- Reducing voter friction and abstention
- Enabling community-driven improvements
-
There was broad agreement that many governance and UX improvements can be implemented at the UI layer, without requiring smart contract changes.
2. Visibility, Roadmapping, and Development Process
-
Council members requested clearer visibility into ongoing and planned xGov UI work, including:
- Public task tracking
- Defined ownership
- Predictable delivery windows
-
It was noted that once the UI is open-sourced:
- Community contributors can assist with improvements
- Iteration cycles can be shortened
-
The Foundation acknowledged these concerns and expressed openness to more transparent workflows post–open source release.
3. Absenteeism in xGov Voting (Immediate Priority)
-
There was strong consensus that chronic absenteeism is undermining the effectiveness and credibility of xGov.
-
Recent voting cycles showed that:
- Proposals with strong approval signals failed due to quorum rules
- A significant portion of registered xGovs have never participated
-
The Foundation presented a short-term technical solution, building on prior collaborative discussions and iterations that took place via Discord and other working channels between the council and the Foundation.
-
The proposed approach:
- Tracks consecutive proposal absences per xGov
- Automatically removes xGovs after exceeding a defined absence threshold
- Introduces the ability to explicitly signal non-participation (e.g., boycott), clearly distinguishing intentional abstention from passive inactivity
-
The council stated that:
- Purging never-voters and introducing an explicit boycott option are expected to immediately and meaningfully improve absenteeism metrics
- These measures restore signal quality by ensuring that non-participation is intentional rather than accidental
-
However, the council emphasized that these changes are stop-gap measures, necessary for short-term stability but insufficient as a long-term solution on their own.
-
It was clarified that:
- Deployment requires a brief pause in proposal flow
- Existing proposals must resolve before the upgrade
-
Broad support was expressed for proceeding immediately, with final parameter values to be confirmed.
4. Immediate Committee Cleanup (“Never-Voters”)
-
The council reiterated the importance of excluding xGovs who have never voted from future committees.
-
It was confirmed that:
- This cleanup can be executed as part of the absenteeism changes
- If completed before the next committee snapshot, inactive xGovs will not carry over
-
The council expects this action to immediately improve quorum health, but reiterated that it must be paired with broader process improvements to be sustainable. One of such necessities is automatic and more malleable committee creation process.
5. Quorum and Governance Impact
-
The Foundation and the council jointly noted that purging inactive xGovs will reduce the total number of registered participants, which is expected to impact quorum calculations and improve the likelihood of proposals reaching quorum.
-
Participants agreed to:
- Observe the effects of committee cleanup and boycott signaling first
- Revisit quorum mechanics only if issues persist after these changes are in place
6. Council Expectations on Abstention (Medium-Term)
-
The council emphasized that while never-voter purges and boycott signaling will materially improve participation in the short term, abstention risk will persist unless:
- The voting process becomes more predictable
- The cognitive and time burden on xGovs is reduced
-
The council reiterated its strong preference for a lock-step proposal process, where:
- All proposals follow a fixed, predictable cadence
- Discussion and voting periods are standardized
- Proposals are grouped and voted on at fixed times each month
-
Members noted that a predictable cadence would:
- Make participation easier to plan for
- Reduce voter fatigue
- Improve overall participation quality
-
The council encouraged parallel work on these structural improvements while short-term fixes are deployed.
7. Open-Source Requirements for xGov Funding (Unresolved)
-
The discussion revisited the current open-source requirement, under which projects must open-source their work at the time of application, regardless of approval outcome or whether any funding is ultimately received.
-
Council members reiterated concerns that this requirement:
- Discourages participation from projects with commercial or strategic considerations
- Creates risk for teams applying in good faith
- Is particularly challenging for long-running or retroactive proposals
-
Foundation representatives noted that this requirement reflects xGov’s original mandate to fund public goods.
-
The council briefly revisited open-sourcing after approval or delivery, which had already been discussed in prior Discord threads and earlier council–Foundation conversations.
- This approach was characterized by the council as a procedural or technical adjustment, rather than a policy shift.
- The end product would still be open-sourced, with funding released conditionally once requirements are met.
- Applicability would be limited to strictly constrained cases, such as long-standing projects with clear, measurable value.
- To formalize this approach, the council shared a working document outlining a proposed submission, review, and enforcement flow.
-
The primary and more substantive discussion focused on whether open-sourcing should be optional in selected cases.
-
Council members reiterated that some high-impact ecosystem projects may not be viable under any mandatory open-source requirement, even if delayed.
-
As an illustrative example, end-user wallets were cited:
- Wallets provide critical infrastructure and play a key role in driving user adoption
- Funding models vary significantly, with some wallets receiving substantial, targeted Foundation support, while others operate with little or no direct funding
- Commercial and competitive constraints may make full open-sourcing impractical, despite their importance to the ecosystem
- Allowing such projects to access xGov funding under defined conditions could level the playing field and potentially deliver greater overall value to the Algorand ecosystem
-
This raised broader questions around:
- The scope and mandate of xGov
- How ecosystem value should be defined and assessed
- The boundary between xGov funding and other Foundation funding programs
-
The council committed to preparing a concrete proposal addressing optional open-source, potentially via a separate, clearly scoped funding bucket within xGov.
- This bucket would allow commercial, closed-source projects to apply under defined conditions
- Funding would be explicitly limited in duration and scope, ensuring projects do not become dependent on xGov as ongoing “life support”
- The intent would be to support specific, high-impact work, not to subsidize or maintain closed-source projects indefinitely
- Closed-source status itself would also be subject to constraints, with expectations around transparency, review, and reassessment over time
-
Participants agreed that optional open-source represents a material policy decision, not a procedural adjustment, and would require executive-level direction from the Foundation.
-
Key Takeaways
- Open-sourcing the xGov UI remains critical to unblocking governance and UX improvements.
- Purging never-voters and introducing explicit boycott signaling are expected to immediately improve absenteeism, but are not sufficient long-term solutions.
- Sustainable participation requires predictable, streamlined voting mechanics that reduce effort for xGovs.
- The scope of xGov funding (OSS vs. non-OSS) remains unresolved and requires executive-level direction.
- Continued coordination is improving but remains constrained by tooling and process maturity.
Action Items
-
Algorand Foundation
- Proceed with open-sourcing the xGov platform UI.
- Finalize and deploy absenteeism-related changes.
- Coordinate timing for any required proposal-flow pause.
-
xGov Council
- Confirm absenteeism thresholds and boycott parameters.
- Draft a structured proposal addressing funding eligibility scope.
- Continue advocating for a lock-step, predictable proposal cadence.
-
Joint
- Monitor participation and quorum outcomes after cleanup.
- Revisit quorum and process mechanics after the next committee cycle.
- Align on longer-term voting process simplification and predictability.
