You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In case Umami reuses your smart contracts (not the case at the moment), we probably want to register the list of safes originated from TzSafe somewhere (e.g. SQL) for later potential use, e.g. airdrops. We wouldn't want to accidentally airdrop a safe that has been created from Umami only.
The text was updated successfully, but these errors were encountered:
If we really want to know the safe is created by UI, the way is to find out the origination call and examine tzip16-metadata is marigold or not. tzip16-metadata could be changed after version 0.3.3.
Currently, there is no way to tracking that users are using safe by UI to send transactions unless put something like Google Analytics on UI,
From Slack:
The text was updated successfully, but these errors were encountered: