Content pfp
Content
@
0 reply
26 recasts
26 reactions

ripe↑ pfp
ripe↑
@ripe
is there a solution for resolving ens names on base? or we just sol for now?
3 replies
0 recast
2 reactions

Greg pfp
Greg
@greg
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
1 reply
0 recast
0 reaction

ripe↑ pfp
ripe↑
@ripe
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?
1 reply
0 recast
0 reaction

Neokry pfp
Neokry
@neokry
smart contract wallets ie multisigs are not guaranteed to have the same address on multiple chains. ie if someone uses xyz.eth for a multisig on L1 there’s a chance it won’t be deployed in base or deployed with a different address
1 reply
0 recast
1 reaction

ripe↑ pfp
ripe↑
@ripe
good to know! super helpful info. ty ty
0 reply
0 recast
0 reaction