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
The current flow may be a bit confusing for CLI users. They use the "Connect to wallet" page to submit their pubkey address, and when they hit enter the page gives the impression that linking the wallet and the VSP is now completed.
Actually there is a second step which is required, the user needs to copy the redeem script from the VSP and import it into their wallet. This should take place before the user can purchase tickets. This information is currently hidden behind a pop-up modal on the "Tickets" page. I think the UX could be improved if this was included on the "Connect to wallet" page immediately after the pubkey has been submitted.
We should also add a disclaimed that all users, CLI or GUI, would benefit from backing up their redeem script in case the VSP goes offline.
The text was updated successfully, but these errors were encountered:
The current flow may be a bit confusing for CLI users. They use the "Connect to wallet" page to submit their pubkey address, and when they hit enter the page gives the impression that linking the wallet and the VSP is now completed.
Actually there is a second step which is required, the user needs to copy the redeem script from the VSP and import it into their wallet. This should take place before the user can purchase tickets. This information is currently hidden behind a pop-up modal on the "Tickets" page. I think the UX could be improved if this was included on the "Connect to wallet" page immediately after the pubkey has been submitted.
We should also add a disclaimed that all users, CLI or GUI, would benefit from backing up their redeem script in case the VSP goes offline.
The text was updated successfully, but these errors were encountered: