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
As a Status app user, I want to be able to scan Metamask QR addresses, so I can send assets or save the address, if Status supports the network.
Description
Metamask stores addresses in QR codes with the following format:
ethereum:0x38cf6E0Ba4C4530735616e1Ee7ff5FbCB726fBd2@0xa
ethereum: - prefix described in EIP-67 0xa - chain ID suffix described in EIP-155
Since Status addresses do not include these parts, we need to convert the data from Metamask QR addresses to a format our app can work with for sending, saving, and editing network preferences.
Conversion
ethereum: - prefix should be ignored and removed on our side
Status addresses follow the EIP-3770 format, which maps hexadecimal chain IDs to readable chain prefixes.
After converting, ethereum:0x38cf6E0Ba4C4530735616e1Ee7ff5FbCB726fBd2@0xa should become oeth:0x38cf6E0Ba4C4530735616e1Ee7ff5FbCB726fBd2
This conversion should happen in all instances of scanning addresses, such as
universal scanner on home pages
scanner for saving addresses in wallet settings
scanner for sending
It should be implemented on all supported platforms.
If the address contains an unsupported network, the user should receive an error "Address contains unsupported network" Users should not be able to save addresses with unsupported network prefixes to avoid problems in the send flow and sending assets to wrong networks.
Implementation.
Design cases for all relevant instances of QR scanner in Figma
Implement the conversion and validation logic
Submit the feature for review and approval by the Status QA team
Acceptance Criteria
User scans Metamask QR addresses with relevant scanner instances
Chain IDs are converted to prefixes according to EIP-3770
ethereum: prefix is ignored and removed from address
User receives a designated error for unsupported networks
User can save addresses with supported and unsupported network prefixes
Future Steps
Consider supporting Metamask's "Payment request" QR format including additional data like requested amount and token ID.
The text was updated successfully, but these errors were encountered:
User Story
As a Status app user, I want to be able to scan Metamask QR addresses, so I can send assets or save the address, if Status supports the network.
Description
Metamask stores addresses in QR codes with the following format:
ethereum:0x38cf6E0Ba4C4530735616e1Ee7ff5FbCB726fBd2@0xa
ethereum: - prefix described in EIP-67
0xa - chain ID suffix described in EIP-155
Since Status addresses do not include these parts, we need to convert the data from Metamask QR addresses to a format our app can work with for sending, saving, and editing network preferences.
Conversion
ethereum: - prefix should be ignored and removed on our side
Status addresses follow the EIP-3770 format, which maps hexadecimal chain IDs to readable chain prefixes.
More networks: chains_mini.json file on chainid.network
After converting, ethereum:0x38cf6E0Ba4C4530735616e1Ee7ff5FbCB726fBd2@0xa should become oeth:0x38cf6E0Ba4C4530735616e1Ee7ff5FbCB726fBd2
This conversion should happen in all instances of scanning addresses, such as
It should be implemented on all supported platforms.
If the address contains an unsupported network, the user should receive an error "Address contains unsupported network" Users should not be able to save addresses with unsupported network prefixes to avoid problems in the send flow and sending assets to wrong networks.
Implementation.
Acceptance Criteria
Future Steps
Consider supporting Metamask's "Payment request" QR format including additional data like requested amount and token ID.
The text was updated successfully, but these errors were encountered: