Indexing Ink with Goldsky

​

Overview

​

Scope

​

Getting started

​

Subgraphs

• Via CLI from a local subgraph configuration file. If you are familiar with developing subgraphs already, you'll be familiar with this approach; after defining a subgraph locally (with a subgraph.yaml file, a schema.graphql file, and the necessary mappings to translate raw event data into the entities defined in the schema), you can deploy subgraphs to Goldsky (once the Goldsky CLI is installed) using goldsky subgraph deploy <name>/<version> --path . For more, read the step-by-step guide.
• Via instant subgraphs, where you can pass through a contract address and the ABI for that contract. This is a quick-start option that automatically generates the underlying subgraph configuration files on your behalf, making it easy to extract blockchain event data and serve it as an API endpoint without complex setup. Use the --from-abi flag in the command above instead of --path. For more, read the no-code subgraphs guide.

​

Mirror

• Using Goldsky Flow in the dashboard:
  • Drop a Data Source card. Select Ink as the chain. Then Enriched Transactions as the onchain dataset to use.
  • Add a Sink card and select your pre-configured sink.
  • Deploy pipeline.
• Using the interactive CLI:
  • Enter command goldsky pipeline create <pipeline-name>.
  • This will kick off a guided flow with the first step to choose the dataset type. Choose Direct Indexing.
  • Next, select Ink Sepolia as chain with the enter key, then Enriched Transactions as the dataset by pressing space on the selected dataset which you can select using the up and down arrow keys. We will process historical data so select Process all historical data by pressing the enter key. This is the same as the yaml config setting of start_at: earliest. If you prefer to only ingest data starting when your pipeline is deployed, select Process data from the time this pipeline is created instead, this is equivalent to the yaml config setting start_at: latest.
  • When asked to choose another source, choose No by pressing enter.
  • Add your pre-configured sink. In this example case, we chose PostgreSQL and as a next step we selected the database schema.
  • Pipeline will be deployed automatically.
• Using a pipeline configuration file:
  • This makes it easier to set up complex pipelines involving multiple sources, multiple sinks, and more complex, SQL-based transformations. For the full reference documentation on, click here.
  • As in the previous steps, we’ll be deploying a pipeline to stream Ink Sepolia transactions. Unlike the other methods, we have added a transformation to only select specific data attributes from the whole dataset. This is the configuration file:

name: ink-sepolia-transactions
resource_size: s
apiVersion: 3
sources:
  ink_sepolia_receipt_transactions:
    dataset_name: ink_sepolia.receipt_transactions
    version: 1.0.0
    type: dataset
    start_at: earliest
transforms:
  subset_transform:
    primary_key: id
    sql: |
      SELECT
        id,
        from_address,
        to_address,
        input,
        `value`,
        block_hash,
        block_number
        FROM ink_sepolia_receipt_transactions
sinks:
  postgres_ink_sepolia_transactions:
    type: postgres
    table: ink_sepolia_transactions
    schema: public
    secret_name: <YOUR_SECRET_NAME>
    description: 'Postgres sink for: ink_sepolia_transactions'
    from: subset_transform

• Add your corresponding secret name and run goldsky pipeline apply ink-sepolia-transactions.yaml --status ACTIVE to deploy the pipeline.

​

Getting support