MetaMask / MetaMask/metamask-extension

(Ext) Add ability to identify failed txs and reason why over time - health check - success/failure rate monitoring

Open
#11,675 0 comments 0 reactions 0 assignees View on GitHub
area-hardware extension external-contributor hardware-trezor INVALID-ISSUE-TEMPLATE T08-featureRequest team-accounts-framework team-hardware-wallets-deprecated type-enhancement
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

**Describe the bug**
Many factors cause failed transactions but they are very frustrating to users and cause confusion, loss of funds to miner fees, and sometimes repeat to the point where users cannot complete an action they are trying to do. Add the ability to have general high level view of top failed tx reasons and increase/decrease of those vs successful txs over time, in a privacy preserving manner.

**Steps to reproduce (REQUIRED)**
Steps to reproduce the behavior, libraries used with version number, and/or any setup information to easily reproduce:

**Expected behavior**
A clear description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Browser details (please complete the following information):**
- OS: [e.g. OS X, Windows]
- Hardware Wallet: [e.g. Trezor Firmware version 1.8.3, Ledger Nano S Firmware version 1.6.0]
- Browser: [e.g. Chrome Version 79.0.3945.79 (Official Build) (64-bit), Firefox Browser 71.0 (64-bit)]
- MetaMask Version: [e.g. 5.0.2]

**Additional context (Error Messages, etc.)**
Discussed because two gas limit estimation issues were identified in v9.8.3 and v9.8.4 that existed since v9.8.0.

Contributor guide

Open the contributing guide

Research direction

No files, tests, reproduction steps, or entry points are named. Start by locating transaction status and error handling, then define privacy-preserving acceptance criteria for identifying top failed-transaction reasons and tracking their success/failure trends over time.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
blockchain, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.