Running a Namespace Versus Acting as a Subdomain Registrar

I’m curious to get a rundown of the specific benefits to running a namespace (which I understand can then still allow you to run as a subdomain registrar) versus just running a subdomain registrar. Let’s leave the potential for accepting ID registration payments yourself rather than having those just be burned out of it because that’s an obvious one and one that I’m less interested in in the grand scheme of things.

1 Like

This is inspired by pbj's breakdown on our Slack:

Subdomain Registrar

  • Source of centralization: registrations can only be made by the domain owner ( can only be made by the owner of — so user registrations must be sponsored by the registrar
  • Flexible pricing if the registrar wishes to require a (off-chain) payment before registering a name
  • Names never expire, and updates to names can be broadcast by any domain
  • Many registrations (> 100) can be batched together, making the on-chain unit-cost (paid by the registrar) of names very low
  • Requires registrar infrastructure


  • Names can be registered by anyone, two-step registration prevents front-running of a name registration
  • Price of names is fixed once a namespace has been created
  • Registration fees are only paid to the creator during the first year of the namespace
  • Each name registration requires 2 blockchain transactions, meaning the unit-cost of names is higher
  • Name updates can be announced directly on the chain (they do not need to be broadcast by a domain owner)

Price of names is fixed once a namespace has been created

Just want to elaborate on this. The application can implement a flexible name price after-the-fact by only acknowledging the existence of names that have paid enough money (e.g. the app code can deny sign-ins from users who haven’t paid enough). The on-chain name price curve is primarily meant to stop squatters, and to help developers quickly get a revenue stream early in their application’s lifetime.

1 Like

Can you provide some clarification on this point @aaron or @jude. I know I said I wanted to leave the accepting registration payments topic out of the conversation, but this is news to me if I’m understanding this bullet point right.

Does this mean any new registrations to that namespace that come more than 12 months since the namespace was created end up in burned BTC? Or do those payments go somewhere else?

Not to clutter my on forum post, but I’m also curious if there is a UI around this for the end-user yet. If I’m running a namespace, what does that actually look like when someone signs up for Graphite?

Yep, after 52595 blocks, registration fees go to the burn address rather than the namespace creator.

Currently, there’s not support in our UI for this process-- when a user tries to register a name in the browser, they can only register within the .id namespace.

1 Like

Been talking with @patrick about running a subdomain registrar or a namespace to help the user onboarding experience, and we both thought it would be good to post my thoughts here so that any misunderstandings or incorrect assumptions could be addressed.

I don’t think I’ll be running either for the following reasons:

I don’t necessarily want IDs to be specific to Graphite. I want anyone with a Blockstack ID to be able to use the app. And yes, that’s possible while running a namespace or a subdomain registrar, but it requires two things:

  1. Me to build out an interface for the registration process/auth process if someone is using a BNS id
  2. It doesn’t actually have the benefit of quicker onboarding anymore than someone just registering a subdomain on the space.

The subdomains issued of have that onboarding benefit and are universal to Blockstack and not controlled in anyway by me. They are basically the faster equivalent to a regular .id username.

I don’t plan to collect registration fees for ID purchases, and I already have a solution for enterprise feature control that utilizes existing IDs. Which is big for me. I don’t want an enterprise user who may have previously been using any Blockstack app to have to create a whole new ID just to be able to access those features. I get this conceptually, but I don’t think it’s necessary.

Would love feedback on my thoughts here…especially if I’m wrong about anything or missing hidden benefits.

1 Like

@aaron @jude how can the subdomain registrar broadcast multiple ‘sponsored names’ in one batch? And how can an existing user’s Blockstack ID be linked to this (new) subdomain while still remaining active on its own?

Will functionality for these use cases become available through the CLI or the Blockstack Browser, or both?

@luckshas FYI.

@aaron @jude how can the subdomain registrar broadcast multiple ‘sponsored names’ in one batch?

It can send up to 120 sponsored names per transaction. See the documentation here:

And how can an existing user’s Blockstack ID be linked to this (new) subdomain while still remaining active on its own?

One way to do this is to have the user use their existing Blockstack ID to sign an attestation that says “this sponsored name is owned by the same person that owns this other name” and make it available to the application. @aaron, @larry, or @yukan would have good ideas about how to do this in the Browser.

1 Like

What happens if the primary name that the subdomains are registered under doesn’t get renewed?

What happens if the primary name that the subdomains are registered under doesn’t get renewed?

The subdomains still resolve, and can still send update transactions (but not transfer transactions) via a zone file update from any existing on-chain name. However, to process a transfer or to create a new subdomain with the same suffix, the on-chain name will need to be reregistered.

(I’m trying not to call off-chain names “subdomains” because they have very different semantics from DNS subdomains. These off-chain names are more like email addresses that keep working as app user accounts even when the mail server goes offline).




I’ve come full circle on this and wanted to share with the community. I am now running both a graphite namespace and a subdomain registrar. The reason turned out to be pretty simple—it’s sort of necessary to control permissions with enterprise users.

By having a .graphite namespace, each enterprise client will get their own root company id on this namespace (i.e. nytimes.graphite or wapo.graphite). Their users will be registered as subdomain ids of that root id (i.e. alice.nytime.graphite).

The root id domain (nytimes or wapo) mapping to the specific Graphite enterprise client makes loading that specific client’s permissions file simple. Those permissions then trickle down to each user as the client has specified.

Just wanted to come back to this post in case anyone was confused or on the fence about either namespaces or subdomain registrars.


This is a really powerful use-case, and does a great job showing how to make the most of subdomains and namespaces. Many kudos to @jehunter5811 for writing this up!


Hello all

I am asking if there is any technical documentation on how to start your .companyname subdomain and act as a subdomain registrar ?

I would recommend looking at Blockusign for inspiration.

Technical overview:

Blockusign code:

Subdomain registrar documentation:

I’m pretty much running a vanila subdomain registrar like here: ,

I did not even purchase my own top level namespace. I simply purchased and put all my subdomains under that, like

Really the “hardest” part is generating a public private key pair and sending bitcoin to it to fund the subdomain registrar.

Can I ask for more technical details about it and how you passed this difficulty ?


aaron explains how to generate a separate keypair here:

1 Like