In this example project we'll walk through how to run a Fuel Indexer service that uses WASM-based execution. We'll go through project structure, how to actually use the service, as well as a few key concepts.


First we'll walk through the basic setup and usage of the project

➜  tree . -I 'target/'
├── contracts
│   └── counter
│       ├── Forc.lock
│       ├── Forc.toml
│       ├── out
│       │   └── debug
│       │       ├── counter-abi.json
│       │       └── counter.bin
│       └── src
│           └── main.sw
├── counter-indexer
│   ├── Cargo.toml
│   └── src
│       └──
├── frontend
│   └── index.html
├── manifest.yaml
├── schema
│   └── counter.graphql
└── web-api-and-fuel-node
    ├── Cargo.toml
    └── src

11 directories, 13 files

With this recommended project structure you'll notice:

  • contracts is where our Sway smart contract counter is located.
  • web-api-and-fuel-node is a combination of a tiny HTTP web application, and a simple Fuel node, that we use to pass messages to/from the counter contract.
  • frontend is unused (as there is no frontend for this small example)
  • manifest.yaml is the configuration file for the index that we will be using.


In this section we'll cover the exact steps needed to spin up this example.

Database setup

We'll start by creating a database. This step assumes some familiarity with creating Postgres roles and databases. In this example we're using an indexer database owned by a postgres role without a password.

Next we'll bootstrap our database by running some migrations.

DATABASE_URL=postgres://postgres@ bash scripts/

Starting the web server & Fuel node

As previously mentioned, web-api-and-fuel-node contains both a tiny web server used to pass messages to/from our Sway smart contract, as well as our Fuel node that we use to interact with the blockchain. We will start both of these services with the following command.

cd fuel-indexer/examples/counter/web-api-and-fuel-node && cargo run

Start the Fuel Indexer service

With our Fuel node and web server up and running, we'll next start our Fuel Indexer service.

cargo build -p fuel-indexer

./target/debug/fuel-indexer --manifest examples/counter/manifest.yaml

Send a transaction to the smart contract via the web server

curl -X POST | json_pp

Verify data was posted to the database

In this example we just created an entity with id = 1

➜  echo "SELECT max(id) FROM counter.count;" | psql -U postgres -d postgres
(1 row)

So that's what we query for

curl -X POST -H 'content-type: application/json' -d '{"query": "query { count(id: 1) { id count timestamp } }", "params": "b"}' | json_pp
      "count" : 1,
      "id" : 1,
      "timestamp" : 123

Hooray! 🎉 we've successfully created our first Fuel Indexer service.