🦊MetaMask
MetaMask extension on desktop browser or MetaMask native app on mobile must be installed in the environment of an enduser in advance.
It’s strongly recommend to check that currently active EOA in MetaMask is equal to the one user logged in or signed up with before requesting signing action because MetaMask are always open to users’ action regardless of Startrail-sdk-js state. ie. It is possible for users to change the EOA account on MetaMask whenever they like.
For Mobile Users
Users are directed to the internal browser within the MetaMask app if they already have the native app installed; otherwise, they are redirected to the app store page.
When users attempt to connect to the MetaMask browser app using the login function, irrespective of whether the native browser app is installed or not, a "false" value is returned. Please handle this scenario appropriately on the client side.
UI
[Popup] Connect with MetaMask
Condition to happen
For the first time user connects to the web-application(URL) with MetaMask.
Impact
Popup request opens up for users.
When to happen in your web-application
When users login to Metamask.
[Popup] Allow this site to switch the network ?
Condition to happen
For the first time user connects Metamask to Polygon or Mumbai network.
Impact
Popup request opens up for users.
When to happen in your web-application
Whenever uses sign for blockchain tx such as create SRR or transfer ownership.
[Popup] Signature Request
Condition to happen
sdk.signMessage is invoked / sdk.signMessage
Impact / 影響
Popup request opens up for users
When to happen in your web-application
When user signs the message sdk.signMessage()
Login to your application with signing requires Popup confirmation to users unlike the case with Startrail login
Network Error
When network error occurs, please go to Settings > Networks on MetaMask, select active network, and change New RPC URL to the live one selected from the list below.
This Network error is more likely to occur in Test environment Mumbai.
Last updated
