Content
@
0 reply
26 recasts
26 reactions
charles
@chsh.eth
what feature would you want that would make basescan more useful? (any block explorer for that matter)
3 replies
0 recast
25 reactions
Steve
@sdv.eth
ENS resolving for starters
1 reply
0 recast
6 reactions
christopher
@christopher
are ENS names on Base?
1 reply
0 recast
0 reaction
Steve
@sdv.eth
They’re on mainnet, which imo should be the source of truth for any Ethereum based UI resolving names, regardless if the app is L1, L2, or even L3 centric. Basescan is just a website. Rainbow resolves ens names for base transactions, etc. Also how else would *.base.eth work? 🙈
1 reply
0 recast
2 reactions
christopher
@christopher
but how would you resolve usernames on Base for addresses on L1? the data would have to go through some sort of cross-layer scheme. there’s a ton of technical challenges and trust assumptions that we shouldn’t bake into a UI out of convenience i think
1 reply
0 recast
1 reaction
Steve
@sdv.eth
Welp I was wrong. This doc is outdated and doesn’t include details for base.eth subdomains but I don’t think it’s considered offchain like cb.id. I will say it’s very disappointing as not only an ENS but Ethereum user that a big aspect of onchain data and tokens is interoperability yet we’re kinda placed into this awkward situation. Let people have cheap to nearly free identities on L2, that’s great. But I’m already paying a premium for my ENS, why can’t Base respect that? https://docs.ens.domains/learn/ccip-read
0 reply
0 recast
1 reaction
