Algorand Foundation pauses xGov grants, closes the Forum and shelves King Safety

The Algorand Foundation's community update¹, published on November 6, pauses the xGov grants program indefinitely from December 6 and pauses Project King Safety as a holistic roadmap item. The same post closes the Algorand Forum, effective November 6, concludes the Ecosystem Advisory Council as a company-run body, and ends the Foundation's sponsorship of the Algorand Technical Council.

Two of those decisions close questions the Foundation spent a year asking. Lifting the supply cap through inflation-based incentives, enabling and capturing MEV, and raising the minimum transaction fee are, in its words, 'no longer being considered at this time²'. xGov, the program that lets consensus participants vote on grants to builders, stops on that date, described as a pause and given no successor.

The Foundation gives one reason for the set: 'new leadership and a renewed focus on building toward a sustainable, revenue-generating network model³'. Its stated next chapter runs outward, bringing Falcon post-quantum security 'beyond Algorand' so that 'custodians, wallet providers, issuers, and other networks can add post-quantum security without rebuilding the systems t⁴hey already use'.

The consultation that ended without a change

The consultation has a paper trail. The September 2025 roadmap⁵ promised a King Safety position paper 'by the end of 2025, with implementation planned for 2026⁶'. On July 1 the Foundation said on X that the paper was then 'being shared with the Ecosystem Advisory Council this month⁷', the step before the council shared it with the community. None of the three options was adopted. The November 6 post also concluded that council, saying that 'as our priorities have shifted⁸' it would end it as a company-run body.

Nothing to migrate

Nothing migrates, nothing expires, and no one has to re-approve anything; the update's only instruction is to move discussion to the Algorand Discord. The Forum it replaces is closed, its own closure announcement sitting as the most recently active entry, with no replies and 26 views. A read-only archive is promised. The xGov portal⁹ is still running as though nothing had happened: 91¹⁰ xGovs, 63¹¹ proposals and 471,994¹² votes, its most recent listed proposal activity about three months old, and no notice of the pause.

Not everyone read the decision as housekeeping. One community member asked the Foundation to make the pause temporary, calling xGov a good way for the Algorand community to have 'some real power in shaping the ecosystem¹³'.

The one fee still on the table

King Safety's three options are gone, but not every charge is. New usage-based fees, 'such as those in place for transactions signed using Falcon-1024 post-quantum accounts, may still be introduced or adjusted'.

A Falcon-signed transaction already carries a minimum of 3,000¹⁴ microALGO, or 0.003¹⁵ ALGO, against 1,000¹⁶ microALGO for an ordinary one, as our guide to the quantum accounts set out. So the one fee an Algorand user can currently pay more of is also the only one the Foundation has declined to rule out touching.

Staking runs to January 2028, on a thin online share

The update's first reassurance is that staking rewards already committed through January 2028 stand. That matters because consensus participation¹⁷ is what the network's security rests on, and the participating share is smaller than the staked total suggests. In the latest reading about 9.82 billion¹⁸ ALGO was staked, and 20.23% of it, roughly 1.99 billion, was online and participating. Every account that comes online moves that share, and every one that leaves does too.

The contest, and the report published beside it

On October 22 the blog announced the Global x402 Challenge¹⁹ results. 115²⁰ projects put a paid endpoint on Algorand mainnet and settled USDC through the GoPlausible facilitator. Twenty of them shared a 500,000²¹ ALGO leaderboard pool, and the top ten went to a final for a separate $100,000 USDC²² pool. That leaderboard ranked its top twenty on counted USDC volume settled through the facilitator. The final was held on October 30, with Moltworld first, Finality second, Earnest third, Tendril fourth and SiteLenz fifth.

Then the transparency. The Foundation published GoPlausible's settlement report as delivered²³, with registrants' names and contact details removed and the figures unchanged. It counts 872,948²⁴ settlements worth 108,102²⁵.65 USDC from 13,026²⁶ paying accounts. One class it calls synthetic-indicated takes in 837,428²⁷ settlements and 91,587.27 USDC — 95.93% of the counted settlements and 84.72% of the counted USDC. A payment lands there when the payer is the merchant itself, a wallet it created or funded, or a fleet whose money it sends back. The remaining 35,520²⁸ settlements and 16,515.38 USDC carry no detected link.

GoPlausible is careful about what its label means: 'A matched pattern indicates a link between payer and merchant; it does not establish intent, and an unmatched payer is not proven independent.'

The spread across the five finalists resists a single story. Moltworld, the winner, counts 12,041.70 USDC, of which 12,041.692²⁹ carries no detected link to the merchant. Finality, second, counts 14,694.90 USDC, 12,464.90 of it synthetic-indicated. Tendril, fourth, is 831.75 of 1,642.40 USDC synthetic-indicated, and Earnest and SiteLenz sit at zero there. Most of the counted activity was tiny: 510,886³⁰ settlements moved under a cent each, worth 574.10 USDC between them, against 108,102.65 USDC counted overall.

The facilitator had heard the question before. In September an entrant published its own analysis³¹ on GoPlausible's GitHub. It traced 60³² merchants and 342³³ payer wallets over the 30 days to September 24, across $10,192³⁴ of USDC. Most of that volume came from wallets linked to the merchant being paid rather than from independent multi-merchant payers. A GoPlausible contributor replied that synthetic traffic at scale 'is not tolerated on facilitator and is being checked per transaction³⁵', and closed the issue.

A place on that leaderboard is not by itself evidence of outside demand. We reported the smaller version of it in August, when CompX's x402 agent APIs were paid for almost entirely by the project's own bots.

The essay: migration as security debt

A separate post, the October 27 piece³⁶ by Will Beaumont, argues that quantum migration is 'security debt accumulating today'. Its case is that signature choices spread into key formats, custody workflows and hardware, and that 'some estimates place such quantum computers as being available as early as 2029³⁷'.

One figure is worth correcting if you plan to quote it. Beaumont writes that Falcon signatures and public keys 'run to over three kilobytes, against dozens of bytes³⁸' for elliptic-curve schemes. Algorand's developer documentation puts a Falcon-1024 signature at roughly 1.2³⁹ KB and its public key at about 1.8⁴⁰ KB, against 64⁴¹ and 32⁴² bytes for Ed25519, so three kilobytes is the pair combined.

Two things in the piece look forward rather than back: planned hybrid accounts carrying a classical and a post-quantum key at once, and SDKs expected to build Falcon-1024 accounts from a standard seed phrase. It also concedes the gap, in its own words: 'Algorand acknowledges that end users will not have Falcon-capable hardware devices for a little while.⁴³'

What the older post says now

The roadmap page has been amended in place: it now opens with a line sending readers to the November 6 update. The 2025 promise is still on it, beneath that line.