Objective:
Is is possible to enable users to interact with a smart contract function using QR codes via the MetaMask mobile app ?
The function accepts four parameters:
id: A unique identifier provided by the user.
from: The sender's address.
_to: The recipient's address.
value: The amount of ERC20 tokens to be transferred.
I beli
Point to be noted: - We are calling erc-20 transfer function in other smart contract function, not directly.
Scenario
Process:
The user inputs the id.
A QR code is generated containing the smart contract function call with the specified parameters (described above).
Scanning the QR Code:
The user scans the QR code using the MetaMask mobile app.
The smart contract function is called, transferring the specified value of ERC20 tokens to the _to address.
Stakeholder review needed before the work gets merged
[ ] Engineering (needed in most cases)
[ ] Design
[ ] Product
[ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
What is this about?
Objective: Is is possible to enable users to interact with a smart contract function using QR codes via the MetaMask mobile app ?
The function accepts four parameters:
id: A unique identifier provided by the user. from: The sender's address. _to: The recipient's address. value: The amount of ERC20 tokens to be transferred. I beli
Point to be noted: - We are calling erc-20 transfer function in other smart contract function, not directly.
Scenario
Process: The user inputs the id. A QR code is generated containing the smart contract function call with the specified parameters (described above). Scanning the QR Code:
The user scans the QR code using the MetaMask mobile app.
The smart contract function is called, transferring the specified value of ERC20 tokens to the _to address.
some reference to the issue
https://github.com/MetaMask/metamask-mobile/issues/1059
Design
No response
Technical Details
No response
Threat Modeling Framework
No response
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
References
No response