responses.csv

"response_id","author","height","What would you use an on-chain form for?","How many fields would it need?","Do responses need to be private?","What is missing or wrong?","Contact (optional)"
"0000001","g1lyj99axrmmjlnckqs8szn88zv6g9g76q0m6u5q","270800","Upgrade coordination across a validator set. Every chain upgrade means asking every operator the same few questions — which version are you on, have you applied the migration, when will you restart — and today that lives in a Discord thread or a Google Form, where the chain being upgraded can't see it. We run validators on around 50 networks and do this constantly.

Second use: gathering structured input before a GovDAO proposal is written. By the time a proposal is on-chain it's yes/no. There's no on-chain way to ask ""should we do this, and what would you change"" first.","5","no","Found while building it: a form can't be edited once it has responses, so a typo in a label is permanent; responses are numbered globally, so a form's first response can appear as #0000003; and a select shows a machine-derived label (""Select an A3"") because gnoweb builds it from the parameter name and a realm can't override it. Field types are limited to text, textarea, number and select — email and yes/no would be the next two worth adding.","github.com/encapsulate-xyz"