How to build real-time Movement data pipelines

Overview

Goldsky provides curated Movement mainnet datasets covering events, transactions, fungible assets, table items, and objects from the Move VM. Use these datasets to build real-time pipelines on top of Movement without managing raw node infrastructure.

Available datasets

All Movement datasets live under the movement_mainnet namespace.

Dataset	Description
`movement_mainnet.raw_events`	All emitted contract event logs — useful for indexing arbitrary contract behavior.
`movement_mainnet.raw_user_transactions`	All raw onchain transactions involving account-level actions (version, sender, payload, etc.).
`movement_mainnet.raw_block_metadata_transactions`	Metadata about blocks and block-level transactions (block height, epoch, version).
`movement_mainnet.raw_fungible_asset_metadata`	Static metadata for fungible tokens — decimals, symbol, name, and supply.
`movement_mainnet.raw_fungible_asset_activities`	Activity feed for fungible tokens — owner address, amount, and activity type.
`movement_mainnet.raw_current_fungible_asset_balances`	Current balances of fungible tokens across accounts.
`movement_mainnet.raw_fungible_asset_to_coin_mappings`	Mapping between fungible asset addresses and their legacy coin type identifiers.
`movement_mainnet.raw_table_items`	Raw items stored in Move tables, including key, value, and table handle.
`movement_mainnet.raw_objects`	Move object records, including owner, address, and object metadata.
`movement_mainnet.raw_current_token_ownerships_v2`	Current NFT and token ownership records per account.
`movement_mainnet.raw_current_token_datas_v2`	Current token metadata including collection, name, URI, and properties.
`movement_mainnet.raw_token_activities_v2`	Activity feed for tokens — mints, transfers, burns, and mutations.
`movement_mainnet.raw_account_transactions`	Per-account transaction index mapping accounts to transaction versions.
`movement_mainnet.raw_move_modules`	Published Move modules, including bytecode, ABI, and deployer address.

The Datasource explorer always has the latest dataset versions. You can also list them with goldsky dataset list.

Quick start

The fastest way to explore Movement data is with a blackhole sink and goldsky turbo inspect:

name: demo-movement-events-blackhole
resource_size: s

sources:
  movement_events:
    type: dataset
    dataset_name: movement_mainnet.raw_events
    version: 1.0.0
    start_at: latest

sinks:
  dev_sink:
    type: blackhole
    from: movement_events

goldsky turbo apply demo.yaml
goldsky turbo inspect demo-movement-events-blackhole

Guide: Track fungible asset activity

Stream fungible asset activities (transfers, mints, burns) into Postgres for accounting and analytics:

name: movement-fungible-asset-activities
resource_size: s

sources:
  fa_activities:
    type: dataset
    dataset_name: movement_mainnet.raw_fungible_asset_activities
    version: 1.0.0
    start_at: latest

sinks:
  postgres_output:
    type: postgres
    from: fa_activities
    schema: public
    table: movement_fa_activities
    secret_name: MY_POSTGRES_SECRET
    primary_key: id

Guide: Monitor a specific account

Filter user transactions to a single Movement account:

name: movement-account-transactions
resource_size: s

sources:
  user_txns:
    type: dataset
    dataset_name: movement_mainnet.raw_user_transactions
    version: 1.0.0
    start_at: latest

transforms:
  account_txns:
    type: sql
    primary_key: id
    sql: |
      SELECT *
      FROM user_txns
      WHERE sender = '0xabc...'

sinks:
  postgres_output:
    type: postgres
    from: account_txns
    schema: public
    table: movement_account_transactions
    secret_name: MY_POSTGRES_SECRET
    primary_key: id

Performance tips

Filter early with SQL

Movement produces high volumes of events and activities. Apply filters as early as possible to reduce data volume downstream:

transforms:
  filtered:
    type: sql
    sql: SELECT * FROM movement_events WHERE type = '0x1::coin::DepositEvent'

Use appropriate resource sizes

For backfills of raw_events or raw_fungible_asset_activities, consider medium or large resource sizes:

resource_size: m  # or l for large backfills

Start with latest for development

When building and testing pipelines, use start_at: latest to avoid processing large amounts of historical data:

start_at: latest  # Only process new data

For any questions or feedback, reach out at support@goldsky.com.

Turbo

API

Reference

Movement Sources

Overview

Available datasets

Quick start

Guide: Track fungible asset activity

Guide: Monitor a specific account

Performance tips

​Overview

​Available datasets

​Quick start

​Guide: Track fungible asset activity

​Guide: Monitor a specific account

​Performance tips

Overview

Available datasets

Quick start

Guide: Track fungible asset activity

Guide: Monitor a specific account

Performance tips