Indexer

The MUD Indexer is an offchain indexer for onchain applications built with MUD.

Why an offchain indexer?

Reads with onchain apps can be tricky. What does it mean to be able to query the Ethereum network? Technically, given a node with a fully synced state, we can explore just about everything using the EVM, but the “exploring” would be looking at raw storage slots for accounts corresponding to smart contracts. A way around this exists by providing view functions on smart contracts: these effectively are just wrappers around raw storage and expose a more friendly API. Instead of having to figure out where the balances for an account are stored in the storage tree, we now can call a function that does the lookup via Solidity via an RPC endpoint.

The issue with view functions is that for any sophisticated application the calls needed to get the “full picture” of the state from the chain are very complex. Servicing so many view function calls also creates the need to run a set of dedicated nodes instead of relying on a third-party provider's free tier.

The MUD indexer solves this problem by listening to the MUD store events to automatically replicate the entire onchain state in a relational database. Having such a database allows clients to quickly and efficiently query the onchain data.

Installation

These environment variables need to be provided to the indexer to work:

Schemaful indexing to SQLite via npx

To run the indexer directly on your computer using SQLite:

1. Start a World to index. An easy way to do this is to use a TypeScript template in a separate command line window.

2. Set RPC_HTTP_URL.

   export RPC_HTTP_URL=http://127.0.0.1:8545

3. Run the indexer. If necessary, install it first.

   npx -y -p @latticexyz/store-indexer@next sqlite-indexer

Note: The indexer.db is persistent if you stop and restart the indexer. If that is not the desired behavior (for example, because you restarted the blockchain itself), delete it before starting the indexer.

Schemaless indexing to PostgreSQL via npx

The schemaless indexer stores MUD table records into a single monolithic table. This allows it to index the data of all tables of all MUD Worlds on a chain efficiently, but querying for data is limited to filters on address, tableId, and the record's key. Since the record's data is stored as encoded bytes blob, it's harder to query based on it in SQL. The main purpose of this variant of the indexer is to efficiently hydrate a MUD client, which decodes the data.

1. Start a World to index. An easy way to do this is to use a TypeScript template in a separate command line window.

2. Set the environment variables.

   export RPC_HTTP_URL=http://127.0.0.1:8545
   export DATABASE_URL=postgres://127.0.0.1/postgres

3. Run the indexer. Install it first if necessary.

   npx -y -p @latticexyz/store-indexer@next postgres-indexer

4. Open a separate command line. In it, specify the database and run the indexer frontend, which is responsible for serving the data to the client.

   export DATABASE_URL=postgres://127.0.0.1/postgres
   npx -y -p @latticexyz/store-indexer@next postgres-frontend

Schemaful indexing with PostgreSQL via npx

The schemaful indexer dynamically creates a PostgreSQL table every time it encounters a new MUD table. It then decodes the MUD events and stores it in the PostgreSQL table with a matching schema. This approach doesn't scale well to all tables of a chain, but it is a convenient way to index the tables of a particular MUD World and have access to powerful SQL queries on its data.

1. Start a World to index. An easy way to do this is to use a TypeScript template in a separate command line window.

2. Set the environment variables and start the indexer, installing it if necessary.

   export RPC_HTTP_URL=http://127.0.0.1:8545
   export DATABASE_URL=postgres://127.0.0.1/postgres
   npx -y -p @latticexyz/store-indexer@next postgres-decoded-indexer

3. To verify the installation, run psql and then:

   • List the schemas.

     \dn

     Result:

                                     List of schemas
                          Name                         |       Owner
     --------------------------------------------------+-------------------
     0x6e9474e9c83676b9a71133ff96db43e7aa0a4342__      | qbzzt
     0x6e9474e9c83676b9a71133ff96db43e7aa0a4342__store | qbzzt
     0x6e9474e9c83676b9a71133ff96db43e7aa0a4342__world | qbzzt
     mud                                               | qbzzt
     public                                            | pg_database_owner
     (5 rows)

   • Connect to the schema for your world.

     set search_path to "0x6e9474e9c83676b9a71133ff96db43e7aa0a4342__";

   • Get the list of tables.

     \dt

     Result (When using the React template):

                             List of relations
                       Schema                      | Name  | Type  | Owner
     ----------------------------------------------+-------+-------+-------
     0x6e9474e9c83676b9a71133ff96db43e7aa0a4342__  | tasks | table | qbzzt
     (1 row)

   • Read the actual data.

     select * from tasks;

     Result:

                                   key                                  | created_at | completed_at |    description     |                            __key_bytes                             | __last_updated_block_number
     --------------------------------------------------------------------+------------+--------------+--------------------+--------------------------------------------------------------------+-----------------------------
     \x3100000000000000000000000000000000000000000000000000000000000000 | 1702401236 |            0 | Walk the dog       | \x3100000000000000000000000000000000000000000000000000000000000000 |                          17
     \x5e9c11602057fbf149cca23095b1863f7ffa8d0d0bd9434005a344ad612488a7 | 1702401238 |            0 | Take out the trash | \x5e9c11602057fbf149cca23095b1863f7ffa8d0d0bd9434005a344ad612488a7 |                          17
     \x0c9151148be227a42be8d3e3e7e61da28a532f2340b0ad9ca8bc747703ec2417 | 1702401238 |   1702401238 | Do the dishes      | \x0c9151148be227a42be8d3e3e7e61da28a532f2340b0ad9ca8bc747703ec2417 |                          17
     (3 rows)

