It's possible that users access the Vaults UI using an old, not current IPFS hash which may not contain the latest changes/features e.g. they bookmark IPFS hash instead of using specific Vaults URL which utilizes jumper.
We should be able to detect this, notify the user and offer link to re-direct the user to the most recent referenced Vaults IPFS hash (or simply to the jumper which will automatically do this).
Description of the Design
Detect if user is using non-current IPFS hash
If yes - display dialog notifying them 'Note: You are attempting to access an older app. See latest version.' (hyperlinking 'latest version')
If user clicks hyperlink, they are redirected to jumper which automatically routes them to most recent referenced UI
Presumably we shouldn't stop them from being able to access the old UI hash if they wish to proceed? Up for discussion but if we do, we should let them bypass dialog and continue to it.
What is the Problem Being Solved?
It's possible that users access the Vaults UI using an old, not current IPFS hash which may not contain the latest changes/features e.g. they bookmark IPFS hash instead of using specific Vaults URL which utilizes jumper.
We should be able to detect this, notify the user and offer link to re-direct the user to the most recent referenced Vaults IPFS hash (or simply to the jumper which will automatically do this).
Description of the Design
Presumably we shouldn't stop them from being able to access the old UI hash if they wish to proceed? Up for discussion but if we do, we should let them bypass dialog and continue to it.
Security Considerations
Unknown
Test Plan