> ## Documentation Index
> Fetch the complete documentation index at: https://docs.goldsky.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Movement Sources

> Build real-time pipelines with Movement mainnet blockchain data

## 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.                            |

<Note>
  The [Datasource explorer](https://app.goldsky.com/data-sources) always has the latest dataset versions. You can also list them with `goldsky dataset list`.
</Note>

## Quick start

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

```yaml theme={null} theme={null}
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
```

```bash theme={null} theme={null}
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:

```yaml theme={null} theme={null}
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:

```yaml theme={null} theme={null}
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

<AccordionGroup>
  <Accordion title="Filter early with SQL">
    Movement produces high volumes of events and activities. Apply filters as early as possible to reduce data volume downstream:

    ```yaml theme={null} theme={null}
    transforms:
      filtered:
        type: sql
        sql: SELECT * FROM movement_events WHERE type = '0x1::coin::DepositEvent'
    ```
  </Accordion>

  <Accordion title="Use appropriate resource sizes">
    For backfills of `raw_events` or `raw_fungible_asset_activities`, consider medium or large resource sizes:

    ```yaml theme={null} theme={null}
    resource_size: m  # or l for large backfills
    ```
  </Accordion>

  <Accordion title="Start with latest for development">
    When building and testing pipelines, use `start_at: latest` to avoid processing large amounts of historical data:

    ```yaml theme={null} theme={null}
    start_at: latest  # Only process new data
    ```
  </Accordion>
</AccordionGroup>

For any questions or feedback, reach out at [support@goldsky.com](mailto:support@goldsky.com).
