Varun Srinivasan on Warpcast

Varun Srinivasan pfp

Varun Srinivasan

ENS names are going through an interesting phase. Original vision was one name everywhere, but L1 got too expensive so people have offchain ENS (farcaster) and L2 ENS (base names, world names). The natural progression seems to be towards multiple ENS namespaces - is this a net good thing?

30 replies

106 recasts

231 reactions

Vinay Vasanji pfp

@vinayvasanji.eth

This was part of my thesis for Everyname, which aggregated and resolved all onchain names associated with any wallet address (both EVM and not) Our thinking was that usernames will eventually be onchain, and that we will likely have app specific or context specific onchain usernames which is now starting to playout In web2 the canonical identifier was typically email, in web3 its the wallet address — apps will most likely offer both their own usernames and the option to use a universal name (.eth) Basically what Warpcast is already doing — its neither good nor bad, as long as the canonical identifier (wallet address) remains, and one of the primary reasons I'm on the fence about apps using embedded wallets

3 replies

6 recasts

38 reactions

vrypan |--o--| pfp

I don't get how we are talking about cross-chain atomic swaps, but we can't have cross-chain domain names. ENS should be one of the first Superchain apps.

0 reply

0 recast

9 reactions

MJC pfp

idk if a phonebook style universal system is something to aspire to or something that is even workable for onchain identity privacy issues, embedded accounts, community forks, etc. all examples of how namespaces could diverge

0 reply

0 recast

4 reactions

boscolo.eth pfp

Study DNS. It is inevitable that we will see multiple tlds to enhance brand expression. Worth noting that Bluesky is using DNS the same way FC uses ENS. Free subdomain, or pay for your own tld. IMO, using CCIP to offer cheaper ENS names minted on an L2/L3 is an anti-pattern for building a reliable name service.

0 reply

0 recast

3 reactions

Timur Badretdinov pfp

Timur Badretdinov

they are working on their own appchain, which imo has a high chance to become the place everyone issues their name long-term https://blog.ens.domains/post/ensv2

1 reply

0 recast

3 reactions

Daniel Fernandes pfp

Daniel Fernandes

It's something like $8 right now to register an ENS for 1 year. Consumers are always going to opine & pout for lower prices, but at some point we need to put our foot down and say "we know what we're worth, pay up or go somewhere else." L2s of course are a great solution in the same way everyone got GMail/Yahoo/Hotmail emails and didn't go buy their own domains.

2 replies

0 recast

3 reactions

‍ pfp

we will probably continue to see more of this given projects like https://namestone.xyz never understood why base elected to create and push for .base.eth I still don't see the point, except maybe to make $ & add some volume 1st they launched .base which was odd & not eth-aligned, then .base.eth which is better but still not necessary

0 reply

0 recast

1 reaction

Phil Cockfield pfp

0 reply

0 recast

1 reaction

Josh Ellithorpe pfp

Josh Ellithorpe

Don't think so, splitting this information in multiple locations means more expensive querying logic, and the potential for accidental duplicates.

1 reply

0 recast

1 reaction

depatchedmode pfp

Don’t worry, while at Fission our boy Blaine cooked up a Name Name Service: https://youtu.be/CHiCEd36KtI

0 reply

0 recast

0 reaction

Stas pfp

I just wish ENS devex was a priority

0 reply

0 recast

0 reaction

Chinmay 🪔🪔🕹️🍿 pfp

Chinmay 🪔🪔🕹️🍿

If ens becomes a tld, that would quickly make it universal.

2 replies

0 recast

3 reactions

Joshua Hyde pfp

Given that Basenames roll up to L1 (example: https://app.ens.domains/jrh3k5.base.eth) , is it necessarily 'multiple ENS namespaces', or merely a means of leveraging the existing infrastructure while reducing costs for the end user?

0 reply

0 recast

3 reactions

Emre Ekinci pfp

its a horrendous thing, I hate it - I rather use my website url which I own and can prove anywhere instead of trying to purchase my username on every single fkn chain

0 reply

0 recast

1 reaction

Sean Brennan pfp

https://discuss.ens.domains/t/temp-check-ensv2-development-funding-request/19762 Here's a funding proposal from last week to build an ENS L2 over the next year. Has wide support

0 reply

0 recast

0 reaction

meta-david🎩 | Building Scoop3 pfp

meta-david🎩 | Building Scoop3

Biggest issue I see a lot of these names don’t necessarily resolve everywhere with the exception of ENS on L1

1 reply

0 recast

3 reactions

mmu pfp

Pretty much have .eth domain be the universal account that lives on L1. And have all the subdomains ENS belong to each L2. .eth —> Ethereum (universal account) .base.eth —> Base .op.eth —> Optimism .arb.eth —> Arbitrum .pol.eth —> Polygon .zk.eth —> zkSync Sending a transaction to a specific subdomain will bridge those funds to its respective L2.

0 reply

0 recast

2 reactions

Herny🟢fomoeb🃏 pfp

Herny🟢fomoeb🃏

No, I think that multiple names do not help to identify one person, for example, if you know a person named henry14.eth, then in the Base blockchain it can be henry1410.base.eth all because you did not have time to buy your main name in time. This is a big problem. I think that everyone should have one name regardless of the network. ENS is one of the indicators of humanity

1 reply

0 recast

2 reactions

Jhon pfp

The ENS names shift is wild! Having different namespaces is cool for flexibility, but could it cause issues with fragmentation?

0 reply

1 recast

1 reaction