dom
@dhof
name registration is such an obvious way to monetize decentralized/federated communication protocols you have to wonder how many times it's going to happen in the next few years for many i think it'd be tough to give up potential revenue to ENS (or in the future fnames) just because they got there a moment earlier
10 replies
0 recast
0 reaction
jesse.base.eth 🔵
@jessepollak
I think one hybrid structure which could achieve the best of both worlds (revenue/control for issuer + compatibility with ENS) is that services leverage ENS subdomains with special treatment in their product (+ fees, additional functionality)
1 reply
0 recast
0 reaction
jesse.base.eth 🔵
@jessepollak
so for instance, fnames would in the background be ENS subdomains of *.farcaster.xyz. in that structure: * can charge for them as they see fit * can expand functionality of names permissionlessly * can display in app w/special treatment * get auto compatibility with every app that already integrates ENS
3 replies
0 recast
0 reaction
Varun Srinivasan
@v
maybe a dumb question, but what does ens compat help with? ens integrations afaik are "lookup contract and swap address with result". supporting ens subdomain seems just as difficult as supporting arbitrary namespace? for us, the benefits of having our own namespace are lower gas costs and simpler contracts
3 replies
0 recast
0 reaction
pgpg
@pgpg.eth
It means that people already supporting the ENS namespace can automatically support the FC namespace without having to do any extra work. Personally I think that this could be an option to those who want it. I don't think you even need to do anything special on your contracts.
0 reply
0 recast
0 reaction
