Content
@
https://warpcast.com/~/channel/safe
0 reply
0 recast
0 reaction
Vinay Vasanji
@vinayvasanji.eth
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
2 replies
0 recast
0 reaction
scottrepreneur
@scottrepreneur.eth
Check out some of the tooling around @safe ! This is doable for sure https://warpcast.com/alexgrover.eth/0xe8caf0ac
1 reply
0 recast
0 reaction
Vinay Vasanji
@vinayvasanji.eth
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
1 reply
0 recast
1 reaction