MetaMask / MetaMask/metamask-extension

Make use of bytecode metadata to improve confirmation dialog

Open
#7,274 10 comments 2 reactions 0 assignees View on GitHub
needs-triage team-confirmations-planning type-enhancement
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

The Solidity compiler stores the hash of contract metadata in the bytecode of each deployed contract. This metadata could be used to improve the confirmation dialog to display the natspec description, decode the function call arguments and display a link to the source code.

Details: https://chriseth.github.io/notes/talks/trust_gap_meetup

![image](https://user-images.githubusercontent.com/9073706/66627831-2b774200-ebfd-11e9-9fa0-919934dfd16d.png)

cc @frankiebee @rekmarks

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by reading the confirmation-dialog behavior and the linked Details talk, then map how deployed-contract bytecode metadata could provide NatSpec text, decoded arguments, and a source-code link. Done means the dialog uses that metadata for all three improvements.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.