Skip to content
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

[Bug]: Contract Interactions - Triggering mint functions displays the mint recipient instead of the contract address in the To header #24561

Open
seaona opened this issue May 16, 2024 · 0 comments
Labels
Sev2-normal Normal severity; minor loss of service or inconvenience. team-confirmations Push issues to confirmations team type-bug

Comments

@seaona
Copy link
Contributor

seaona commented May 16, 2024

Describe the bug

Whenever we are interacting with a contract, if I trigger the mint function function mint(address to, uint256 amount) with signature 0x40c10f19we see how the recipient is now the address to whom we are minting tokens to, instead of the usual contract address.

Expected behavior

We should see the contract address as recipient, like we do with the rest of contract interactions, that don't have a custom screen.

Screenshots/Recordings

Screenshot from 2024-05-16 11-05-18

mint-recipient-incorrect.mp4

Steps to reproduce

  1. Select mainnet
  2. Go to https://etherscan.io/token/0x6b175474e89094c44da98b954eedeac495271d0f#writeContract
  3. Connect MM
  4. Trigger a mint
  5. See how the recipient is not the contract address but the address you input in the mint function

Error messages or log output

No response

Version

11.15.4 prod (maybe earlier)

Build type

None

Browser

Chrome

Operating system

Linux

Hardware wallet

No response

Additional context

No response

Severity

No response

@seaona seaona added type-bug Sev2-normal Normal severity; minor loss of service or inconvenience. labels May 16, 2024
@bschorchit bschorchit added the team-confirmations Push issues to confirmations team label May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Sev2-normal Normal severity; minor loss of service or inconvenience. team-confirmations Push issues to confirmations team type-bug
Projects
Status: To be fixed
Status: To be fixed
Development

No branches or pull requests

2 participants