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

# Scroll

> Scroll support on Goldsky: Turbo pipelines, Edge RPC, Compose, and Subgraphs on Scroll Mainnet, with CLI setup steps to get started.

#### Scroll Mainnet<table><tbody><tr><td>Chain ID</td>
<td>`534352`</td></tr>
<tr><td>Currency</td>
<td>ETH</td></tr>
<tr><td>Explorer</td>
<td>[https://scrollscan.com](https://scrollscan.com)</td></tr></tbody></table>[https://edge.goldsky.com/standard/evm/534352?key=YOUR\_KEY](https://edge.goldsky.com/standard/evm/534352?key=YOUR_KEY)#### Scroll Sepolia<table><tbody><tr><td>Chain ID</td>
<td>`534351`</td></tr>
<tr><td>Currency</td>
<td>ETH</td></tr>
<tr><td>Explorer</td>
<td>[https://sepolia.scrollscan.com](https://sepolia.scrollscan.com)</td></tr></tbody></table>## OverviewGoldsky is the modern back-end for crypto-enabled products; the infrastructure layer between your application and the blockchain. We handle the complex, undifferentiated work of building on crypto rails: streaming real-time data, maintaining reliable chain connectivity, and executing onchain logic. Teams use Goldsky to ship faster and stay focused on their core product.## Getting startedTo use Goldsky, you'll need to create an account, install the CLI, and log in. If you want to use Turbo or Compose, you'll also need to install their respective CLI extensions.> [accordion] Install Goldsky CLI and log in
>
> 1. Install the Goldsky CLI:
>
>    **For macOS/Linux:**
>
>    ```shell theme={"dark"}
>    curl https://goldsky.com | sh
>    ```
>
>    **For Windows:**
>
>    ```shell theme={"dark"}
>    npm install -g @goldskycom/cli
>    ```
>
>    > [!NOTE]
>    >
>    > Windows users need to have Node.js and npm installed first. Download from [nodejs.org](https://nodejs.org) if not already installed.
> 2. Log into your Project by running:
>    ```shell theme={"dark"}
>    goldsky login
>    ```
>    This opens your browser to sign in (Google, GitHub, SSO, or email). Once you authenticate, the CLI is logged in automatically — there's no API key to copy or paste.
>    \[!NOTE] On a headless or remote machine (or in CI), create an API key on your [Project Settings](https://app.goldsky.com/dashboard/settings) page and pass it directly with `goldsky login --token <API_KEY>`. Use `goldsky login --no-browser` to print the login URL instead of opening a browser.
> 3. Now that you are logged in, run `goldsky` to get started:
>    ```shell theme={"dark"}
>    goldsky
>    ```> [accordion] Install Turbo CLI extension
>
> If you already have the Goldsky CLI installed, install the Turbo extension by running:
>
> ```bash theme={"dark"}
> goldsky turbo
> ```
>
> This will automatically install the Turbo extension. Verify the installation:
>
> ```bash theme={"dark"}
> goldsky turbo list
> ```
>
> > [!NOTE]
> >
> > Make sure to update the CLI to the latest version before running Turbo commands: `curl https://goldsky.com | sh`
>
> For a complete reference of all Turbo CLI commands, see the [CLI Reference](https://docs.goldsky.com/turbo-pipelines/cli-reference.md) guide.> [accordion] Install Compose CLI extension
>
> If you already have the Goldsky CLI installed, install the Compose extension by running:
>
> ```bash theme={"dark"}
> goldsky compose install
> ```
>
> To update to the latest version:
>
> ```bash theme={"dark"}
> goldsky compose update
> ```
>
> For more details, see the [Compose quickstart](https://docs.goldsky.com/compose/quick-start.md) guide.## SubgraphsMAINNET SUPPORTEDScroll subgraphs can be deployed on Goldsky in 2 ways:<ul><li>Via CLI from a local subgraph configuration file. If you are familiar with developing subgraphs already, you'll be familiar with this approach; after defining a subgraph locally (with a `subgraph.yaml` file, a `schema.graphql` file, and the necessary mappings to translate raw event data into the entities defined in the schema), you can deploy subgraphs to Goldsky (once the Goldsky CLI is installed) using `goldsky subgraph deploy <name>/<version> --path .` For more, read the [step-by-step guide](https://docs.goldsky.com/subgraphs/deploying-subgraphs.md).</li>
<li>Via instant subgraphs, where you can pass through a contract address and the ABI for that contract. This is a quick-start option that automatically generates the underlying subgraph configuration files on your behalf, making it easy to extract blockchain event data and serve it as an API endpoint without complex setup. Use the `--from-abi` flag in the command above instead of `--path`. For more, read the [low-code subgraphs guide](https://docs.goldsky.com/subgraphs/guides/create-a-low-code-subgraph.md).</li></ul>[Subgraphs network names use a different convention than Turbo chain slugs](https://docs.goldsky.com/chains/supported-networks.md#chain-identifiers-subgraphs-vs-turbo); don't mix them up.## TurboMAINNET SUPPORTEDTurbo pipelines provide high-performance streaming data pipelines with sub-second latency. Deploy a pipeline to start streaming Scroll data to your preferred destination.### Quick deployValidate and deploy a Turbo pipeline with the CLI:goldsky turbo validate scroll\_mainnet-pipeline.yaml
goldsky turbo apply scroll\_mainnet-pipeline.yaml### Configuration fileTurbo pipelines are defined in a YAML configuration file. Reference a Scroll dataset by its `dataset_name` and pinned `version`, then send it to your configured sink. See the specific Scroll datasets and versions in the section below\.name: my-scroll\_mainnet-pipeline
resource\_size: ssources:
scroll\_mainnet\_source:
type: dataset
dataset\_name: \<DATASET\_NAME>   # e.g. scroll\_mainnet.\<dataset>
version: \<DATASET\_VERSION>     # pin to a specific version
start\_at: latest               # or 'earliest' to process all historical datasinks:
postgres\_scroll\_mainnet:
type: postgres
from: scroll\_mainnet\_source
schema: public
table: scroll\_mainnet\_data
secret\_name: \<YOUR\_SECRET\_NAME>
primary\_key: id### Available chain slugsThese are the Goldsky Turbo chain slugs for Scroll (not the Subgraphs network name above):
Mainnet: `scroll_mainnet`For the full configuration reference, see the [Turbo documentation](https://docs.goldsky.com/turbo-pipelines/introduction.md). See [chain identifiers: Subgraphs vs. Turbo](https://docs.goldsky.com/chains/supported-networks.md#chain-identifiers-subgraphs-vs-turbo) if you need the Subgraphs network name instead.## Edge RPC
      

MAINNET SUPPORTED


      

Edge RPC provides reliable, high-performance RPC access for Scroll with low latency via multi-region CDN, intelligent caching, automatic failover, and built-in observability—optimized for both indexing backends and frontend applications.


      
      

\### RPC endpoints


      \<table><thead><tr><th>Network</th>
            \<th>Chain ID</th>
            \<th>Endpoint</th></tr></thead>
        \<tbody><tr><td>Mainnet</td>
              \<td>`534352`</td>
              \<td>`https://edge.goldsky.com/standard/evm/534352?key=YOUR_KEY`</td></tr></tbody></table>
      
      

\### Usage examples


      

curl "https://edge.goldsky.com/standard/evm/534352?key=YOUR_KEY" \\\
  -X POST \\\
  -H "Content-Type: application/json" \\\
  -d '\\{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1\\}'


        

import \\{ JsonRpcProvider \\} from 'ethers'

const provider = new JsonRpcProvider('https://edge.goldsky.com/standard/evm/534352?key=YOUR_KEY')
const blockNumber = await provider.getBlockNumber()


        

import \\{ createPublicClient, http \\} from 'viem'

const client = createPublicClient(\\{
  transport: http('https://edge.goldsky.com/standard/evm/534352?key=YOUR_KEY')
\\})
const blockNumber = await client.getBlockNumber()


      
      

For the full list of supported RPC methods and configuration options, see the [Edge RPC documentation](https://docs.goldsky.com/edge-rpc/introduction.md).


    ## ComposeMAINNET SUPPORTEDCompose lets you build offchain-to-onchain systems that durably move data and execute logic between your application and Scroll. Write TypeScript code that runs in verifiable sandboxes with full tracing and auditability.### Quick startInitialize a new Compose application:goldsky compose init my-scroll\_mainnet-appThis creates a project structure with example tasks you can customize:my-scroll\_mainnet-app/
├── compose.yaml      # App manifest and configuration
├── tasks/            # Executable task definitions
│   ├── task\_a.ts
│   └── task\_b.ts
└── .gitignore### Run locallyStart your Compose application in development mode:cd my-scroll\_mainnet-app
goldsky compose startTest a task execution:goldsky compose callTask my\_task '\{}' --env local### Deploy to productionWhen ready, deploy your application to Goldsky's managed infrastructure:goldsky compose deployFor the full guide on building Compose applications, see the [Compose documentation](https://docs.goldsky.com/compose/introduction.md).## Getting supportCan't find what you're looking for? Reach out to us at [support@goldsky.com](mailto:support@goldsky.com) for help.


## Related topics

- [Stablecoin contract addresses](https://docs.goldsky.com/turbo-pipelines/guides/token-transfers/stablecoin-addresses.md)
- [Live inspect](https://docs.goldsky.com/turbo-pipelines/live-inspect.md)
- [Turbo CLI Reference](https://docs.goldsky.com/turbo-pipelines/cli-reference.md)
- [Prometheus integration](https://docs.goldsky.com/turbo-pipelines/prometheus-integration.md)
- [ERC-1155 transfers](https://docs.goldsky.com/turbo-pipelines/guides/token-transfers/ERC-1155-transfers.md)
