Connect algob project settings with a webapp

In this guide we explain how an algob project can be easily connetced/integrated with your dapp.

About @algo-builder/web

We recently released @algo-builder/web package which allows you to interact with contracts easily. It is designed to be used with web dapps as well as scripts and user programs. For more information check out the using-web section.

About algob

Algob is the CLI (Command Line Interface) for Algo Builder. Think about it as an Ethereum Truffle but for Algorand projects. algob can be included as a library using yarn add @algo-builder/algob and then import it using import * from '@algo-builder/algob' or can be run from command line as described in the project README file.

Usage in Webapp

Currently, it is not possible to use algob directly in a web app, because algob uses nodejs file system. Because of this issue, @algo-builder/web was designed to provide common functionality and support dapp development.

Project structure:

├── assets
│   ├── TEAL files
│   ├── PyTEAL files
├── scripts (algob project scripts)
│   ├── deploy.ts
│   ├── run.ts
├── src (react frontend code)
│   ├── app.js
│   ├── index.js
├── test
│   ├── JS test files
│   ├── .mocharc.json (optional)
├── algob.config.js
├── package.json (common for algob & react-app)

Contracts are present in /assets, scripts are present in /scripts folder, and dapp’s frontend code is available in /src folder.


In an algob project we persist checkpoints. This is helpful to store deployment information (transaction IDs, asset indexes, etc.) for later use (in future scripts).

  • The checkpoint files are saved in artifacts/scripts/ in a human-readable YAML format. Contains:
    • Deployed informaton (assetID, appID, creator, txID, etc.)
    • Logic Signatures (Delegated/signed OR unsigned)
  • Cached information (eg. compiled smart contracts) are stored in artifacts/cache (contract filename, compiled hash, TEAL code, etc.)

Since, @algo-builder/web API can’t load data from files in your webapp, user either needs to:

  • copy these checkpoints from /artifacts to your webapp (inside /src/), so it can be bundled by webpack and deployed.
  • OR, you can override your react-app config and remove removeModuleScopePlugin (this allows imports outside /src folder in react-app)

After you’re able to import checkpoint files (in /artifacts/*.yaml), you can simply add a yaml loader to load files & read data in your react source code. For eg. (reading a logic sig from checkpoints data and getting the contract’s address). As a reference, checkout config-overrides.js file.


For reference checkout algo-builder-templates/htlc project. It’s a webapp with integrated with an algob project. You firstly deploy the smart contracts using algob deploy. The deployed information in checkpoints is used by the dapp’s frontend (for eg. ASA ID).

We have also added a config-overrides.js to override webpack.config.js:

  • add a yaml loader
  • allow imports from outside /src in react app (so these could be bundled in webpack config)

Helper methods

All web-modes classes expose helper methods to improve developer’s experience with the framewok. These methods can be also found under the same name and for most of the time with the same interfaces in Runtime, and Deployer. These methods enable users to use algosdk types like Transaction and SignedTransaction. List of the methods:

  • makeTx - createsTransaction object from execParams
  • signTx - signes Transaction and returns SignedTransaction object.
  • makeAndSignTx - combines funcnionality of the two methods listed above
  • sendTxAndWait - sends SignedTransaction and waits for the response that is returned to the user.