Skip to main content

​
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.
DatasetDescription
movement_mainnet.raw_eventsAll emitted contract event logs — useful for indexing arbitrary contract behavior.
movement_mainnet.raw_user_transactionsAll raw onchain transactions involving account-level actions (version, sender, payload, etc.).
movement_mainnet.raw_block_metadata_transactionsMetadata about blocks and block-level transactions (block height, epoch, version).
movement_mainnet.raw_fungible_asset_metadataStatic metadata for fungible tokens — decimals, symbol, name, and supply.
movement_mainnet.raw_fungible_asset_activitiesActivity feed for fungible tokens — owner address, amount, and activity type.
movement_mainnet.raw_current_fungible_asset_balancesCurrent balances of fungible tokens across accounts.
movement_mainnet.raw_fungible_asset_to_coin_mappingsMapping between fungible asset addresses and their legacy coin type identifiers.
movement_mainnet.raw_table_itemsRaw items stored in Move tables, including key, value, and table handle.
movement_mainnet.raw_objectsMove object records, including owner, address, and object metadata.
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

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'
For backfills of raw_events or raw_fungible_asset_activities, consider medium or large resource sizes:
resource_size: m  # or l for large backfills
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.