Technical Working Group: Naming System

I am also very interested in this topic. would love to hear an update from @Kepler :slight_smile:

I guess we are all very very interested…

@Kepler any news or update about it?

We are currently re-evaluating CNS in our priority list, we will give an update soon.

What i can say in advance is that we will first focus on an MVP that targets specific use cases and then based on the feedback we will decide on the next steps.

We are also looking for use cases/challenges that your projects might have that you think CNS can help with. Please share them with us if you have any.

Thank you for your patience and understanding.

Is there a plan for this group to pick back up in 2025?

heya @Kepler

just wondering if there’s been any movement on CNS since this post.

is the MVP in the works yet, and is there any rough timeline or direction for the naming standard?

would be great to know so projects can start thinking about how to plug into it, I’m sure some devs here are curious too

Hi @nadiein , thanks a lot for asking.
Indeed, we’ve been working on an MVP, and an update will come next week. Please stay tuned.

Cheers,
Bartosz.

As announced in yesterday’s Global R&D, we have deployed a “minimal CNS” to the mainnet, and would like to ask the community to test it and provide feedback.

The scope of the minimal CNS is as follows:

CNS Root: rupqg-4qaaa-aaaad-qhosa-cai

  • restricted, manual TLD registration
  • support for resolver flows

TLD Operator: rtows-riaaa-aaaad-qhosq-cai

  • a single TLD supported (.icp)
  • restricted registration
  • acts also as Naming Canister

CNS Resolver: (github-repo)

  • JS library for use in browsers
  • Rust library for use in Rust canisters

The TLD operator is pre-populated with domains for well-known canisters and names for IC-subnets, and it supports reverse-lookups for these ids/names.

Anybody can register test-domains as a subdomains of .test.icp.

  • no ownership checks, but also no stability for now
  • first-come first-served

See cns/minimal_cns at main · dfinity/cns · GitHub for details.

Special thanks to @icme for his contributions to the project :tada:

Thanks @bartosz. @rbirkner do you know who is the best person to ask about progress on this CNS system (looks like bartosz is no longer active).

I note that after registering a .test.icp. domain, this isn’t servable in the browser without first loading some JS via the standard DNS, and that JS is then responsible for loading the site from a CNS domain?

I was also interested in this 7 months or so ago after the R&D prez but as you probably saw, if not in Discords WG Marco said the only way is to ask in the forum since it has been discontinued, maybe we can tag @NathanosDev as one of the official contributors and @icme as well.

@alexu, do you know who best to ask about this?

Are there any outstanding TODOs on the CNS solution?

Is it in scope for this solution to allow users to type the domain name in the browser and have the page served up without any special extensions etc. or is that out of scope?

I can see how to register a test domain with this ‘minimal CNS’, but I’m unclear where to go from there.

https://x.com/dfinity/status/2108491018903421050?s=46&t=sSIc06RLmt0M-_Jt80Kuhg

“And now what? .icp is coming. What’s going to happen to our domains?”