We’re planning what to ship next and we want the roadmap to reflect what you actually need. Whether you’re a worker operator, a builder integrating $LCAI, a chat user, a DAO voter, or just lurking — your perspective shapes what we prioritize.
Drop your feedback:
How to write feedback that ships
Copy/paste this template — the more concrete, the more shippable
Prompts if the blank canvas is hard
Worker / validator UX — onboarding, monitoring, slashing transparency, per-job dashboards, automation, alerting
Models — which models should we support next? llama3-70b? mistral? qwen? code-specific? multimodal? embeddings?
Builder experience — SDKs (TS, Python, Rust, Go), REST/GraphQL gaps, dev portal, example apps, hackathon boilerplates
Bridge & wallet — chains to bridge to, external wallet integrations, UX on the existing flow
DAO & governance — proposal types, voting UX, treasury transparency, delegation
Tooling — explorer features, faucet improvements, IDE, status pages, RPC reliability
Docs — what’s missing, what’s wrong, what’s confusing, what would have saved you hours
Examples of strong feedback
“Worker dashboard with per-job latency + earnings chart, exportable as CSV for accounting”
“Add qwen2.5-coder-7b — code-completion is the use case I can’t move off OpenAI for”
“Bridge UI shows ‘pending’ for 30+ minutes with no estimate; need a time-to-arrival indicator”
“SDK in TypeScript with first-class streaming responses so I can wire it into Next.js chat apps without writing the SSE plumbing myself”
“Make it better” → tell us what feels bad
“Faster” → tell us which path is slow and what an acceptable target would be
What happens next
We’ll triage everything in <#1390661760020647996> over the next several days, then post a public summary of what made it into the upcoming sprints — and why some things didn’t. Brutally honest feedback is welcome; no good idea will be ignored.
Thank you for being part of this 
-– The Lightchain AI team