by Igor Yalovoy
Every blockchain developer should know these Web3 and Metamask use cases
On November 2nd MetaMask and other dapp browsers will stop exposing user accounts by default. This will make some code from this paper to break. I will publish updated version with web3 1.0 and new MetaMask interface.
We are going to use Web3 0.20 version, not Web3 1.0. The code for Web3 1.0 would be different.
Every dApp has its mission, but the way they interact with Metamask is similar. In this article, we’ll cover the ten most common practices to handle Web3/Metamask interactions.
#1. Detect Metamask and instantiate Web3
According to docs, here’s the best way to do it.
What is going on here? First, we check if Web3 was injected. If it is injected we create a new instance using the injected provider. Why is that? Because we want to use our library version, not the one injected by Metamask.
If Web3 is not present, we try to connect to a localhost provider, like ganache.
#2. Check if Metamask is locked
Metamask can be installed but locked. In order to interact with a user account and send transactions, the user has to unlock Metamask.
#3. Check the current network
There are many test networks beyond the main network. Typically your contract is deployed to a certain network. You want to be sure that the user runs Metamask on the same network.
#4. Get the current account
A user may have multiple accounts at Metamask, but they expect the dApp to interact with the current one.
You should always grab the account from the Web3 instance. Do not keep and reuse it, because the user may change their account at any time.
#5. Get the balance on the current account
Here we use the function
getAccount from #4 and call
#6. Detect that the current account has changed
A user may change their account at any time. You dApp should be ready for that and react properly.
#7. Detect whether Metamask is locked/unlocked
Similar to #6. A user may lock/unlock anytime. Your dApp should handle it correctly.
#8. Handle cancel/confirm
Once a user interacts with your dApp, you have to send a transaction using the Web3 API. A user may press the cancel or confirm button on the Metamask popup. This may lead to UI inconsistency if not handled correctly.
In order to return instantly with the transaction hash, call
#9. Get the transaction receipt
Once your dApp transaction is mined, a transaction receipt becomes available. Yet there is no event/notification, so we have to implement a poll mechanism.
#10. Listen for Web3 events
Solidity events are great. They allow switching from ugly polling to just a push mechanism, assuming your contract implements all necessary events. You can completely avoid polling and just react to events. Event callback returns a lot of data, but we are mostly interested in
Whatever your dApp is about, it still has to perform common tasks, such as detecting Web3, getting the account state and balance, recognizing the current network, and handling transactions and events. We’ve gone over how it can be done using ten code snippets.
A lot of examples here use methods which might throw an error because of Metamask’s state or some variables being undefined at the moment of a call. You should wrap them in
try/catch in a production environment.
Async/await has been used here for simplicity. It can be replaced with Promise then/catch.
How to Create and Deploy Your Own EOS Token
We are going to figure out what is EOS token and how you can create and deploy one yourself.hackernoon.comHow Much Does It Cost to Run DApp in 2018
You think your AWS or Digital Ocean bill for your website is killing you?hackernoon.comDifference Between Ethereum and EOS Tokens
Ethereum has ERC-20 token and EOS has EOSIO.Token. They serve the same purpose, but are they the same?medium.com
Originally published at ylv.io on October 15, 2018.