Docker

The indexer Docker image is available on github (opens in a new tab).

There are several ways to provide the environment variables to docker run:

• On the command line you can specify -e <variable>=<value>. You specify this after the docker run, but before the name of the image.
• You can also write all the environment variables in a file and specify it using --env-file. You specify this after the docker run, but before the name of the image.
• Both Docker Compose (opens in a new tab) and Kubernetes (opens in a new tab) have their own mechanisms for starting docker containers with environment variables.

The easiest way to test the indexer is to run the template as a world in a separate command-line window.

SQLite

The command to start the indexer in SQLite mode is pnpm start:sqlite. To index an anvil instance running to the host you can use this command.

docker run \
  --platform linux/amd64 \
  -e RPC_HTTP_URL=http://host.docker.internal:8545 \
  -p 3001:3001  \
  ghcr.io/latticexyz/store-indexer:latest  \
  pnpm start:sqlite

However, this creates a docker container with a state, the SQLite database file. If we start a new container with the same image and parameters, it is going to have to go back to the start of the blockchain, which depending on how long the blockchain has been in use may be a problem. We can solve this with volumes (opens in a new tab):

1. Create a docker volume for the SQLite database file.

   docker volume create sqlite-db-file

2. Run the indexer container using the volume.

   docker run \
      --platform linux/amd64 \
      -e RPC_HTTP_URL=http://host.docker.internal:8545 \
      -e SQLITE_FILENAME=/dbase/indexer.db \
      -v sqlite-db-file:/dbase \
      -p 3001:3001  \
      ghcr.io/latticexyz/store-indexer:latest  \
      pnpm start:sqlite

3. You can stop the docker container and restart it, or start a separate container using the same database.

4. When you are done, you have to delete the docker containers that used it before you can delete the volume. You can use these commands:

   docker rm `docker ps -a --filter volume=sqlite-db-file -q`
   docker volume rm sqlite-db-file

   Note: You should do this every time you restart the blockchain. Otherwise your index will include data from multiple blockchains, and make no sense.

Schemaless indexing with PostgreSQL via Docker

The command to start the indexer in schemaless PostgreSQL mode is pnpm start:postgres. This command starts both the indexer and query frontends.

1. The docker instance identifies itself to PostgreSQL as root. To give this user permissions on the database, enter psql and run this command.

   CREATE ROLE root SUPERUSER LOGIN;

   Note: This is assuming a database that is isolated from the internet and only used by trusted entities. In a production system you will use at least a password as authentication, and limit the user's authority.

2. Start the docker container. For example, to index an anvil instance running to the host to the database postgres on the host, use.

   docker run \
     --platform linux/amd64 \
     -e RPC_HTTP_URL=http://host.docker.internal:8545 \
     -e DATABASE_URL=postgres://host.docker.internal/postgres \
     -p 3001:3001  \
     ghcr.io/latticexyz/store-indexer:latest  \
     pnpm start:postgres

   If you want to create additional query frontends (for reliability and load balancing), use these commands:

   HOST_PORT=3002
   docker run \
     --platform linux/amd64 \
     -e DATABASE_URL=postgres://host.docker.internal/postgres \
     -p $HOST_PORT:3001  \
     ghcr.io/latticexyz/store-indexer:latest  \
     node dist/bin/postgres-frontend.js

Schemaful indexing with PostgreSQL via Docker

The command to start the indexer in schemaful PostgreSQL mode is pnpm start:postgres-decoded. This command starts both the indexer and the query frontend.

1. The docker instance identifies itself to PostgreSQL as root. To give this user permissions on the database, enter psql and run this command.

   CREATE ROLE root SUPERUSER LOGIN;

   Note: This is assuming a database that is isolated from the internet and only used by trusted entities. In a production system you will use at least a password as authentication, and limit the user's authority.

2. Start the docker container. For example, to index an anvil instance running to the host to the database postgres on the host, use.

   docker run \
     --platform linux/amd64 \
     -e RPC_HTTP_URL=http://host.docker.internal:8545 \
     -e DATABASE_URL=postgres://host.docker.internal/postgres \
     -p 3001:3001  \
     ghcr.io/latticexyz/store-indexer:latest  \
     pnpm start:postgres-decoded

