MetaMask / MetaMask/metamask-mobile
wc:2886ec64d45553a106f066926c18db552369f835d02b9148e261841b10bcaa0b@2?expiryTimestamp=1716810982&relay-protocol=irn&symKey=82ebe0f96d63eaa06c998bc3a64d8f4ef32f5689c59b8e9c3541a649fac23aef
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
### What is this about?
Binance
### Scenario
_No response_
### Design
_No response_
### Technical Details
_No response_
### Threat Modeling Framework
_No response_
### Acceptance Criteria
_No response_
### Stakeholder review needed before the work gets merged
- [X] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [X] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)
### References
_No response_
Contributor guide
Research direction
The issue names no files, tests, entry points, or actionable change; its only subject is Binance. Start by confirming what the opaque title refers to and whether a reproducible problem exists. No completion condition is provided, so the work is not ready to begin.
Written by the indexing model from the issue text.
Assessment
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 5/100