What additional value does this provide? A namespace doesn't change

how a smart contract operates. I acknowledge that Pascal has made significant contributions to Kadena, and I've expressed my appreciation for his work on multiple occasions, both publicly and directly to him. However, introducing exceptions raises a question: if we grant one to Pascal, who will be next? Should Amir, who also develops great things for the community, receive an exception? What about the web2 companies joining us; do they need exceptions too?

MetaMask and TrustWallet aren't supported! Kadena has its own blockchain so doesn't have a contract address as such. You can obtain it from CoinMetro.com / Binance.com / KuCoin.com / Gate.io / Okx.com (and other exchanges listed here: https://www.coingecko.com/en/coins/kadena#markets)

You are not granting Pascal... you are granting all projects that are currently developping on top of NG, and will a part of the NG multi-sig: - KadenAI - RedLinx, - Arkade - MoK - Hypercent -KdaBet

Everyone should be able to register their own, yes. Helps UX, looks tidier, easy to read, generates trust.

"What about vanity namespaces? The immediate response to this is obviously going to be: “What an opaque format! Can’t I have something like the cool kids with the .eth domains?” The answer is that the current functionality is a stepping stone on the way to vanity domain names in the same sense that the ENS-style name mappings resolve names to contract addresses. The current iteration at the very least achieves decentralized namespace definition, and is a necessary step to scaling the Kadena blockchain for developers" We know it is opaque and this is something that Core is working on.

MetaMask and TrustWallet aren't supported! Kadena has its own blockchain so doesn't have a contract address as such. You can obtain it from CoinMetro.com / Binance.com / KuCoin.com / Gate.io / Okx.com (and other exchanges listed here: https://www.coingecko.com/en/coins/kadena#markets)

Let people choose!

This is example of Layer H, no? Easier for human to interact with chain

To be clear: registering a namespace (two would be better 😀) for NG is just a submitting a simple transaction signed off by the team multi-sig. So can you be clear and say publicly that: - You don't want register a namespace for Marmalade NG

The goal is to provide that in the next steps: https://t.me/kadena_io/534399

Can you outline the next step now so the pascal can offer insight as alternative?

The core issue seems to be a lack of clarity about preferences from the people. We currently offer a decentralized solution for creating namespaces as requested, but now again there's a shift in demand towards a centralized approach. To enhance user experience, a naming service could be implemented to streamline the naming process. The principle namespaces approach is a scalable and sustainable one, designed to accommodate our chain's growth from 20 to 10,000 chains. With this solution, the control over namespaces lies with the people, not with Kadena.

Thanks for the clarity (and sneaky bit of Alpha) Are you basically saying it'll be like Kadena names is for wallet addresses, but for contract addresses?

MetaMask and TrustWallet aren't supported! Kadena has its own blockchain so doesn't have a contract address as such. You can obtain it from CoinMetro.com / Binance.com / KuCoin.com / Gate.io / Okx.com (and other exchanges listed here: https://www.coingecko.com/en/coins/kadena#markets)

Errr wow that's like every project, congrats on the support you're getting.

I love the product you build for the community. the support you get showcases how good it is. I'll give you praise for that. But we won't be doing Vanity namespaces anymore. It is one of the things if we started over again we would never have vanity namespaces. We would like to evolve our blockchain and this is one of those pieces.

If you love the product and appreciate the community aspect behind this why not grant the namespace as a one off? Knowing this is an actual piece of trusted infrastructure that works within Kadena that many projects will fuction on. A namespace seems like a no brainer for something like this does it not?

😔 I really think you are missing the point here read my messages again and see why we are pushing for principle namespaces. It is because of the community aspect behind it.

I feel a disconnect from what you are saying though and it make no sense to me. Does the community not want a namespace for NG?

The point might be that kadena's customers are developers and by not heeding what the customer wants you guys will push another developer away from Kadena like you guys did Sterling Long. No matter what Emily things he was a good dev and loved Kadena and people still use his Kode tool daily to dev. 4 projects are working with NG now and we need this resolved. What is the atualy cost of issuing him a namespace? Is it just philosophical argument? If so, please just get over the philosophy so we can go ahead and build on kadena

NG is a piece of Kadena history it should have a nampespace end of. You promote the build your own blockchain narrative, but when you do you get second class treatment lol

I am understanding it correctly? in future they vanity namespaces will be assigned again?