Substreams Triggers

Use Custom Triggers and enable the full use GraphQL.

Обзор

Custom Triggers allow you to send data directly into your subgraph mappings file and entities, which are similar to tables and fields. This enables you to fully use the GraphQL layer.

By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data in your subgraph’s handler. This ensures efficient and streamlined data management within the subgraph framework.

Defining handleTransactions

The following code demonstrates how to define a handleTransactions function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a Transactions object. For each transaction, a new subgraph entity is created.

1export function handleTransactions(bytes: Uint8Array): void {2  let transactions = assembly.eth.transaction.v1.Transactions.decode(bytes.buffer).transactions // 1.3  if (transactions.length == 0) {4    log.info('No transactions found', [])5    return6  }78  for (let i = 0; i < transactions.length; i++) {9    // 2.10    let transaction = transactions[i]1112    let entity = new Transaction(transaction.hash) // 3.13    entity.from = transaction.from14    entity.to = transaction.to15    entity.save()16  }17}

Here’s what you’re seeing in the mappings.ts file:

1. The bytes containing Substreams data are decoded into the generated Transactions object, this object is used like any other AssemblyScript object
2. Looping over the transactions
3. Create a new subgraph entity for every transaction

To go through a detailed example of a trigger-based subgraph, check out the tutorial.

Дополнительные ресурсы

To scaffold your first project in the Development Container, check out one of the How-To Guide.