The following article aims to be a guide through integration of a key management strategy on client side of your Decentralised Application on agv Network.

The following wallets will be discussed:


  • Metamask: Metamask is a browser add-on that manages a user’s Ethereum wallet by storing their private key on their browser’s data store and the seed phrase encrypted with their password. It is a non-custodial wallet, meaning, the user has full access and responsibility their private key. Once lost, the user can no longer control the savings or restore access to the wallet. For more...

High-level steps:

The overall steps would essentially remain the same for any client side application to talk to the blockchain:

  1. Set up Web3: web3.js is a javascript library that allows our client-side application to talk to the blockchain. We configure web3 to communicate via Metamask/Wallet Connect/Portis.

    Note: Refer Web3.js docs to add web3 to your project

  2. Set up Account: To send transactions from (specifically for transactions that alter the state of the blockchain)
  3. Instantiate contracts: Once we have our web3 object in place, we next instantiate our deployed contract, with which we interact.
  4. Call functions: we fetch data via functions in the contract - through our contract object.