Kiran on Warpcast

Kiran pfp

im pretty bearish on ENS long-term imo any sufficiently popular cryptosocial product will generate native demand for their own namespace, and be able to charge rent for identities. it'll be more profitable than co-opting ENS the only truly canonical, interoperable identity is an ethereum address

11 replies

0 recast

0 reaction

Brenner pfp

Only way i could see namespace staying as a building block is if they charged a market rate tax % for the namespace and paid clients/apps (like Farcaster) to use ENS instead of making their own namespace It ends up as: users paying clients/apps to keep using the name they already acquired instead of fragmenting

1 reply

0 recast

0 reaction

Garrett pfp

Sure, but as more web3 social apps come online why wouldn’t namespace rent get commoditized to 0 (as it’s just a barrier to onboarding). I imagine apps will find more lucrative and differentiated ways to monetize that leverage new incentive models with tokenization, etc.

2 replies

0 recast

0 reaction

This also doesn’t take into account the ubiquity of ENS in ethers.js and Wagmi and the derivatives. Not saying you can’t build that same sort of resolution into ethers but defaults have power.

1 reply

0 recast

0 reaction

Victor Ma 🧾 pfp

https://i.imgur.com/PSlMZDJ.png

2 replies

0 recast

0 reaction

jesse.base.eth 🔵 pfp

jesse.base.eth 🔵

discussed this today with @dhof here: farcaster://casts/0x047cee8aa6cbe9e300bc58dab1449f0c95aaddf46a5682006e8962263a693ad8/0x047cee8aa6cbe9e300bc58dab1449f0c95aaddf46a5682006e8962263a693ad8 don't think ENS precludes products (1) having fully control of their namespace; (2) being able to charge. composability ftw.

1 reply

0 recast

0 reaction

andrew pfp

ENS as an identity layer is going the way of the gravatar ENS as a DNS-for-web3, maybe

0 reply

0 recast

0 reaction

Nicholas Charriere pfp

Nicholas Charriere

You're highlighting web3's biggest problem btw: everyone wants to build protocols, and wants builders to build on top of them, but the application layer is too thin. When an app DOES win at the application layer, they build their own protocols (example: opensea & seaport).

2 replies

0 recast

0 reaction

Ben - [C/x] pfp

@perl web3 evolution

0 reply

0 recast

0 reaction

Matthew pfp

0 reply

0 recast

0 reaction

4484.eth pfp

but why would a crypto social product go for native namespace over ENS? i think users will fight it. what happened to interoperability of protocols?

0 reply

0 recast

0 reaction

carlosdp.eth pfp

The whole point of ENS and it being controlled by a public good DAO is to allow anyone to own their namespace and still have interoperability with the whole ecosystem, without worrying about “competing” with ENS ENS is a public good, it doesn’t make profit. Look at how .lens integrated!

0 reply

0 recast

0 reaction