Add button that uses Web3 provider to send transaction
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- blockchain, web-dev
Research direction
Start in the test dapp at the existing ethers provider and the create token and deploy contract button entry points. Trace how their current factories create transactions, then identify where a top-of-page web3/ethers toggle can select the implementation. Done means ethers remains the default, web3 produces the same transactions, and both buttons work in either mode.
Written by the indexing model from the issue text.
Description
Currently, the test dapp only uses ethers.js for instantiating a provider. We need to also use web3.js, because many dapps use that exclusively. For us to properly test and QA MetaMask, we should test against the same tools that dapps use. Also, some functionality (e.g. batch transactions) are better supported by web3.js than ethers.
To start, let's just allow the test dapp to use web3 in place of ethers wherever it is currently used
- add a radio button toggle somewhere on the top of the page. The options in the toggle should be "web3" and "ethers"
- the toggle should default to ethers
- if ethers is selected, the create token and deploy contract buttons should behave as they do today
- if web3 is selected, create token and deploy contract should use web3 instead of the current "factories" created by the ethers provider, however the transactions created by the buttons should be the same
- Dominant language
- JavaScript
- Stars
- 642
- Forks
- 369
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from MetaMask/test-dapp
-
vvxg66w6tx Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 20/100
-
Add EIP-7702 example Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
team-wallet-framework wf-project-standardization
Difficulty 4/5 3-5 days Newbie friendliness 42/100
All issues in MetaMask/test-dapp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·