Safe

If I create a SAFE on Base does that SAFE only accept Base tokens? I think the answer is yes but just want to confirm

One workaround to this usability problem (e.g. someone sending the wrong token to the SAFE) is to give the wallet a @basename 

That way it is unequivocally associated with the L2 and marginally reduces the risk of someone sending non-Base tokens to that address - not perfect, but better than a vanilla ENS

Web3 naming (.base) for the next billion+ users on BASE | Native Name Service | http://basename.app

ENS supports setting a Base-specific address! I've set it on gregskril.eth as an example https://app.ens.domains/gregskril.eth

though I'll admit wallet support isn't near where it should be yet... working on it

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

Yes saw that! Thing I'm unclear about is is it possible to ONLY set a Base address and not have any other address associated with the ENS?

The issue with a SAFE that's restricted to a single L2 is you really don't want someone to accidentally send the wrong token to that address — my OtoCo safe can't receive mainnet

Onchain Tools

shared this before, but feels fitting for this channel, and saved me today

deploy a multisig with the same address on every chain

https://multisafe.app

Check out some of the tooling around @safe ! This is doable for sure

For some reason the SAFEs that I have deployed (contract versions: 1.3.0+L2 and 1.4.1+L2) don't allow me to replicate my Base SAFEs on other chains

Yeah. Likely need to start with one that _is_ deployable on all chains. Not sure how easy it is to do with the og ones.

Check out some of the tooling around @safe ! This is doable for sure
https://warpcast.com/alexgrover.eth/0xe8caf0ac