Content
@
0 reply
0 recast
0 reaction
Jason
@chaskin.eth
Justifying the present is a natural thing to gravitate toward when one feels powerless to build the future. But we are building the future.
5 replies
1 recast
15 reactions
Greg
@greg
You can store all of this under a single ENS name Specify address per chain: https://docs.ens.domains/ensip/11 Resolution always starts from the same place so app devs don’t need to manage a bunch of RPCs. The way to read from L2s is with EIP3668 (https://eips.ethereum.org/EIPS/eip-3668) + ENSIP10 (https://docs.ens.domains/ensip/10)
1 reply
0 recast
2 reactions
nicholas 🧨
@nicholas
Computers should figure this out. Humans shouldn't have to
0 reply
0 recast
1 reaction
Marius van der Wijden
@vdwijden
Why would vitalik.eth be unclear? Its eth mainnet and should be resolved with mainnet. vitalik.base.eth should be resolved like this: base.eth resolved on ethereum mainnet, vitalik.base on base ENS resolver. I thought this was how ENS is intended to be used. You can add optional fields to base.eth to help the reolver figure out where to resolve the subdomains afaik. I recently had a great conversation with @matoken where he explained how they are thinking about this. I think overloading the ENS with useless information about the chain etc. will impact UX significantly
1 reply
0 recast
1 reaction
nkemjika.eth
@nkemjika
I am guessing that the use of the chain and ens root will be optional?
1 reply
0 recast
0 reaction
Nchibinh26
@nchibinh26
Bước tiến cần dũng cảm và quyết tâm, đừng ngần ngại!
0 reply
0 recast
0 reaction
