Validate Blockchain Data Integrity Across Indexers

This workflow validates data consistency by automatically comparing entity changes between two blockchain indexers for a specific subgraph and block. It fetches data via HTTP requests, uses a Python script to pinpoint any discrepancies, and logs the detailed results to a Supabase database for auditing. This process is crucial for developers and teams maintaining decentralized applications to ensure data integrity and quickly identify potential indexer divergence.

Workflow Overview

What is this?: This is an automated validation tool that monitors and compares data from two different blockchain indexers. It executes a side-by-side comparison of entity changes for a specific subgraph deployment at a given block number, providing a definitive report on their synchronization status.
What problem does it solve?: Are you constantly worried about silent data divergence between your primary and backup indexers? Manually checking for data consistency is time-consuming, prone to human error, and simply not scalable. This workflow eliminates that uncertainty by providing an automated, reliable system to detect and log any discrepancies the moment they occur.
What will you get?: You will gain a robust, automated system for maintaining data integrity across your decentralized infrastructure. This workflow empowers you to proactively detect data inconsistencies, save significant manual auditing time, and maintain a verifiable log of all comparisons for compliance and debugging. Ultimately, it provides peace of mind that your application's data sources are perfectly aligned.

Apps Included

How to Use

Prerequisites

An active Dify instance (Cloud or Self-hosted).

The deployment ID of the subgraph you want to monitor.

Status URLs for the two indexers you need to compare.

Supabase project credentials (URL and API Key) for logging the results.

Setup Steps

Import the Workflow

Begin by importing this workflow into your Dify account. You will be prompted to configure the required environment variables during the setup process.

Configure Environment Variables

Navigate to the environment variables section and securely add your Supabase credentials. This allows the workflow to connect to your database and log the comparison results.

Run the Workflow

Execute the workflow by providing the required inputs: the subgraph deployment ID, the status URL for your first indexer, the status URL for your second indexer, and the specific block number you wish to check.

Review the Output

Check the workflow's output. It will return a clear status indicating if the data is identical, along with any detected differences. If differences are extensive, an AI-generated summary will be provided.

Verify Database Logs

Log in to your Supabase project and check the 'indexer_block_entity_changes' table. You will find a new row containing a detailed record of the comparison, including timestamps, inputs, and results, which is automatically created by the workflow.

Pro Tips

Integrate this workflow with a scheduler (like a CRON job via n8n or another tool) to run periodic checks on critical subgraphs, turning it into a fully automated monitoring system.

Consider adding a notification step (e.g., sending a Slack or Discord message) within the Dify workflow if the 'identical' output is 'false', to get real-time alerts on data divergence.

Back

Information

Published date8/15/2025
Last updated8/15/2025

Platform

Dify