MetaMask / MetaMask/metamask-extension

(Ext) [Enhancement] add transaction hash on hardware screen

Open
#31,220 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

extension external-contributor INVALID-ISSUE-TEMPLATE team-accounts-framework type-enhancement
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

**Describe the bug**

## Goal

Double check the transaction hash on a hardware wallet.

## Actual behavior

The transaction hash is not displayed on Metamask UI, it is impossible to verify it.

**Expected behavior**

The transaction hash is displayed on Metamask UI, then one can verify it's the same on the Ledger screen

**Steps to reproduce**

1. Start a transaction signing workflow
2. Look for transaction hash

**Error messages or log output**

```shell

```

**Detection stage**

In production (default)

**Version**

12.14.1

**Build type**

None

**Browser**

Chrome

**Operating system**

Windows

**Hardware wallet**

Ledger

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the transaction signing workflow and the path that sends details to the Ledger display; the issue does not name specific files or tests. Confirm where the transaction hash becomes available and how the hardware-wallet screen is rendered. Done means the hash is visible in MetaMask and can be compared with the hash shown on the Ledger screen.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.