In this tutorial we are going to build a simple application that will allow you to connect to Keplr, you will also have to create a viewing key to be able to see your balance, just as we have done in other examples. But now we will use events to detect if you switch accounts, which is very important to know.
Requirements
For this tutorial you will need to have a React app created. You can find how to do it here. Also, install your dependencies and install Griptape:
# With npm
npm install && npm install @stakeordie/griptape.js
# With yarn
yarn && yarn add @stakeordie/griptape.js
Getting started
This tutorial consist of these steps:
Grip you application
Bootstrap the application
Create a contract definition
Build the application
Grip your application
Go to the src/index.js and import gripApp and getKeplrAccountProvider from @stakeordie/griptape.js package.
src/index.js
import {
gripApp,
getKeplrAccountProvider
} from "@stakeordie/griptape.js";
In order to interact with a contract, you first need to create its definition. First we need to import createContractClient and snip20Def APIs from @stakeordie/griptape.jsto our file src/contracts/sscrt.js Once that is done, we create the definition sscrt to which we are going to assign an id that can be the name you want, we are also going to assign an address of instantiated contract on the blockchain.
Finally, Griptape has SNIP-20 compliant contract definitions, so you don't need to write it yourself.
To build this application we must import boostrap, viewingKeyManager, onAccountAvailable, onAccountChange and coinConvert APIs from @stakeordie/griptape.js, in addition to importing the definition of the contract sscrt that we have just created.
src/App.js
import {
bootstrap,
viewingKeyManager,
onAccountAvailable,
coinConvert,
onAccountChange
} from '@stakeordie/griptape.js';
import { sscrt } from './contracts/sscrt';
Now, you may notice that we are using the event onAccountAvailablewhere you can call the viewingKeyManager from our contract sscrt to know if we already have a viewing key. If that's the case, the key is assigned to setViewingKey state and the function getBalance is called.
Now, in order to detect when changing the account, we have the event onAccountChange, then we show an alert that says it has changed the account, and we will assign it the false value to the setIsAccountChanged state.
src/App.js
const removeAccountChangeListener = onAccountChange(() => {
alert("You have changed your account, please refresh this page.")
setIsAccountChanged(false);
});
viewinkeys...
To create a viewing key, we're going to make an asynchronous request to sscrt.createViewingKey(), if this doesn't return a response, the function ends. If it is the case and if it returns a response then, we parse the result.
Now we send our contract sscrt and our key. We also need to check if a viewing key already exists so we can add it by viewingKeyManager.add() or replace it by viewingKeyManager.set()with the new key.
After having our viewing key, we want to see our balance. For that reason, we create the function getBalance, within the function, we can see that we make an asynchronous request to obtain the value of our viewing key.
If we do not have a viewing key the function ends, but if this is the case, where we have a viewing key, then we went to consult our amount In sscrt.getBalance(), then we convert our amount with the function coinConvert where ... and finally we assign the value of balance to setCoinsstate.