xGov Council Meeting – (September 2nd, 2026) 📅

xGov Council Meeting – (September 2nd, 2026) :date:

Attendees: xGov Council members (Algorand Foundation representatives excused themselves shortly before the call due to an urgent matter on their side)


Overview

A short council-only session. Foundation representatives had been expected but excused themselves at the last moment, citing an urgent matter. Some council members speculated on the reason; as that speculation was based on unofficial information, it has been left out of these notes. The practical consequence is that no new information was available on the election timeline or the node staking rewards setup beyond a brief message received shortly before the call.

The council’s official term has ended, but members continue to operate on a voluntary basis until a new council is elected. The main outcome of the session was an agreement to produce an end-of-term retrospective report on the council’s work and the proposals funded during the term. No formal votes were taken.


Key Topics Discussed

1. Foundation Updates & Communication

The council had reached out to the Foundation ahead of the meeting regarding the election timeline, council member payments, and the staking node setup. Shortly before the call, the Foundation sent a short response apologising for the last-minute absence and sharing the following operational updates:

  • The treasury top-up is expected from the Foundation’s finance office by early the following week at the latest, with pending approved proposals to be paid out as soon as it arrives.
  • No update was available on the node staking rewards mechanism or the election timeline. The council acknowledged both sit with the Foundation and will follow up once things settle on their side.

2. Pending Proposals & Council Mandate

With the top-up imminent, the council discussed clearing pending items and how to handle proposals still in the pipeline.

  • Members were asked to complete any outstanding Terms and Conditions confirmation votes so approved proposals can be paid out as soon as the top-up lands.
  • Proposers with proposals nearing the voting phase were advised to hold off until the top-up is in place and, ideally, until a new council is elected — the current council no longer holds a formal mandate, and a different council would be confirming those proposals.

3. End-of-Term Retrospective Report

A council member proposed leaving a closing report as the term’s legacy: a summary of the council’s work and a factual review of the proposals funded during the term and their current status.

  • Discussion on fairness: since proposals were funded retroactively for work already done, judging them after the fact has limits. The counterview was that project status is usually obvious at a glance — actively maintained and used, or dormant — without needing deep analysis. The council agreed a first-look review tells most of the story.
  • The council noted this also ties into what the Foundation expects of the next council: more objective, measurable evaluation of proposals in line with the planned scorecard.
  • Agreed approach: one member will compile a factual, chronological dataset of all proposals (status, requested amounts, discussion links) from the platform, along with the meeting notes published on the forum, as a neutral foundation for the report. Council members will each review two or three funded proposals and add brief assessments; the chair will tally results within roughly a week.
  • The council also discussed publishing the proposal documents previously submitted to the Foundation (node rewards funding, process improvements, election changes), as these were never publicly shared and reflect a significant part of the council’s work.

4. xGov Funding Scope & Sustainability

A council member raised whether xGov should shift toward funding protocol and SDK maintenance rather than acting as a catch-all grants program, given the limited budget.

  • Staking rewards from the planned node allocation are estimated at roughly 500k ALGO per month at most — an amount that cannot sustain protocol-level development, which runs at one to two orders of magnitude higher cost.
  • The Foundation had previously indicated protocol maintenance is outside xGov’s scope, and the council does not currently have the mandate or budget to change that.
  • The council’s view: xGov’s realistic role is supporting smaller builders and community projects. Broader protocol-sustainability questions are better raised through the EAC, which has an explicit mandate to advise the Foundation board — particularly once the next EAC cohort is elected.

Outcomes and Next Steps

  • Council members to complete outstanding TNC confirmation votes so pending payouts proceed once the top-up lands.
  • Proposers with proposals nearing voting to be advised to wait for the top-up and the new council.
  • One council member to compile the full proposal dataset and gather the term’s meeting notes; the chair to share the notes archive.
  • Council members to each review two or three funded proposals with brief assessments; chair to tally within about a week.
  • Council to consider publishing the proposal documents submitted to the Foundation during the term.
  • Chair to follow up with the Foundation on the election timeline, node staking setup, and communication cadence.

Note: This was a council-only session. Members continue on a voluntary basis past the end of the official term pending elections.

The end-of-term report sounds useful. Will it include a simple summary of what each funded project delivered and whether it is still active? That would make it easier for the wider community to understand the results.