MetaMask / MetaMask/metamask-extension
Question about interacting with minimal smart contracts via MetaMask
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### What is this about?
I’m experimenting with very small Solidity contracts (simple counters and basic payable functions) on EVM-compatible networks. From MetaMask’s perspective, are there any best practices to ensure smooth transaction prompts and UX when interacting with very minimal contracts? Thanks in advance!
### 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
- [ ] 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)
- [ ] Security
- [ ] Legal
- [x] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)
### References
_No response_
Contributor guide
Research direction
The issue names no repository files, tests, or entry points. First clarify whether a documentation change is wanted and which MetaMask interaction or UX behavior should be documented; done would require an agreed scope and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity
- Domain
- blockchain
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100