# Providers

As explained previously, the 0xcert Framework tends to be platform-agnostic, thus it is not created for merely one blockchain or one specific platform. It aims to provide a consistently optimal developing experience, regardless of the platform you employ. To achieve this, the 0xcert Framework consists of several modules, and each module needs a provider object to tell the module how to operate.

Each provider operates on the same principles, but can also have its own distinctive characteristics. The current version of the Framework supports the Ethereum and the Wanchain blockchains. Soon, more platforms will be added.

Even within the same blockchain, you can use multiple providers depending on your needs. If you would like to communicate with the blockchain on the front-end, you could use MetamaskProvider, while for communication on the back-end you could use HttpProvider. For more information about other providers for Ethereum, such as Bitski, please click here, and to learn more about providers for Wanchain, please click here.

In this guide, we will be using the MetaMask provider for the Ethereum blockchain. MetaMask is a popular plug-in that allows you to create and store the private keys for your Ethereum account inside your browser or mobile device. It works as a bridge between your browser and the Ethereum blockchain through its own infrastructure. MetaMask can also be paired with hardware wallets such as Ledger or Trezor.

Live example

Click here to check the live example for this section.

# Installation process

We recommend you employ the provider module as an NPM package in your application.

$ npm i --save @0xcert/ethereum-metamask-provider

On our official GitHub repository, we also host a compiled and minimized JavaScript file that can be directly implemented into your website. Please refer to the API section to learn more about other providers.

# Usage overview

To start developing the application, we have to first instantiate the MetamaskProvider provider class. This is usually only needed once within the application.

import { MetamaskProvider } from '@0xcert/ethereum-metamask-provider';

const provider = new MetamaskProvider();

MetaMask needs to be authorized and unlocked to be used on the website. This is specific to this provider. Therefore, before you start interacting with the Ethereum node, you should check whether the MetaMask account has been enabled. If not, you have to enable it, as shown in the example below.

if (!await provider.isEnabled()) {
  await provider.enable();

Now that we're connected to the Ethereum blockchain, we can begin performing query and mutation requests.


When you connect to MetaMask, provider.accountId represents your selected account.


Make sure your MetaMask account is connected to the Ethereum Ropsten network.


To perform this deployment step, you'll need to pay some gas on the Ethereum network. You can get free Ether in your wallet on the Ropsten network via this link.

# Error handling

If any error happens on the blockchain, providers are able to handle it and throw a meaningful error, so you know exactly what went wrong.

Error example:

  name: 'ProviderError',
  issue: '001001',
  original: '', // optional
  message: 'Sender does not have sufficient balance.'