Verification

If you use either SQLite or PostgreSQL with the query frontend (using PostgreSQL only as storage), you can run this command to test the indexer.

curl 'http://localhost:3001/trpc/findAll?batch=1&input=%7B%220%22%3A%7B%22json%22%3A%7B%22chainId%22%3A31337%2C%22address%22%3A%220x6e9474e9c83676b9a71133ff96db43e7aa0a4342%22%7D%7D%7D' | jq

The result should be nicely formatted (and long) JSON output with all the data stored in the World.

{
  "0": {
    "json": {
      "chainId": 31337,
      "address": "0x6e9474e9c83676b9a71133ff96db43e7aa0a4342"
    }
  }
}

Using the indexer

The source code of a MUD client has a call either to syncToRecs (opens in a new tab) or to syncToZustand (opens in a new tab), typically in setupNetwork.ts (opens in a new tab). This call initializes the synchronization between the data source (RPC or indexer) and the client's copy.

To use the indexer, specify an indexerUrl parameter with the URL.

const { components, latestBlock$, storedBlockLogs$, waitForTransaction } = await syncToRecs({
  world,
  config: mudConfig,
  address: networkConfig.worldAddress as Hex,
  publicClient,
  startBlock: BigInt(networkConfig.initialBlockNumber),
  indexerUrl: "http://127.0.0.1:3001",
});

If the client does not need all the information stored in the World, you can filter the synchronization to save on resources.

Usage examples

SQLite to view the tasks from the React template

1. Start the indexer.

   export RPC_HTTP_URL=http://127.0.0.1:8545
   npx -y -p @latticexyz/store-indexer@next sqlite-indexer

2. Get the list of tables. To do that, we read all the data and filter it locally.

   curl 'http://localhost:3001/trpc/findAll?batch=1&input=%7B%220%22%3A%7B%22json%22%3A%7B%22chainId%22%3A31337%2C%22address%22%3A%220x6e9474e9c83676b9a71133ff96db43e7aa0a4342%22%7D%7D%7D' > alldata.json
   cat alldata.json | jq '.[0].result.data.json.tables[]' > tables.json
   cat tables.json | jq '.name + " " + .tableId'

3. Ask the indexer for only the information in a specific table (which requires you to know the tableId for it).

   INDEXER_URL=http://localhost:3001/trpc
   WORLD_ADDRESS=0x6e9474e9c83676b9a71133ff96db43e7aa0a4342
   TABLE_ID=0x746200000000000000000000000000005461736b730000000000000000000000
   CHAIN_ID=31337
   JSON='{"0":{"json":{"chainId": '$CHAIN_ID', "address": "'$WORLD_ADDRESS'", "filters": [{"tableId": "'$TABLE_ID'"}]}}}'
   ENCODED_JSON=`echo "console.log(encodeURI('$JSON'))" | node`
   curl $INDEXER_URL'/findAll?batch=1&input='$ENCODED_JSON > data.json
   cat data.json |  jq '.[0].result.data.json.tables[0].records'

   To see that the only table returned is Tasks, run this command:

   cat data.json | jq '.[0].result.data.json.tables[].name'

Postgres to read data from SkyStrife season 0

1. If necessary, start Docker and PostgreSQL.

2. Start the Postgres Docker container.

   docker run \
      --platform linux/amd64 \
      -e RPC_HTTP_URL=https://rpc.holesky.redstone.xyz \
      -e RPC_WS_URL=wss://rpc.holesky.redstone.xyz/ws \
      -e DATABASE_URL=postgres://host.docker.internal/postgres \
      -e START_BLOCK=895629 \
      -p 3001:3001  \
      ghcr.io/latticexyz/store-indexer:latest  \
      pnpm start:postgres

3. It will take a while until the indexer synchronizes all the way to the present. However, we can already read information and it will give us the latest it has.

4. Read the data from the indexer.

   INDEXER_URL=http://localhost:3001/trpc
   WORLD_ADDRESS=0x7203e7adfdf38519e1ff4f8da7dcdc969371f377
   CHAIN_ID=17001
   JSON='{"0":{"json":{"chainId":'$CHAIN_ID', "address":"'$WORLD_ADDRESS'"}}}'
   ENCODED_JSON=`echo "console.log(encodeURI('$JSON'))" | node`
   curl $INDEXER_URL'/findAll?batch=1&input='$ENCODED_JSON > data.json

5. Obtain the list of tables.

   TABLES=`cat data.json | jq '.[0].result.data.json.tables'`
   echo $TABLES | jq '.[].name'

6. Get the combatant entities.

   echo $TABLES | jq '.[] | select (.name=="Combat")'