### Token Transfers - Native Source: https://docs.goldsky.com/mirror/create-a-pipeline Guide for handling native token transfers. Details how to track and manage native currency movements. ```APIDOC Native Token Transfers: Purpose: Track native token transfers. Method: Data streaming and database synchronization. Output: Native transfer records. Related: ERC-20 Transfers, ERC-721 Transfers, ERC-1155 Transfers. ``` -------------------------------- ### Stablecoin Transfers Overview Source: https://docs.goldsky.com/mirror/create-a-pipeline Create a stream containing all transfers for stablecoins. This overview guide details how to monitor stablecoin activity. ```APIDOC Stablecoin Transfer Stream: Purpose: Create a stream of all stablecoin transfers. Method: Data streaming and database synchronization. Input: List of stablecoin contract addresses. Output: Stream of stablecoin transfer events. Related: Stablecoin Contract Addresses, ERC-20 Transfers. ``` -------------------------------- ### Install Goldsky CLI Source: https://docs.goldsky.com/mirror/create-a-pipeline Installs the Goldsky CLI globally using npm. Ensure Node.js and npm are installed on your system. ```shellscript npm install -g @goldskycom/cli ``` -------------------------------- ### Install Goldsky CLI Source: https://docs.goldsky.com/mirror/create-a-pipeline Instructions for installing the Goldsky CLI on macOS/Linux and Windows. Windows users require Node.js and npm to be installed first. ```Shell ## For macOS/Linux: curl https://goldsky.com | sh ## For Windows: npm install -g @goldskycom/cli ``` -------------------------------- ### Install Goldsky CLI (Windows) Source: https://docs.goldsky.com/mirror/create-a-pipeline Installs the Goldsky CLI on Windows systems. The provided snippet is incomplete but indicates the use of PowerShell for installation. ```shellscript Invoke-WebRequest -Uri https://goldsky.com -OutFile goldsky_install.ps1; powershell -ExecutionPolicy Bypass -File goldsky_install.ps1 ``` -------------------------------- ### Sync Dataset to Postgres Source: https://docs.goldsky.com/mirror/create-a-pipeline Guide on synchronizing datasets to a PostgreSQL database. Specific details on the process are available. ```APIDOC Dataset to PostgreSQL Synchronization: Purpose: Sync datasets to a PostgreSQL database. Method: Mirror platform data synchronization. Output: Dataset available in PostgreSQL. Related: Sync Subgraph to Postgres. ``` -------------------------------- ### Download and Execute Goldsky Script Source: https://docs.goldsky.com/mirror/create-a-pipeline Downloads a script from Goldsky's domain and executes it using the shell. This is a common method for initial setup or bootstrapping. ```shellscript curl https://goldsky.com | sh ``` -------------------------------- ### Instant Subgraph Configuration Source: https://docs.goldsky.com/mirror/create-a-pipeline Configuration details for instant subgraphs. This guide covers setting up pre-built subgraphs for quick data synchronization. ```APIDOC Instant Subgraph Configuration: Description: Configuration for deploying pre-built 'instant' subgraphs. Purpose: Rapid deployment of common data synchronization tasks. Configuration Options: - subgraph_id: Identifier for the instant subgraph. - network: Blockchain network (e.g., 'ethereum', 'polygon'). - start_block: Optional block number to start syncing from. - end_block: Optional block number to stop syncing at. Example: instant_subgraph: subgraph_id: "erc20-transfers" network: "ethereum" start_block: 18000000 Related: CLI Reference, Pipeline Configuration. ``` -------------------------------- ### Install Goldsky CLI (macOS/Linux) Source: https://docs.goldsky.com/mirror/create-a-pipeline Installs the Goldsky CLI on macOS and Linux systems. This command downloads and executes the installation script directly from the provided URL. ```shellscript curl https://goldsky.com | sh ``` -------------------------------- ### Start Goldsky CLI Source: https://docs.goldsky.com/mirror/create-a-pipeline Executes the Goldsky CLI to begin interacting with its features after successful login. ```shellscript goldsky ``` -------------------------------- ### Install Goldsky CLI Source: https://docs.goldsky.com/mirror/create-a-pipeline Installs the Goldsky Command Line Interface globally using npm. This tool is essential for managing Goldsky projects and pipelines. ```shellscript npm install -g @goldskycom/cli ``` -------------------------------- ### Install and Login Goldsky CLI Source: https://docs.goldsky.com/mirror/create-a-pipeline Provides instructions for installing the Goldsky Command Line Interface (CLI) and logging into the service. This is the first step for automating pipeline deployments and managing Goldsky resources via the command line. ```bash # Install the Goldsky CLI: # For macOS/Linux: # curl -fsSL https://goldsky.com/install.sh | bash # After installation, you would typically log in: # goldsky login # Follow the prompts to authenticate your account. ``` -------------------------------- ### Install Dependencies Source: https://github.com/goldsky-io/documentation-examples/tree/main/mirror-pipelines/goldsky-enriched-erc20-pipeline Installs the necessary project dependencies using npm. This is a required step before starting the server. ```bash npm install ``` -------------------------------- ### Apply and Start Goldsky Pipeline Source: https://docs.goldsky.com/mirror/create-a-pipeline Apply a pipeline configuration file to create a new pipeline. Once created, start the pipeline to begin processing data. ```shell goldsky pipeline apply ``` ```shell goldsky pipeline start ``` -------------------------------- ### Create a Pipeline Source: https://docs.goldsky.com/mirror/create-a-pipeline Guides users through the process of creating a new pipeline within the Goldsky platform. This involves setting up the pipeline's basic configuration and defining its initial parameters. ```APIDOC POST /pipelines Description: Creates a new data pipeline. Request Body: content-type: application/json schema: | { "type": "object", "properties": { "name": { "type": "string", "description": "The name of the pipeline." }, "description": { "type": "string", "description": "A brief description of the pipeline." }, "source": { "type": "string", "description": "The data source for the pipeline (e.g., 'ethereum', 'polygon')." }, "sink": { "type": "string", "description": "The data destination for the pipeline (e.g., 'postgres', 's3')." }, "configuration": { "type": "object", "description": "Pipeline-specific configuration parameters." } }, "required": [ "name", "source", "sink" ] } Responses: 201 Created: description: Pipeline created successfully. content: application/json: schema: | { "type": "object", "properties": { "id": { "type": "string", "description": "Unique identifier for the created pipeline." }, "name": { "type": "string" }, "status": { "type": "string", "enum": ["pending", "running", "stopped", "failed"] } } } 400 Bad Request: description: Invalid input provided for pipeline creation. 409 Conflict: description: A pipeline with the same name already exists. Example: curl -X POST \ http://api.goldsky.com/v1/pipelines \ -H 'Content-Type: application/json' \ -d '{ "name": "eth-mainnet-blocks", "description": "Pipeline for capturing Ethereum mainnet blocks", "source": "ethereum", "sink": "postgres", "configuration": { "network": "mainnet", "block_interval": "15s" } }' ``` -------------------------------- ### Create Pipeline via CLI Source: https://docs.goldsky.com/mirror/create-a-pipeline Guides users through creating pipelines using the Goldsky CLI. Run 'goldsky pipeline create ' and follow prompts to select sources, transforms, and sinks. ```bash goldsky pipeline create ``` -------------------------------- ### SQL Data Source Query Source: https://docs.goldsky.com/mirror/create-a-pipeline Example SQL query to select data from a source. This snippet defines the initial data selection for the pipeline. ```SQL SELECT id, block_number, transaction_hash, data FROM source_1 ``` -------------------------------- ### Create Pipeline via Guided CLI Source: https://docs.goldsky.com/mirror/create-a-pipeline Initiates an interactive CLI process to create a new pipeline. The process guides users through selecting data sources, defining necessary transformations based on the sources, and configuring the final data sinks. ```shell goldsky pipeline create ``` -------------------------------- ### Goldsky Flow UI Actions Source: https://docs.goldsky.com/mirror/create-a-pipeline Describes key interactive elements within the Goldsky Flow UI for pipeline development. These actions guide the user through the pipeline configuration process. ```UI Run Save + Preview Output Deploy ``` -------------------------------- ### Start Server Source: https://github.com/goldsky-io/documentation-examples/tree/main/mirror-pipelines/goldsky-enriched-erc20-pipeline Starts the local development server for the pipeline. This command is used after dependencies have been installed. ```bash npm start ``` -------------------------------- ### Examples Source: https://docs.goldsky.com/reference/config-file/instant-subgraph Provides practical examples of subgraph configurations, including multi-chain deployments and specific enrichment scenarios like adding balances on transfer. These examples serve as starting points for custom subgraph implementations. ```APIDOC Examples: Multi-chain: - Configuration for deploying a subgraph across multiple blockchain networks. - Key aspects: Network-specific endpoints, chain ID handling. Nouns enrichment with balances on transfer: - Demonstrates enriching Nouns DAO data with token balances during transfer events. - Involves: Defining data sources for Nouns events, configuring an external API call to fetch token balances, mapping balance data to Nouns entities. ``` -------------------------------- ### Mirror Introduction and Getting Started Source: https://docs.goldsky.com/mirror/sources/direct-indexing Introduction to Goldsky Mirror for streaming on-chain data and step-by-step instructions for creating a Mirror pipeline. ```APIDOC Stream Onchain Data with Mirror: Description: Introduction to Goldsky Mirror for streaming on-chain data. URL: /mirror/introduction Getting Started with Mirror: Description: Step-by-step instructions on how to create a Goldsky Mirror pipeline. URL: /mirror/create-a-pipeline ``` -------------------------------- ### Render Data Pipeline UI Elements Source: https://docs.goldsky.com/mirror/create-a-pipeline Demonstrates rendering various UI components for a data pipeline setup using JSX. It includes images, descriptive paragraphs, ordered and unordered lists, and code elements to guide the user through the process. ```jsx sx(ZoomImage, {\n children: _jsx(\"img\", {\n className: \"mint-block mint-mx-auto\",\n width: \"300\",\n src: \"https://mintlify.s3.us-west-1.amazonaws.com/goldsky-38/images/mirror/flow/1-side-menu.png\"\n })\n }), \"\\n\", _jsx(_components.p, {\n children: \"Let’s now look at how we can deploy a simple pipeline; in the following section we are going to see the steps needed to stream Ethereum raw logs into a ClickHouse database. Since the steps are the same for any pipeline, feel free to adapt the components to fit your specific use case.\"\n }), \"\\n\", _jsxs(_components.ol, {\n children: [\"\\n\", _jsx(_components.li, {\n children: _jsx(_components.strong, {\n children: \"Select the Data Source\"\n })\n }), \"\\n\"],\n start: \"1\"\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"Start by dragging and dropping a \", _jsx(_components.code, {\n children: \"Data Source\"\n }), \" card onto the canvas. Once you do that, you’ll to need select the chain you are interested in. We currently support \", _jsx(_components.a, {\n href: \"/chains/supported-networks\",\n children: \"100+ chains\"\n }), \". For this example we are going to choose \", _jsx(_components.code, {\n children: \"Ethereum\"\n }), \".\"],\n \n}), \"\\n\", _jsx(ZoomImage, {\n children: _jsx(\"img\", {\n className: \"mint-block mint-mx-auto\",\n width: \"300\",\n src: \"https://mintlify.s3.us-west-1.amazonaws.com/goldsky-38/images/mirror/flow/2-chain-list.png\"\n })\n }), \"\\n\", _jsx(_components.p, {\n children: \"Next, we need to define the type of data source we want to use:\"\n }), \"\\n\", _jsxs(_components.ul, {\n children: [\"\\n\", _jsxs(_components.li, {\n children: [\"Onchain datasets: these are \", _jsx(_components.a, {\n href: \"/mirror/sources/direct-indexing\",\n children: \"Direct Indexing datasets\"\n }), \" representing both raw data (e.g. Raw Blocks) as well as curated datasets (e.g. ERC-20 Transfers)\"]\n }), \"\\n\", _jsxs(_components.li, {\n children: [ _jsx(_components.a, {\n href: \"/mirror/sources/subgraphs\",\n children: \"Subgraphs\"\n }), \": this can be community subgraphs or existing subgraphs in your project for the choosen network\"]\n }), \"\\n\"],\n \n}), \"\\n\", _jsxs(_components.p, {\n children: [\"For this example, we are going to choose \", _jsx(_components.code, {\n children: \"Raw Logs\"\n }), \".\"],\n \n}), \"\\n\", _jsx(ZoomImage, {\n children: _jsx(\"img\", {\n className: \"mint-block mint-mx-auto\",\n width: \"300\",\n src: \"https://mintlify.s3.us-west-1.amazonaws.com/goldsky-38/images/mirror/flow/3-raw-logs.png\"\n })\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"After selecting the data source, you have some optional configuration fields to use, in the case of \", _jsx(_components.code, {\n children: \"Onchain Datasets\"\n }), \" you can configure:\"\n],\n \n}), \"\\n\", _jsxs(_components.ul, {\n children: [\"\\n\", _jsxs(_components.li, {\n children: [ _jsx(_components.code, {\n children: \"Start indexing at\"\n }), \": here you can define whether you want to do a full backfill (\", _jsx(_components.code, {\n children: \"Beginning\"\n }), \" or read from edge (\", _jsx(_components.code, {\n children: \"Current\"\n }), \" )\"],\n \n}), \"\\n\", _jsxs(_components.li, {\n children: [ _jsx(_components.code, {\n children: \"Filter by contract address\"\n }), \": optional contract address (in lowercase) to filter from\"],\n \n}), \"\\n\", _jsxs(_components.li, {\n children: [ _jsx(_components.code, {\n children: \"Filter by topics\"\n }), \": optional list of topics (in lowercase) to filter from, separated by commas.\"],\n \n}), \"\\n\", _jsxs(_components.li, {\n children: [ _jsx(_components.code, {\n children: \"View Schema\"\n }), \": view the data schema to get a better idea of the shape of the data as well as see some sample records.\"],\n \n}), \"\\n\"],\n \n}), \"\\n\", _jsx(ZoomImage, {\n children: _jsx(\"img\", {\n className: \"mint-block mint-mx-auto\",\n width: \"300\",\n src: \"https://mintlify.s3.us-west-1.amazonaws.com/goldsky-38/images/mirror/flow/4-raw-logs-selected.png\"\n })\n }), \"\\n\", _jsxs(_components.ol, {\n start: \"2\",\n children: [\"\\n\", _jsx(_components.li, {\n children: _jsx(_components.strong, {\n children: \"(Optional) Select a Transform\"\n })\n }), \"\\n\"],\n \n}), \"\\n\", _jsxs(_components.p, {\n children: [\"Optionally select a Transform for your data by clicking on the \", _jsx(_components.code, {\n children: \"+\"\n }), \" button at the top right edge of the \", _jsx(_components.code, {\n children: \"Data Source\"\n }), \" card and you’ll have the option to add a Transform or a Sink.\"],\n \n})] ``` -------------------------------- ### Goldsky Flow Pipeline Configuration Steps Source: https://docs.goldsky.com/mirror/create-a-pipeline Outlines the sequential steps for configuring a Goldsky Flow pipeline, from selecting a sink to confirming and deploying the pipeline. ```UI 1. Select the Sink 2. Confirm and deploy ``` -------------------------------- ### Goldsky Configuration Source: https://docs.goldsky.com/mirror/create-a-pipeline Configuration details for the Goldsky platform, including theme, colors, logos, and navigation links. ```json { "theme": "maple", "name": "Goldsky", "colors": { "primary": "#FFAD33", "light": "#FFBF60", "dark": "#FFAD33" }, "logo": { "light": "https://mintlify.s3.us-west-1.amazonaws.com/goldsky-38/images/logo/light.svg", "dark": "https://mintlify.s3.us-west-1.amazonaws.com/goldsky-38/images/logo/dark.svg" }, "favicon": "/images/favicon.png", "appearance": { "default": "dark", "strict": true }, "background": { "image": "https://mintlify.s3.us-west-1.amazonaws.com/goldsky-38/images/bg.png", "color": { "light": "#090B0C", "dark": "#090B0C" } }, "navbar": { "links": [ { "label": "Homepage", "href": "https://goldsky.com" }, { "label": "Support", "href": "https://docs.goldsky.com/getting-support" }, { "label": "GitHub", "href": "https://github.com/goldsky-io/documentation-examples" } ], "primary": { "type": "button", "label": "Dashboard", "href": "https://app.goldsky.com/" } }, "navigation": { "global": { "anchors": [ { "anchor": "Changelog ↗", "icon": "list", "href": "https://goldsky.com/changelog" }, { "anchor": "Blog ↗", "icon": "newspaper", "href": "https://goldsky.com/blog" } ] }, "tabs": [ { "tab": "Documentation", "groups": [ { "group": "Overview", "pages": [ "introduction", "benefits", "getting-support" ] }, { "group": "More", "pages": [ "subgraph-vs-mirror", "pricing/summary", "teams-and-projects", "rbac", "faq" ] } ] }, { "tab": "Subgraphs", "groups": [ { "group": "Subgraphs", "pages": [ "subgraphs/introduction", "subgraphs/deploying-subgraphs", "subgraphs/migrate-from-the-graph", "subgraphs/webhooks", "subgraphs/tags", "subgraphs/serverless-vs-dedicated", "subgraphs/graphql-endpoints" ] }, { "group": "Guides", "pages": [ "subgraphs/guides/subgraph-deploy-wizard", "subgraphs/guides/create-a-no-code-subgraph", "subgraphs/guides/create-a-multi-chain-subgraph", "subgraphs/guides/send-subgraph-driven-webhooks", "subgraphs/guides/declared-eth-calls" ] }, { "group": "More Info", "pages": [ "subgraphs/subgraphs-github" ] } ] }, { "tab": "Mirror", "groups": [ { "group": "Mirror" // Content for Mirror group is truncated in the provided text. } ] } ] } } ``` -------------------------------- ### Pipeline Configuration Schema Source: https://docs.goldsky.com/mirror/create-a-pipeline Schema details for pipeline configurations. This documentation explains the structure and parameters required for setting up data pipelines. ```APIDOC Pipeline Configuration Schema: Description: Defines the structure for Goldsky pipeline configurations. Key Sections: - sources: Specifies data sources (e.g., subgraphs, event streams). - transformations: Defines data processing steps. - sinks: Configures data destinations (e.g., databases, message queues). Parameters: - name: Name of the pipeline. - version: Schema version. - schedule: Cron expression for pipeline execution. Example: pipeline: name: "eth-transfers" sources: - type: "subgraph" url: "https://api.goldsky.io/subgraph/name/... sinks: - type: "postgres" connection_string: "postgres://..." Related: CLI Reference, Instant Subgraph Configuration. ``` -------------------------------- ### Sync Subgraph to Postgres Source: https://docs.goldsky.com/mirror/create-a-pipeline Guide on synchronizing subgraph data to a PostgreSQL database. Details the process for subgraph data integration. ```APIDOC Subgraph to PostgreSQL Synchronization: Purpose: Sync subgraph data to a PostgreSQL database. Method: Mirror platform data synchronization. Output: Subgraph data available in PostgreSQL. Related: Sync Dataset to Postgres. ``` -------------------------------- ### Merging Cross-Chain Subgraphs Source: https://docs.goldsky.com/mirror/create-a-pipeline Guide on merging cross-chain subgraph data. Provides information on consolidating data from multiple blockchain networks. ```APIDOC Cross-Chain Subgraph Merging: Purpose: Merge data from cross-chain subgraphs. Method: Goldsky's subgraph management tools. Output: Consolidated cross-chain data. Related: Subgraph Synchronization. ``` -------------------------------- ### Goldsky Flow Pipeline Naming and Resource Sizing Source: https://docs.goldsky.com/mirror/create-a-pipeline Details the final configuration steps for a deployed pipeline, including naming the pipeline and selecting appropriate resource sizes. ```UI Pipeline Name: ethereum-raw-logs Resource Size: Small (default) ``` -------------------------------- ### Stream DEX Trades Source: https://docs.goldsky.com/mirror/create-a-pipeline Stream Decentralized Exchange trade events to your database. This guide explains how to capture and process DEX trade data. ```APIDOC DEX Trade Event Streaming: Purpose: Stream Decentralized Exchange trade events. Method: Mirror platform data streaming. Input: DEX contract events. Output: Stream of DEX trade data. Related: Contract Event Decoding. ``` -------------------------------- ### Decode Traces with Mirror Source: https://docs.goldsky.com/mirror/create-a-pipeline Synchronize blockchain traces to a database using the contract ABI with Mirror. This guide details the process for trace data. ```APIDOC Mirror Trace Synchronization: Purpose: Sync traces to a database using the contract ABI. Method: Utilizes Mirror platform capabilities. Input: Contract ABI, Trace data. Output: Synchronized trace data in a database. Related: Decoding Contract Events, DEX Trades. ``` -------------------------------- ### Goldsky CLI Commands for Pipeline Management Source: https://docs.goldsky.com/mirror/create-a-pipeline Provides essential Goldsky CLI commands for managing pipelines. This includes applying a pipeline configuration from a file, starting a created pipeline, and monitoring its status and output in real-time. ```shell # Apply a pipeline configuration from a local file goldsky pipeline apply # Start a created pipeline goldsky pipeline start # Monitor an existing pipeline goldsky pipeline monitor ``` -------------------------------- ### Goldsky CLI Reference Source: https://docs.goldsky.com/mirror/create-a-pipeline Goldsky's command line interface reference. This section details available commands and their usage for interacting with Goldsky services. ```APIDOC Goldsky CLI Reference: Description: Comprehensive guide to Goldsky's command-line interface. Commands: - goldsky init: Initializes a new project. - goldsky sync : Syncs a specified subgraph. - goldsky status: Checks the status of running services. Usage: For managing and interacting with Goldsky deployments. Related: Pipeline Configuration, Instant Subgraph Configuration. ``` -------------------------------- ### Token Transfers - ERC-1155 Source: https://docs.goldsky.com/mirror/create-a-pipeline Create a table containing ERC-1155 token transfers for multiple or all token contracts. This guide focuses on ERC-1155 specific transfer data. ```APIDOC ERC-1155 Token Transfers: Purpose: Create a table of ERC-1155 transfers for specified contracts. Method: Data streaming and database synchronization. Input: List of ERC-1155 token contract addresses. Output: Table of ERC-1155 transfer events. Related: Native Transfers, ERC-20 Transfers, ERC-721 Transfers. ``` -------------------------------- ### Token Transfers - ERC-721 Source: https://docs.goldsky.com/mirror/create-a-pipeline Create a table containing ERC-721 token transfers for multiple or all token contracts. This guide focuses on ERC-721 specific transfer data. ```APIDOC ERC-721 Token Transfers: Purpose: Create a table of ERC-721 transfers for specified contracts. Method: Data streaming and database synchronization. Input: List of ERC-721 token contract addresses. Output: Table of ERC-721 transfer events. Related: Native Transfers, ERC-20 Transfers, ERC-1155 Transfers. ``` -------------------------------- ### Token Transfers - ERC-20 Source: https://docs.goldsky.com/mirror/create-a-pipeline Create a table containing ERC-20 token transfers for multiple or all token contracts. This guide focuses on ERC-20 specific transfer data. ```APIDOC ERC-20 Token Transfers: Purpose: Create a table of ERC-20 transfers for specified contracts. Method: Data streaming and database synchronization. Input: List of ERC-20 token contract addresses. Output: Table of ERC-20 transfer events. Related: Native Transfers, ERC-721 Transfers, ERC-1155 Transfers, Stablecoin Transfers. ``` -------------------------------- ### General Resource Size Guidelines Source: https://docs.goldsky.com/mirror/about-pipeline Provides general guidance on choosing resource sizes, suggesting starting small and scaling up. It details the capabilities of a 'small' resource size for backfilling and write speeds, and when larger sizes are typically needed. ```markdown Here’s some general information that you can use as reference: - A `small` resource size is usually enough in most use case: it can handle full backfill of small chain datasets and write to speeds of up to 300K records per second. For pipelines using subgraphs as source it can reliably handle up to 8 subgraphs. - Larger resource sizes are usually needed when backfilling large chains or when doing large JOINS (example: JOIN between accounts and transactions datasets in Solana) - It’s recommended to always follow a defensive approach: start small and scale up if needed. ``` -------------------------------- ### Goldsky Mirror Pipeline Setup Source: https://docs.goldsky.com/chains/supported-networks Provides step-by-step instructions for creating a Goldsky Mirror pipeline. This section guides users through the initial setup process. ```APIDOC APIDOC: Section: Getting Started Title: Creating a Goldsky Mirror Pipeline Description: Step by step instructions on how to create a Goldsky Mirror pipeline. Content: - Follow the guided setup process to define your data pipeline. - Configure data sources, transformations, and sinks. - Example: Navigate to the 'Create Pipeline' section in the Goldsky dashboard. ``` -------------------------------- ### Decode Contract Events with Mirror Source: https://docs.goldsky.com/mirror/create-a-pipeline Synchronize contract events to a database using the contract ABI with Mirror. This guide explains the process of decoding and syncing these events. ```APIDOC Mirror Contract Event Synchronization: Purpose: Sync contract events to a database using the contract ABI. Method: Utilizes Mirror platform capabilities. Input: Contract ABI, Event data. Output: Synchronized event data in a database. Related: Decoding Traces, Token Transfers. ``` -------------------------------- ### Install ClickHouse Local (Shell) Source: https://clickhouse.com/ This command downloads and installs ClickHouse using a shell script. It's a quick way to get started with ClickHouse on Unix-like systems. ```shell curl https://clickhouse.com/ | sh ``` -------------------------------- ### SQL Transform Query Example Source: https://docs.goldsky.com/mirror/create-a-pipeline Provides an example SQL query to select specific columns from a source. The SQL editor allows users to define transformation logic and preview results. ```sql SELECT id, block_number, transaction_hash, data FROM source_1 ``` -------------------------------- ### SQL Transform Example Source: https://docs.goldsky.com/mirror/create-a-pipeline Example SQL query to select specific fields from the data source within a Goldsky Flow transform. This query specifies the columns to retrieve from the source data. ```sql SELECT id, block_number, transaction_hash, data FROM source_1 ```