SCF Q4 2026 Public Goods Award Results
The Stellar Community Fund approved 23 of 24 Q4 2026 public goods proposals, totaling $581,100, in the first vote held entirely on Stellar mainnet via Tansu governance app. Neural Quorum weighted votes from 28 community members determined results. StellarChain's $50,000 renewal failed after promising unmet deliverables.
The Stellar Community Fund's Q4 2026 Public Goods Award approved 23 of 24 proposals, worth $581,100 in requested budgets. @BuildOnStellar announced the results on November 5, 2026. The only proposal that did not pass was StellarChain's $50,000 renewal.
Public Goods awards fund the shared tools most Stellar builders rely on but nobody sells: SDKs, explorers, monitoring, security tooling and governance software. This round was also the first time the vote itself happened on Stellar mainnet.
How did the vote work?
Stellar Pilots and Public Good Contributors voted on Tansu, an on-chain governance app built on Stellar. Each voter's weight came from their Neural Quorum Governance (NQG) score, SCF's reputation system, so more established community members carry more weight.
Ballots were anonymous. Nobody could see how anyone voted while voting was open, and individual choices are still private. Only the totals were published when each proposal was finalized.
Proposals were posted October 21 and 22, voting closed October 28 and 29, and results were finalized on-chain on October 30.
Across the round, 28 people cast weighted votes, with 14 to 22 voting on each proposal.
One rule shaped the outcome. A proposal passes only if its approve votes outweigh reject and abstain votes combined. An abstain therefore works partly like a no.
The Q2 and Q3 rounds used the same setup on Stellar's test network.
Where did each proposal land?
Shares are of total weighted votes. Budgets are as requested in each proposal.
| Proposal | Category | Budget | Voters | Approve | Reject | Abstain |
|---|---|---|---|---|---|---|
| Lumen Loop | Ecosystem Visibility | $26,000 | 19 | 100% | 0% | 0% |
| Python Stellar SDK | SDKs | $15,000 | 22 | 95.3% | 0% | 4.7% |
| Flutter Stellar SDK | SDKs | $15,000 | 19 | 94.3% | 0% | 5.7% |
| RefractorSpace | Governance Tools | $25,500 | 20 | 91.3% | 3.5% | 5.2% |
| Rust Soroban Client | SDKs | $15,000 | 20 | 87.6% | 5.2% | 7.2% |
| Tansu | Governance Tools | $50,000 | 20 | 86.9% | 10.2% | 2.9% |
| Java Stellar SDK | SDKs | $15,000 | 20 | 86.9% | 0% | 13.1% |
| PG Atlas | Ecosystem Visibility | $37,000 | 22 | 86.1% | 9.3% | 4.6% |
| Hardware wallet support | Wallet Support | $15,000 | 17 | 85.4% | 6.1% | 8.5% |
| iOS Stellar SDK | SDKs | $15,000 | 14 | 85.2% | 0% | 14.8% |
| OBSRVR Radar | Infra Monitoring | $20,000 | 19 | 83.8% | 0% | 16.2% |
| .NET Stellar SDK | SDKs | $15,000 | 20 | 79.6% | 5.1% | 15.3% |
| Stellar Security Portal | Developer Experience | $40,000 | 18 | 76.9% | 5.8% | 17.3% |
| KMP Stellar SDK | SDKs | $15,000 | 19 | 72.4% | 5.5% | 22.1% |
| soroban-ret | Security & Auditing | $20,000 | 19 | 72.2% | 0% | 27.8% |
| Stellar Registry | Developer Experience | $50,000 | 22 | 71.9% | 18.7% | 9.4% |
| Stellar PHP SDK | SDKs | $15,000 | 21 | 71.4% | 9.5% | 19.0% |
| Soroban Scan | Data Support | $6,600 | 20 | 69.6% | 15.2% | 15.2% |
| Stellar Scaffold | Developer Experience | $50,000 | 22 | 67.3% | 23.4% | 9.4% |
| Stellarlight | Ecosystem Visibility | $40,000 | 22 | 64.2% | 15.4% | 20.5% |
| StellarAtlas | Infra Monitoring | $38,000 | 22 | 58.8% | 34.1% | 7.1% |
| Hyperledger Solang | Developer Experience | $28,000 | 20 | 57.6% | 22.2% | 20.2% |
| OpenGrants | Other | $15,000 | 20 | 54.4% | 21.6% | 24.0% |
| StellarChain (did not pass) | Infra Monitoring | $50,000 | 22 | 47.2% | 28.8% | 24.0% |
By category, Developer Experience projects drew the most approved budget at $168,000, followed by SDKs at $120,000 and Ecosystem Visibility at $103,000.
Why didn't StellarChain pass?
StellarChain, a Stellar block explorer, got more approve votes (47.2%) than reject votes (28.8%). Under the pass rule, though, its 24.0% abstain counted against it. StellarChain had received $50,000 in each of Q2 and Q3, according to SCF payment records.
Its proposal had two visible weak spots:
- A promised product hadn't shipped. More than half the Q4 budget, $28,000, was for Orion, a full-history data service. The same proposal listed Orion as "not released" from the previous quarter.
- An ad slot was counted as progress. A homepage advertising placement was listed as "partially delivered" work.
Voters don't publish their reasons, so these are the documented facts rather than a confirmed cause.
StellarChain is trying again. On November 6 it opened a pull request in the Public Goods repository to resubmit its Q4 proposal, still for $50,000 and still centered on Orion. The new version says Orion "was not counted as a completed commitment" in Q3 and that any missing release will be reported as partial delivery. The pull request has not been merged.
The next closest votes were OpenGrants at 54.4% approve, Hyperledger Solang at 57.6% and StellarAtlas at 58.8%. StellarAtlas drew the highest reject share of any project that passed, 34.1%.
Who is new, and who came back?
Six of the 23 approved projects are new to the Public Goods Award:
- Lumen Loop: the Stellar ecosystem news, research and project directory platform.
- soroban-ret: Inferara's tool for turning deployed smart contracts back into readable code. It runs on Inferara's Stellar Security Portal, and Soroban Scan uses it too.
- Rust Soroban Client Library: a toolkit for Rust developers building on Stellar.
- PG Atlas: a map of which Stellar tools depend on which, used to judge how critical each public good is.
- Soroban Scan: Rumble Fish's smart contract explorer.
- StellarAtlas: a network monitoring tool that tracks the health of Stellar's validators.
The other 17 were all funded in Q3. Q4's approved total is about 28% above Q3, which Tansu puts at $453,000 for 18 projects.
What is Tansu working on?
Tansu is the governance platform this round was voted on, built and maintained largely by Pamphile Tupui Roy. Its proposal passed with 86.9% approve.
According to its proposal, in Q3 Tansu:
- ran the Q3 vote "without incident," without the cost and collateral problems seen in Q2;
- rebuilt the membership system that decides who can vote and how much weight they get;
- passed a second security pre-audit with no critical or high-severity issues;
- added the Stellar Registry as its second user.
For Q4, the work covers:
- Running the program on mainnet. This covers this round and the next, plus taking over the voting-weight system from SDF and SCF.
- Putting membership on-chain, so Pilots can vote on promoting members and voting weights come from one source.
- New ways to vote, including delegating your vote, vetoes, and voting on a whole round at once instead of one proposal at a time.
- Safeguards, such as automatically stopping proposers from voting on their own proposals, plus an external security audit.
What are the SDK maintainers working on?
SDKs are the libraries developers use to build on Stellar in their own programming language. Eight are in this round: Python, Java, iOS, Flutter, Kotlin Multiplatform, PHP, .NET and Rust.
Much of their Q3 work went into keeping up with network upgrades. Stellar's Protocol 28 upgrade went to its mainnet vote on September 16, 2026, per @StellarOrg. The PHP, Flutter, iOS and Kotlin SDKs had support out by late August, ahead of that vote. The Rust client followed on September 5, and the Python and Java SDKs also shipped major releases.
For Q4, Soneso's four SDKs are working on support for the next Horizon and RPC releases and a security hardening pass. The .NET SDK is preparing for the following upgrade, Protocol 30. Python and Java are focused on clean-up and maintenance. The Rust client is making Stellar smart contracts easier to call from Rust.
Their usage claims hold up. We checked them against public package registries on November 12, 2026:
| SDK | Proposal claim | Registry now |
|---|---|---|
| Rust client | 74,000+ downloads (Oct 6) | 86,119 |
| Rust base library | 86,000+ downloads (Oct 6) | 100,669 |
| PHP | 62,623 total downloads | 68,246 |
| Flutter | 2,326 downloads per month | 2,717 |
| Python | no figure given | 208,256 last month |
Every claim is at or below the current public number.
Which commitments are worth watching?
A few proposals have gaps worth tracking through the quarter:
- Hardware wallets: Protocol 28 has been live since September, but Ledger support will only be released "after the next audit," and development has moved to a private repository.
- soroban-ret: Its starting error count for Q4 is the same figure it reported in July, so the proposal shows no change in that measure since then.
- Hyperledger Solang: The proposal gives two different figures for how much of its test suite currently passes, 25.7% and 31.3%.
- OBSRVR Radar: One of its Q4 deliverables fixes a slowdown that its own Q3 changes caused.
- StellarAtlas: $8,000 of its budget is hardware for self-hosting.
What comes next?
The 23 teams now have the quarter to deliver on the work in their proposals, and SCF records show no Q4 payments yet. The Q1 2027 round is already being set up on Tansu.
The program's rules are also changing. Two open pull requests would add service level and continuity obligations: each funded project sets its own measurable service targets, publishes a deploy runbook, and confirms that everything needed to build and deploy it lives in its repository. Current recipients would file them by January 7, 2027, and they would apply from Q1 2027, with misses reported but not affecting the second payment tranche in that first quarter.
New projects are lining up too. Quasar, a free Stellar RPC and full-history archive with no API key, is in intake review and has drawn strong support in its thread.
Because results now live on mainnet, anyone can check each round's totals the way this piece did, and compare what teams set out to do with what they ship.
Sources
- @BuildOnStellar results post, November 5, 2026: https://x.com/BuildOnStellar/status/2118439711152967938
- Round on Tansu: https://app.tansu.dev/governance/?name=stellarpgq4
- Vote totals, read from the on-chain results for each proposal: https://stellar.expert/explorer/public/contract/CDXINK2T3P46M4LWK35FVIXXHJ2XHAS4FOVCGVPJ63YV5OVTM24IY5BI
- StellarChain result transaction: https://stellar.expert/explorer/public/tx/33c4be48a74b0d150b60aa13ae6c945e6568dc920b7e000116082fb297671d8e
- Tansu pass rule and voting weights: https://github.com/Consulting-Manao/tansu/blob/main/contracts/tansu/src/contract_dao.rs
- Proposal documents: linked from each proposal on Tansu
- StellarChain resubmission, PR #209: https://github.com/SCF-Public-Goods-Maintenance/scf-public-goods-maintenance.github.io/pull/209
- Service level and continuity obligations, PRs #211 and #212: https://github.com/SCF-Public-Goods-Maintenance/scf-public-goods-maintenance.github.io/pull/211
- Quasar intake: https://github.com/SCF-Public-Goods-Maintenance/scf-public-goods-maintenance.github.io/issues/205
- @StellarOrg on the Protocol 28 mainnet vote: https://x.com/StellarOrg/status/2100000614092521698
- Download figures: crates.io, packagist.org, pub.dev, pypistats.org (November 12, 2026)
- Q2 and Q3 payment figures: SCF records (last synced November 9, 2026)
