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
Context
Today, any dapp or software can add an asset in your massa wallet, just by calling an endpoint. It would make sense that user must confirm the add, to avoid spamming
todo:
Add a new wails workflow to confirm token addition. ( I think the password is not needed for this one)
The text was updated successfully, but these errors were encountered:
Determine the flow here please @peterjah .
If I understand there are 2 ways of adding a token:
A) user manually via UI,
B) via API endpoint, a DApp can call it and add the token into user's assets, without user's permission (??)
If that's the case, we must create the confirmation only for B).
Context
Today, any dapp or software can add an asset in your massa wallet, just by calling an endpoint. It would make sense that user must confirm the add, to avoid spamming
todo:
Add a new wails workflow to confirm token addition. ( I think the password is not needed for this one)
The text was updated successfully, but these errors were encountered: