datasets

Goldsky Dataset Reference

Reference tables for blockchain datasets available in Turbo pipelines.

For quick dataset questions (e.g., "what dataset for Solana transfers?"), answer directly: identify the chain prefix (see Popular Chain Prefixes below), identify the dataset type (see Common Datasets), and return a YAML snippet like:

sources:
  my_source:
    type: dataset
    dataset_name: <chain>.<dataset>
    version: 1.0.0
    start_at: earliest

Tip: Verify a dataset exists with goldsky dataset get <chain>.<dataset> --outputFormat json — returns the exact slug, version, schema, and isTurboOnly (false = usable by Turbo and Mirror; true = Turbo-only). To browse or search: goldsky dataset list --output json (optionally --group <chain>; the list is a slim index and omits isTurboOnly — use dataset get for that). goldsky turbo validate file.yaml validates a whole Turbo pipeline config — it is not a dataset-existence check (Turbo-specific, needs the turbo binary). ⚠️ Plain `goldsky dataset list` with no flags is an interactive picker that only works in a real terminal — in an agent/CI/piped context it produces no output at all. Always pass --output json (or --group). On an older CLI without those flags, fall back to the public read-only endpoint: curl -s https://api.goldsky.com/api/public/datasets/v1.

Dataset Reference Files

Chain prefix and chain ID information is in the `data/` folder.

Data location: data/ (relative to this skill's directory)

Dataset versions are not pinned in this skill. Version numbers drift as datasets are revised, so confirm the exact version with goldsky dataset get <name> --outputFormat json rather than trusting a static list. The dataset-type and schema tables below are stable references; treat any version number in them as a starting point to validate, not ground truth.

Quick Reference

Common Datasets

Important: Use raw_transactions, NOT transactions

Popular Chain Prefixes

See `data/chain-prefixes.json` for complete list with chain IDs.

Common Dataset Types

EVM Chains

Important: Use raw_transactions, NOT transactions. Use raw_logs, NOT logs (though logs works as an alias on some chains). There is no consumable `decoded_logs` source dataset. For decoded contract events, source from <chain>.raw_logs and decode in a SQL transform via _gs_log_decode(_gs_fetch_abi(<explorer-url>, <source>), topics, data). See /turbo-transforms for the full pattern.

Solana

Bitcoin

Stellar

All datasets use version 1.1.0:

Sui

NEAR

Starknet

Fogo

Dataset Schemas

Source: docs.goldsky.com. Do not use field names not listed here — run goldsky dataset get <chain>.<dataset> --outputFormat json to inspect unknown schemas.

Solana

solana.transactions

No `from_address` or `to_address` on Solana transactions — use accounts array instead.

solana.transactions_with_instructions

All fields from solana.transactions plus:

Instruction object fields: id, index, parent_index, block_slot, block_timestamp, block_hash, tx_signature, tx_fee, tx_index, program_id, data (base58), accounts (string[]), instruction_type

solana.instructions

solana.token_transfers

solana.native_balances

solana.blocks

solana.rewards

solana.token_balances

Schema not fully documented — do not guess field names. Inspect with goldsky dataset get solana.token_balances --outputFormat json.

EVM Chains

<chain>.raw_logs / <chain>.logs

topics is a comma-separated string, not an array. Topic 0 is the event signature hash.

<chain>.raw_transactions

L2 chains also include: receipt_l1_fee, receipt_l1_gas_used, receipt_l1_gas_price, receipt_l1_fee_scalar

<chain>.blocks

<chain>.erc20_transfers

<chain>.erc721_transfers

Dataset Name Format

All datasets follow the pattern: <chain_prefix>.<dataset_type>

Examples:

• ethereum.erc20_transfers - ERC-20 transfers on Ethereum mainnet
• base.logs - All event logs on Base
• matic.blocks - Block data on Polygon
• solana.token_transfers - SPL token transfers on Solana

Finding Dataset Versions

Datasets are versioned. To find available versions:

goldsky dataset get base.erc20_transfers --outputFormat json

Common versions:

• 1.0.0 - Initial version
• 1.2.0 - Enhanced schema (common for ERC-20 transfers)

When in doubt, use the latest version shown by goldsky dataset get <name> --outputFormat json.

Common Discovery Patterns

"I want to track USDC transfers on Base"

1. Dataset: base.erc20_transfers
2. Filter by contract address in your pipeline transform:

transforms:
  usdc_only:
    type: sql
    primary_key: id
    sql: |
      SELECT * FROM source_name
      WHERE address = lower('0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913')

"I want all NFT activity on Ethereum"

Dataset: ethereum.erc721_transfers

"I want to monitor a specific smart contract"

1. Source: <chain>.raw_logs, filtered to the contract address in the source filter
2. To decode events: add a SQL transform calling _gs_log_decode(_gs_fetch_abi(<explorer-url>, <source>), topics, data) AS decoded, then filter downstream by WHERE decoded.event_signature = '<EventName>(<types>)'. Never put topic0 hashes in the source filter.

"I need multi-chain data"

Use multiple sources in your pipeline:

sources:
  eth_transfers:
    type: dataset
    dataset_name: ethereum.erc20_transfers
    version: 1.0.0
    start_at: latest
  base_transfers:
    type: dataset
    dataset_name: base.erc20_transfers
    version: 1.2.0
    start_at: latest

Troubleshooting

Dataset not found

Error: Source 'my_source' references unknown dataset 'invalid.dataset'

Fix:

1. Check the chain prefix is correct (e.g., matic not polygon)
2. Check the dataset type exists (e.g., erc20_transfers not erc20)
3. Run goldsky dataset list --output json to see all available options

Chain not listed

If you can't find a chain in the tables above:

goldsky dataset list --output json | grep -i "<chain_name>"

Some chains use non-obvious prefixes (e.g., Polygon uses matic).

Version mismatch

Error: Version '2.0.0' not found for dataset 'base.erc20_transfers'

Fix: Check available versions:

goldsky dataset get base.erc20_transfers --outputFormat json

Use a version that exists in the output.

Related

• `/turbo-builder` — Interactive wizard to build pipelines using these datasets