Skip to main content

​
Overview

Goldsky provides high-performance data infrastructure for NEAR, making it easy to extract, transform, and load on-chain data to power both application and analytics use cases using Turbo Pipelines. NEAR is a sharded, proof-of-stake blockchain designed for usability and scalability. With its unique sharding mechanism called Nightshade, NEAR enables high throughput and low transaction costs while maintaining decentralization.

​
Benefits of building with NEAR datasets

Building with NEAR datasets on Goldsky provides several key advantages:
  • Real-time data access - Stream NEAR data to your infrastructure with sub-second latency
  • Complete historical data - Access the full history of NEAR transactions, receipts, and execution outcomes
  • Flexible transformations - Use SQL to filter, aggregate, and transform data before it reaches your database
  • Sharding-aware - Work with NEAR’s unique sharded architecture through structured datasets
  • Cross-contract tracking - Follow execution flows across multiple contracts using receipts and execution outcomes
  • Scalable infrastructure - Handle high-throughput NEAR data without managing your own nodes

​
Getting started

To use Goldsky, you’ll need to create an account, install the CLI, and log in.
  1. Install the Goldsky CLI: For macOS/Linux: 
    curl https://goldsky.com | sh
    For Windows: 
    npm install -g @goldskycom/cli
    Windows users need to have Node.js and npm installed first. Download from nodejs.org if not already installed.
  2. Go to your Project Settings page and create an API key.
  3. Back in your Goldsky CLI, log into your Project by running the command goldsky login and paste your API key.
  4. Now that you are logged in, run goldsky to get started: 
    goldsky

​
Turbo Pipelines

Turbo pipelines allow users to replicate data into their own infrastructure (any of the supported sinks) in real time. For a complete overview of how to deploy Turbo pipelines, including a video walkthrough, check the Quickstart guide.
Watch this video walkthrough for a complete guide to using pipelines with NEAR.

​
Working with NEAR datasets

Goldsky provides real-time streaming of NEAR datasets, including all historical data, for both mainnet and testnet. The following datasets are currently available:
DatasetDescription
ReceiptsReceipts created during execution of transactions.
TransactionsTransactions pulled from chunks as found on the NEAR blockchain.
Execution OutcomesExecution outcomes generated from both transaction and receipt executions.
These datasets can be used as sources in your Turbo pipelines to stream NEAR data to any of the supported sinks.

​
Deploying NEAR pipelines with Turbo

Turbo pipelines are defined using YAML configuration files and deployed via the Goldsky CLI. Here’s the workflow:
  1. Create a pipeline configuration file - Define your sources, transforms, and sinks in a YAML file
  2. Validate your configuration - Run goldsky turbo validate near-pipeline.yaml to check for errors
  3. Deploy the pipeline - Run goldsky turbo apply -f near-pipeline.yaml to deploy
  4. Monitor your pipeline - Use goldsky turbo logs near-pipeline.yaml to view logs and goldsky turbo inspect near-pipeline.yaml to see live data
For a complete walkthrough, see the Turbo Pipelines Quickstart.
Remember to first create a Secret in order for Turbo Pipelines to be able to write the data into the database of your choice.

​
Example Turbo pipeline configuration

One powerful use case is creating a dedicated “failure feed” for debugging. By pulling directly from the near.execution_outcomes dataset and filtering for failed transactions, you can turn a massive stream of data into actionable insights. With a simple SQL transform, you can filter execution outcomes to only capture failures: 
SELECT
  id,
  executor_id,
  status,
  gas_burnt,
  tokens_burnt,
  transaction_hash,
  signer_id,
  trigger_block_height,
  trigger_block_timestamp
FROM execution_outcomes
WHERE status <> 'SUCCESS'
The power of this approach:
  • The Source - Pull directly from the near.execution_outcomes dataset
  • The Filter - With one line (WHERE status <> 'SUCCESS'), turn a massive stream of data into a dedicated “Failure Feed”
  • The Result - A clean table that any developer can sink into Postgres to build a debugging dashboard in minutes
Here’s the complete Turbo pipeline configuration:
near-execution-outcomes-failures.yaml
name: near-execution-outcomes-failures
resource_size: s

sources:
  execution_outcomes:
    type: dataset
    dataset_name: near.execution_outcomes
    version: 1.0.0
    start_at: latest

transforms:
  failed_executions:
    type: sql
    primary_key: id
    sql: |
      SELECT
        id,
        executor_id,
        status,
        gas_burnt,
        tokens_burnt,
        transaction_hash,
        signer_id,
        trigger_block_height,
        trigger_block_timestamp
      FROM execution_outcomes
      WHERE status <> 'SUCCESS'

sinks:
  postgres_output:
    type: postgres
    from: failed_executions
    schema: public
    table: failed_execution_outcomes
    secret_name: YOUR_POSTGRES_SECRET
    primary_key: id
Add your corresponding secret name and run goldsky turbo apply -f near-execution-outcomes-failures.yaml to deploy the pipeline.

​
Getting support

Can’t find what you’re looking for? Reach out to us at support@goldsky.com for help.