Description
Currently, users with locked tokens can use the MentoLock component to create another lock, which we don't want. While we can't prevent this on a contract level, we can do it in the UI. To prevent this, we made a hotfix to disable locking in the UI entirely.
This issue is to implement logic to hide the MentoLock component when:
Users are not connected
Users are connected & already have an existing lock.
Hiding the component is better, as showing users the functionality they cannot use is not a good experience. However, if you see value in adding designs or other messaging, let's discuss in the comments for this issue
Acceptance Criteria
[ ] MentoLock component is hidden when a user with an existing lock is connected.
[ ] MentoLock component is hidden when a user is not connected.
Description Currently, users with locked tokens can use the MentoLock component to create another lock, which we don't want. While we can't prevent this on a contract level, we can do it in the UI. To prevent this, we made a hotfix to disable locking in the UI entirely.
This issue is to implement logic to hide the MentoLock component when:
Hiding the component is better, as showing users the functionality they cannot use is not a good experience. However, if you see value in adding designs or other messaging, let's discuss in the comments for this issue
Acceptance Criteria