A survey as a live protocol test
The Cardano Foundation said in its announcement that the 2026 State of the Cardano Developer Ecosystem survey will publish its questions and answers on Cardano using CIP-179. The survey is scheduled to remain open for about one month and close on November 30, 2026.
That changes the status of the questionnaire. A conventional survey usually stores responses in a database controlled by the organization conducting it. Readers may see a final report, selected charts and a description of the methodology, but they may not be able to inspect the underlying responses or repeat the calculations independently.
The Foundation’s stated approach is different. Once the questions and answers are recorded on the ledger, anyone should be able to inspect the published data, count responses independently and reproduce the analysis. The survey code and report-generation software are also open source, according to the announcement.
That does not prove that the resulting answers represent the entire developer population. It does establish a more inspectable record of what was submitted. Those are separate claims, and confusing them is how a transparent dataset becomes an overconfident conclusion.
The Foundation is also presenting the survey as one of the first CIP-179 surveys deployed on Cardano mainnet. That gives the standard an ordinary public use case rather than leaving it as a specification or demonstration. The system will have to accommodate real respondents, real submissions and the less tidy conditions that appear when software meets the public.
What CIP-179 provides
CIP-179 defines a metadata format for creating, answering and cancelling on-chain surveys and polls. The standard includes references to the survey itself, responder credentials and different response arrangements, including public and sealed responses.
That distinction matters. Recording a response on a ledger does not by itself describe every privacy property of the process. The survey design still determines what is exposed, how a response is associated with a credential and whether the answer can be read publicly or kept sealed under the standard’s supported format.
For this survey, the Foundation’s announcement describes the questions and answers as being published on Cardano. The practical questions therefore concern the exact implementation as much as the standard: what information is attached to each answer, whether respondents can be linked to submissions and how the reporting software interprets the records.
The questionnaire asks what developers are building, which programming languages and tools they use, how much experience they have and which obstacles are slowing their progress. It also includes technical stake-pool operators, smart-contract developers and other contributors. The Foundation is making it available in nine languages.
Those subjects are consequential because survey results can influence documentation work, tooling priorities, funding decisions and governance discussions. A result that says a tool is widely used can affect maintenance plans. A result that identifies a recurring obstacle can become evidence for a funding proposal. The value of the evidence depends on both the answers and the ability to understand how the answers were collected.
The governance record
The survey is accompanied by a governance Info Action asking DReps, stake-pool operators and Constitutional Committee members to share it with developers. The action does not require a vote. It is a request for distribution, not a decision on protocol parameters or treasury spending.
CardanoScan’s governance record shows the Foundation’s Info Action, including its deposit, voting status and November 30, 2026 expiry. That record supplies the ledger view of the governance step, while the Foundation’s announcement explains the survey’s purpose and participation request.
The sequence is therefore clear. The Foundation publishes the questionnaire and supporting software. Respondents submit answers through the CIP-179 process. The governance action asks ecosystem representatives to distribute the survey. The resulting records can then be analyzed from the published data rather than only from a private database.
Whether that sequence produces a reliable measure of the developer ecosystem is a different question.
The unresolved respondent problem
Only one critical reaction was identified in the supplied sources. DRepTalk reproduced an argument from DRep BKIND, who questioned whether browser-generated keys and sponsor-submitted responses can establish how many distinct people took part.
The criticism targets the difference between counting transactions and counting people. An on-chain system can make submissions visible and countable, but a visible submission is not automatically proof that it came from a unique human respondent. One person may submit more than once, several people may submit through a common sponsor or credential arrangement, and a browser-generated key may identify a submission without identifying its owner.
That objection does not show that the survey will fail. It identifies a limit on what the ledger alone can prove. The chain may provide a durable record of submissions while leaving respondent uniqueness dependent on the survey’s identity and anti-duplication design.
The Foundation will also need to address spam and duplicate answers. The supplied announcement establishes that the survey is intended to be open to public participation, but the sources do not specify the complete filtering procedure or the evidence that will accompany the final count. Those details will determine whether independent analysts can reproduce not only the raw total, but also the rules used to decide which responses belong in the result.
Privacy is another trade-off. Permanent publication can improve auditability, but developers may hesitate to describe their work, experience or obstacles if their answers can be connected to a credential or other identifying information. CIP-179’s support for public and sealed responses provides design choices, but it does not choose the appropriate balance for this questionnaire.
The mainnet deployment will therefore test more than a survey format. It will test whether an immutable ledger can make ecosystem research easier to audit without making participation harder or less private. The evidence that would settle the question is the implementation itself, the published response records, the filtering rules and an independent reproduction of the final report. Until those are available, Cardano has demonstrated a survey mechanism, not yet the reliability of the conclusions it will produce.
Thomas Green is not a person. No notebook, no deadlines, no face behind the name — just a byline this newsroom publishes under. Here is the production line underneath it, because a name beside a portrait reads like a journalist, and this one is not one.
The models. Writing: gpt-5.6-luna. Out on the live web: gpt-5.6-terra and gpt-5.6-luna. Pictures: gpt-image-1. Swap one in the newsroom and this line swaps with it — it is read off the machines, not typed here.
How a story is made
- Research. The searching model reads around the story, pointed at primary sources — the filing, the post, the repository — rather than at somebody else's write-up of them.
- Writing. The writing model drafts it against what was found, at Thomas Green's usual length and in Thomas Green's usual register.
- The loop. A reviewer reads the draft and sends it back with notes. Then reads it again. A piece can go round several times before it leaves the building.
- Enrichment. A quotation has to appear word for word on the page it is taken from. A chart may only use figures that appear in the source it cites. Whatever fails is dropped, and the reason is kept.
- Fact check. A last pass hunts for claims the article makes and its sources do not.
- A human stop. Sensitive subjects are held for a person to read before publication, and a person can kill any of it at any point.
If that sounds less like a newsroom and more like a factory: quite. It is called Press Factory.
This article was generated using AI and published automatically without human pre-publication review.
How this article was made
The article was produced by the Grandmonts Media News Engine using automated research, drafting and verification workflows. No human editor reviewed the article before publication. Grandmonts Media remains responsible for the published content. Errors can be reported at office@grandmonts.cz.