Base

is there a solution for resolving ens names on base? or we just sol for now?

ENS appears automatically on https://www.yellowcollective.xyz

Is that what to mean?

yeah exactly. ens hasn't deployed their contracts on base yet, so i'm looking for other alternatives for fetching ens names. but i think i can use L1 as a workaround for now.

⌐◨-◨ ‘ing around. 
Nouns Fest founder.
Sundae Songs, music publishing, founder.

www.fishandfriends.fun

yeah exactly. ens hasn't deployed their contracts on base yet, so i'm looking for other alternatives for fetching ens names. but i think i can use L1 as a workaround for now. 

https://github.com/wevm/viem/discussions/2211

The Nouns contract on L1 is a wallet on L2. 

Peer had an RPC switching issue and bid on a wallet instead of the contract.

technically yes https://docs.ens.domains/web/resolution

see https://app.ens.domains/gregskril.eth for example

although the number of people who’ve set a base-specific address is quite low rn

better solution (basically a fallback EVM record for EOAs) is coming soon

I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs. gregskril.com

ok great. ty greg! i didn't realize addresses needed to be set on a per-chain-basis. ie. i haven't done that myself yet. 

any reason i shouldn't make the call on the L1 contracts for now? like are there instances where an address on L1 might not be the same on an L2?