Business Plan

A .kas domain on its own is an on-chain ownership record — nothing more. No SEO footprint, no meta tags, no structured data a search engine can read, no category, nothing telling a visitor who holds it or where to find them. There's no curated place to browse premium Kaspa-native names by niche, and no standard way to attach an identity — an X account, a website — to a domain.

1. Prove ownership — connect Kasware to verify the .kas name on KNS.
2. List it — sign a message with Kasware to confirm the request is yours. The fee is a one-time 200 KAS.
3. Categorize it — pick at least one category so it can actually be found.
4. Add resources — attach an X account and links to the domain's public profile.
5. Get discovered — the domain appears on its category page and in search.
6. Community voting — anyone can support a domain for 1 KAS per vote, one per wallet, boosting its ranking.

The current fee schedule is deliberately simple: a one-time listing fee and a per-wallet vote fee. Signing is free and profile edits remain free after listing.

• Listing fees — one-time 200 KASper domain.
• Voting fees — 1 KAS per vote, one vote per wallet. Fees are paid on Kaspa L1 to the configured treasury.

KaspaDomains does not sell, resell, or broker .kas domains, and never takes custody of them. Every listing is created and controlled by the wallet that owns the underlying KNS name. This keeps the product scoped to what it actually is: a discovery and identity layer on top of ownership that already exists on Kaspa L1.

• .kas domain holders who want their name to be more than a wallet-address curiosity — projects, creators, and individuals building a Kaspa-native identity.
• The Kaspa community, as the audience browsing and voting on the domains they value.

The full flow described above — wallet-gated listing, mandatory categories, resource management, community voting, category and search browsing — is built, and every write is gated on a Kaspa L1 signature checked against KNS. It is not yet running against a live database: the schema has not been applied, so no listing or vote has been created end to end. The earlier Kasplex contract path has been removed: most of those contracts had no deployed code and the rest failed every call. See the docs for the details, or browse what's already listed. A mainnet launch, a formal contract security review, and continued ecosystem growth are the next milestones.