How to Interact with Smart Contracts on Ethereum Blockchain

Now that we know that we have a connection between our browser and our Ethereum node, let's make a connection to our contract. Remember that in order to create a JavaScript representation of our contract, we need to load the ABI. Let's copy the ABI that we compiled earlier into this project. Only I'm going to rename it tab.json at the end, so I'm going to rename it to counter_soul_counter_abi.json. In the code, we can use a JavaScript require to load this .json file. This is possible because of the NWB config. If you're building using another method, you can always just copy and paste the ABI here in the code. I'm going to type let counter_abi equal require, and I'm going to require the file. We can log it out to make sure it loaded. See it in the log? Great. Also remember that our particular instance of the counter contract lives at a specific address on the blockchain. I hope you saved the contract address from last time. I'll copy that address, and I'm going to define a variable, let contract address equal, and then paste the hash in. And remember, this is an important point. When you deploy your website, it lives on a specific domain name. When you deploy your contracts, they'll live at a specific address. So you'll have these addresses hard-coded, or at least in a config file, committed into your code. So now that we have our ABI and our contract address, we can create a new contract object. We do that by saying var counter contract equals new web3.eth contract. We pass the two arguments counter_abi and contract address. Let's assign this to window so that we can inspect it in our console. So looking at counter contract, notice that the functions that we want to call are in methods on this object. In order to get the value of our counter, we have counter contract dot methods dot get. But notice here there are two important functions on get send and call. There's a difference between them. We use call when we want to call a function locally and send when we want to send a transaction to the network. Getting the value of the counter can be done locally, so let's use dot call. However, calling out to our Ethereum node is async, so dot call will return a promise. So we call counter contract dot methods dot get dot call dot then and we take the count and we'll log out the count. Great, we got our count. Now let's add a function for this and show the value in our view. First thing we'll do is we'll add a div and placeholder to show our counter value and we'll update our button to call check counter. Let's define our check counter function. First we'll type window dot check counter equals function. Then on the contract, we'll call counter contract dot methods dot get dot call dot then, which will be given account. Then we find the counter value element by ID. And we set the inner text equal to the count. Flip back to our browser and let's try it out. Great, it works. The next thing that we need to do is send a transaction from our browser to mut ate that counter value. Now let's mutate our contract state by incrementing the counter. To do this, we'll need to send a transaction to the blockchain. We can check this out in our console. The counter contract object has functions that help us build this transaction. It looks like this. Counter contract dot methods dot increment. We'll call dot send on this. Dot send means send a transaction. So recall that to send a transaction, we need to specify the sending account as well as the amount of gas that we're willing to spend to run this transaction. Let's grab our first account address and try it. We'll set our account to a variable. And then call counter contract dot methods dot increment dot send passing from our account. Gas will just put one million dot then and capture the error and response and log it out. Hmm, the promise that returns isn't resolving. Let's check our logs to see if we can figure out why. In the network tab, we can see the response that says authentication needed, password or unlock. We forgot to unlock our account. So let's do that first. We'll type web three dot ETH dot personal dot unlock account pass our account address and then the password ABC 123. Looks good. Now let's start re-setting our increment transaction. Looking at the network tab, it looks like it went through. Let's mine this transaction. That can get we'll do minor dot start. Got our transaction and minor dot stop. Let's check our counter again. It works. All right, let's add a button which will increment this counter for us. We'll set our from account. So we're going to add a new button where on click calls increment counter. And let's define our increment counter function. We'll call window dot increment counter equals function counter contract dot methods dot increment dot send from from account gas one million. And let's look back over to our browser and press the increment counter button. And we need to mine the transaction. Now I don't know about you, but I'm getting tired of starting and stopping the minor manually. So let's just leave the minor running. Now let's increment the counter. And if it doesn't work, you might need to unlock your account again. Let's wait a couple seconds for it to be mined. Then check the counter value. It works. Let's try that again. Wait for the minor. Click it again. It works. Fantastic. So there's a really basic web three Ethereum tutorial. I think the most obvious improvement I'd like to make here is to have the counter value automatically update in the view once the transaction has been mined. We'd use web sockets to push the new information from the RPC server to the browser. And then we could update this value automatically without the user having to check manually . But using web sockets is something we'll cover in a later video. In fact, we have a lot to cover in other videos. This tutorial shows you the key connection and how to build D apps. But there is so, so much more to cover. For example, I want to talk about the specifics of writing real world solidity contracts, taking performance and security into account. I want to talk about building apps where our users can trade collectibles or vote on resolutions and make provably fair agreements. I want to go beyond Ethereum and talk about distributed storage with IPFS and talk about high throughput transactions with sidechains and state channels. I want to talk about how to accept Bitcoin payments on your website without any bank or credit card intermediary. And of course, we're going to talk about how to build your own cryptocurrency. We'll discuss what it means to create your own tokens and how to integrate them into your own apps. For now though, let's celebrate our success connecting our Ethereum network to a browser app. We're entering a brand new world and we've got a lot to build. (upbeat music) (ambient music)