Skip to content

Create Remove_Web3.js_injection_from_dapp.md #168

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
BrianHHough wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Create Remove_Web3.js_injection_from_dapp.md #168

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions Remove_Web3.js_injection_from_dapp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
BOUNTY_NAME : Remove Web3.js injection dependency from your Dapp

LINK_TO_ORIGINAL_BOUNTY_ANNOUNCEMENT : https://explorer.bounties.network/bounty/2326

LINK TO APPLY FOR BOUNTY : https://explorer.bounties.network/bounty/2326

BOUNTY_AMOUNT : 10 DAI [$$10.07 USD]

OTHER_DETAILS : A common issue we see in Dapps is that their developers assume that a Web 3 browser == MetaMask and that they will magically have access to a Web3.js library, injected inside the page on their behalf. We see this implicit dependency & injection as a bad practice that needs to disappear for the ecosystem to move forward. Developers should import the web3 convenience library of their choice and build their Dapp on top of that, just as they do for other Javascript libraries. Opera exposes a Web3 Provider (window.web3.currentProvider) which you need to instantiate your own web3 object from. Removing this dependency on MetaMask Web3.JS library injection will make your dapp more compatible and resilient with other Web3 browsers such as Opera and make it future-proof as this will likely be deprecated.