Spark Names Identity Directory by panagot

Why?

Spark Names are live on Firo mainnet, but public discovery is still thin. The existing site (sparknames.firo.org) is mainly education and wallet CTAs. This proposal turns a working prototype into a production website where anyone can browse names, open identity profiles, inspect registry statistics, and help owners publish optional public additionalInfo via wallet renew.

Spark Names already exist. This proposal builds the public identity and discovery layer around them.

This is Part 1 (identity site + registry utilities). Part 2 forum identity integration (SSO / badges / proof-of-usage style features) would be a separate FCS proposal.

A live explorer snapshot shows ~502 registered names (~71 short / ≤5 chars; ~14 due within ~30 days). Registration fees support the Community Fund, yet adoption and renewal activity are not presented as a neutral public surface.

For Firo, this creates a permanent public discovery layer for Spark Names: active registered names become discoverable through shareable profiles, while aggregate statistics make adoption and renewal activity visible. It also gives wallets, explorers, and community apps a documented public data surface to build against.

This proposal funds that product on names.firo.org (Firo DNS; independent community operation with a clear disclaimer that it is not run by the official Core team), a public utility the Spark Names ecosystem needs today.

Working preview: https://spark-names-demo.vercel.app

How much?

Total: 1,500 FIRO The funded amount is fixed in FIRO (same convention as my completed Spark Sync Monitor, which was funded and paid in FIRO). Payouts are 800 FIRO then 700 FIRO.

• Effort: ~25–30 hours over ~3 weeks (UI prototype already exists).
• Pay: 1,500 FIRO total (800 kickoff / 700 on delivery), fixed in FIRO.
• Production URL: names.firo.org under Firo DNS. No separate second-level domain is required. Hosting and a small claims database run on the operator host behind that subdomain, with an on-site disclaimer that the project is not operated by the Firo Core team.

What?

A public Spark Names identity website on names.firo.org.

Identity

• Lookup, directory, and public profile pages
• Live mainnet registry reads via the most reliable available path: the existing explorer-backed implementation is the working fallback; if a stable public node RPC/read endpoint is provided, the site will verify and/or migrate relevant reads (getsparknames, getsparknamedata, tip) to that source
• Claim → edit → publish using the existing Spark Names wallet renewal/update mechanism for public additionalInfo (wallet register/renew with ownership proof remains the source of truth)
• Permanent site-side claims register (small database on the host) so verified profile claims persist for all visitors; on-chain data remains the ownership and public-metadata source of truth
• The site distinguishes wallet ownership (ownership proof over the Spark address bound to the name) from optional public metadata (additionalInfo — free-form on-chain text, max 1024 bytes; our structured profile JSON is a site convention). It will never generate or infer biographies, affiliations, or other claims not present in the underlying data
• Deep links to explorer + wallet docs (this site does not register/renew Spark Names)

Utilities

• Registry stats (totals, length histogram, renewals due)
• Expiry radar + profile warnings
• Documented public JSON / data interface for integrators
• Embeddable badges + shareable profile URLs
• Privacy-safe: public registry fields and verified claim/profile records only; no private wallet keys or view data stored on the server

Infrastructure

• names.firo.org via Firo DNS + 12-month HTTPS hosting (operator-run host + claims DB)
• Site disclaimer: independent community project, not Firo Core
• MIT source + ops notes so Firo can fork or take over

Already shipped (prototype)

• Live preview: https://spark-names-demo.vercel.app
• Explorer-backed live registry browse (including public additionalInfo when present), stats, tools, claim/edit UI

Out of scope

• Website checkout to buy/renew Spark Names (Campfire / Core)
• Forum SSO, voting, or proof-of-usage schemes (status badges on this site are in scope; forum badges are not)

Future integration (not funded here)

The production site will include a short specification that makes a future forum connection straightforward (profile URL scheme, recommended public fields, privacy notes). Forum SSO / badges / voting are excluded from this proposal and would need a separate ask.

Milestones?

Milestone 1 — Kickoff — 800 FIRO Paid at kickoff (~650 FIRO engineering start + ~150 FIRO hosting budget)

Starts production work: provision HTTPS host + claims DB, begin DNS coordination for names.firo.org, harden the live registry path against the existing preview, and keep the MIT repo/docs current while delivery proceeds.

Acceptance (kickoff): proposal funded; work started; production host provisioned (or hosting ordered) for the names.firo.org deployment. Live production URL and full feature acceptance are Milestone 2.

Milestone 2 — Delivery on names.firo.org — Weeks 1–3 — 700 FIRO Paid on delivery

• names.firo.org live with HTTPS via Firo DNS; Core/community disclaimer on-site
• Live mainnet directory/profiles; claims persist server-side
• Stats + expiry radar production-ready; badges / JSON interface documented
• Guide + DEPLOY/OPS accurate; MIT repo tagged
• Short Part 2 prep specification (docs only); forum announcement + handover notes

Acceptance: names.firo.org live with HTTPS and disclaimer; resolves real mainnet names; claims persist server-side; utilities documented; Part 2 prep specification published; MIT repo tagged.

Total duration: ~3 weeks after funding.

Outcomes?

• Live MIT-licensed Spark Names identity website on names.firo.org
• Public directory, profiles, and registry stats for mainnet names
• Profiles rooted in on-chain data + optional published additionalInfo, with a durable site claims register
• 12 months hosting covered
• Documented public data surface for integrators
• Track record: completed Firo Spark Sync Monitor via FCS (forum completion · firostatus.com)

Success metrics

• Production site live on names.firo.org within ~3 weeks of funding
• Clear disclaimer that the site is not operated by Firo Core
• All currently active mainnet Spark Names discoverable through the directory/read path
• Public profile URLs for registered names
• Registry statistics and expiry warnings driven by live mainnet registration state
• Public JSON/data interface documented for third-party integrators
• MIT repository + deployment documentation published
• Part 2 prep specification completed (docs only for forum integration not funded here)
• No private wallet keys or view data stored on the server

Why you?

Independent full-stack engineer focused on privacy-tech infrastructure (Node.js, TLS/Electrum, dashboards, public sites). I already completed Firo Spark Sync Monitor through FCS prototype first, then production on firostatus.com, MIT, documented handoff.

The Spark Names identity preview is already public and reads live mainnet registry data today. This ask funds the production website on names.firo.org, hardened live path, claims persistence, and clean documentation not greenfield UI, and not a protocol change.