MetaMask / MetaMask/metamask-extension
Load transaction history from other clients
Open
area-activity
area-background
area-transactions
INVALID-ISSUE-TEMPLATE
team-core-extension-ux
type-enhancement
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
Right now we only log outgoing transactions from the same instance of MetaMask.
Long term we should load all transactions from that account, so even if someone has multiple metamask instances, they both appear "up to date".
Related to #133 but kindof is the inverse of it.
Contributor guide
Research direction
Start by examining how this instance logs outgoing transactions and read related issue #133 for the inverse behavior. The intended result is for an account's transaction history to include transactions from other MetaMask instances, so each instance appears up to date.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100