Skip to content

[META] Builder onboarding after mainnet #6280

Open
1 of 7 issues completed
Open

Description

@alexiscolin

Mainnet is live, so the onboarding audit (#5458 and its nine sub-issues) and the personas (#5455) have been closed. Most of what they asked for has shipped. What is left is below, one issue per problem.

Status 2026-10-28. The quickstart is fixed (#6279, closed by #6378). Most of the other fixes are merged but not on mainnet: mainnet runs gnoweb v1.5.1, skips v1.6.0, and gets the gnoweb release train with v1.7.0, which has no date yet (#6372). Onyx runs v1.6.0-rc.1.

Open work

Issue Why it matters Where it stands
✅ #6279 The quickstart deployed to staging, which is down Closed by #6378: the walkthroughs deploy to the latest testnet. Reference pages: #6412
#6274 boards2 is empty on mainnet, and the homepage sends people there To do: a first board on mainnet. #6147 (ProposeCreateBoard) waits for review
🟡 #6275 The mainnet homepage still has testnet leftovers and no "start here" Waiting for mainnet deploy, once #6379 (the rest, in review) merges. #6293 merged; onyx shows the new page
#6276 Gas: gnoweb commands charge a flat 1 GNOT, there is no estimation, and no link after deploy To do: drop the flat fee, estimate gas, print the realm URL after deploy. Copy-command fixes: #6418, #6419
🟡 #6278 The production gnoweb lags master, and nothing watches the faucet Waiting for mainnet deploy (v1.7.0). Discord link fixed (v1.5.1). Still to do (ops): watch the faucet
#6421 The CDN serves one visitor's theme to everyone and adds no-store to every response To do: CDN config (ops), and the theme fix in gnoweb or the CDN

✅ done · 🟡 code merged, waiting for the mainnet deploy · no mark: code or ops work still to do.

Tracked elsewhere: playground #5421 · wallet in gnoweb #3610 · CODEOWNERS #5425 · gas sponsorship #5382 · gnokey gas estimation #3703 · r/docs live again #5871 · SEO and AI discoverability #5769 · HTTP caching #5768 · gnoweb mainnet fixes #6126 #6158 (open), #6206 #6229 #6256 (merged, in v1.6.0).

Who we build for

Short version of #5455. Reference it in an issue as Persona: A.

Persona What gets them to "it works" What stops them today
A Go developer, new to Web3 Writes plain Go and it deploys Gas is guesswork (#6276)
B Solidity or Cosmos builder Sees how their patterns translate No migration guide (#5871 is a start)
C Hackathon hacker A demo running in two hours No starter templates, no full-stack example
D CTO evaluating chains Credible signals: mainnet, docs, ecosystem Thin showcase, no production SDK
E Open-source contributor A PR reviewed quickly No review expectations (#6277)
F Crypto-native user Usable apps on mainnet Few apps (#6274, Explore in #6273)
G Vibe coder, builds through an AI assistant The assistant gets Gno right Assistants confuse Gno and Go (#5769, gnomcp)

G was proposed by @jefft0 on #5462.

Metadata

Metadata

Labels

a/uxUser experience, product, marketing community, developer experience team

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions