MetaMask / MetaMask/metamask-extension
[Bug]: Permissions 7715 - Metrics - New Confirmation page event is sent with incorrect chain id
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
Describe the bug
New Confirmation page event is sent with incorrect chain id. Ie in this case, I'm triggering Permissions for Sepolia, but the chain_id property in the New Confirmation PAge event is set to 0x1
Expected behavior
- We should set the correct chain id
- It seems we could add more properties here, to get a bit more insights, like the type of permission
Screenshots/Recordings
https://github.com/user-attachments/assets/351e9579-116e-4cc0-a1a8-e0def3259e9d
Steps to reproduce
- Open network requests
- Trigger a Grant Permission on Sepolia
- See event is set to chain id 0x1
Error messages or log output
Detection stage
In production (default)
Version
flask
Build type
None
Browser
Chrome
Operating system
MacOS
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the New Confirmation page event described in the issue and reproduce the behavior by triggering a Grant Permission on Sepolia while inspecting network requests. Done means the event reports Sepolia's chain ID instead of 0x1; additional permission properties are suggested but not required by the stated bug.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100