MetaMask / MetaMask/metamask-extension
Please add a basic communication capability or add ascii decoding of incoming transactions.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
Recently found a very popular project with lot of users and thousands Ethers collected where you can be sure MetaMask is the primary method to access it.
But yet, Googling the function names from their selectors as well as the Stellar del Futoro (the name of the Ethereum token) yells no website at all.
The only way left to figure an idea of what this is about is to ask the peoples using it which leaves the Ethereum blockchain as the sole way to communicate. I send multiple ASCII encoded messages to many of it’s users, but none of them figured the bunch of numbers they received was actually text.
I’m currently having a hard time to find a creative way of getting a reply.
In situation like this, it would be really nice to have basic ascii decoding of transactions with data in transaction history.
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
The issue names no files, tests, or entry points; begin by locating the transaction-history UI and how incoming transaction data is presented. Clarify whether the intended scope is ASCII decoding or a broader communication capability, then define the transaction-history behavior and tests that would establish completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, 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