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
Jason
@chaskin.eth
Does the ENS name looks the same? Like just from looking at it can you tell what chain you want to receive the tokens?
1 reply
0 recast
0 reaction
Greg
@greg
yes, looks the same take @slobo.eth for example — he's set 0x534 on mainnet but 0x5D7 on a handful of L2s if you switch networks in metamask extension and type in slobo.eth, you'll see it resolve a different address based on the network
1 reply
0 recast
2 reactions
Wilson Cusack
@wilsoncusack
I think the original image is about being able to give someone a string that represents fully where they want to receive funds. Maybe ens could improve here with a like “preferred network” setting? But still doesn’t solve the same problem.
1 reply
0 recast
1 reaction
Greg
@greg
Yea i understand and see the reasoning. Just expressing that it feels smoother if the user can provide only a name instead of chain info and stuff. The space is moving towards chain abstraction, this seems like the opposite Agree a lightweight ENS standard around “preferred chain” or more granular “preferred payment method” that supports a token address something would be valuable! Can just be a specific format for a text record
0 reply
0 recast
0 reaction
