-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Select Station's network from modules, by requests from dApps #748
Comments
|
The case you mention here mustn't be allowed to happen. If user is requested to connect a wallet, or sign operation on a specific network in a DApp, the operation signature request must occur on that network in Massa wallet. It can't go though on another network. |
@LucasF243 let's work on designs. If the need is unclear let's sync about it. |
The Massa blockchain doesn't have this limitation. So we must handle this limitation another way:
Solution 2 requires the wallet to submit all operation it signs. This is not the case today, but this is the direction we want to take now. |
Context
A dApp is unable to make request to switch the wallet network of Station at the moment -> to verify this by dev.
Example Metamask's window when Bridge requests to connect the Sepolia testnet wallet:
Needs:
To avoid user confusion with selected network of the Station, therefore his Wallet,
the selected network
should be always displayed on the module pages. This applies to:Wallet module pages
'Sign' pop up windows
DApps (such as Bridge, Dusa, etc.) should be able to request the change of network to Wallet.
Here is to be discussed about the change of network to whole Station, or to allow modules to run different version (which I am not sure it's possible). cc @gregLibert @peterjah
User flow
How to
tbd by dev
Technical details
Give the technical insights so anyone in the team can tackle the tasks - Dev
QA testing
Does this task require some QA tests ?
If yes, explain how to validate it
The text was updated successfully, but these errors were encountered: