Goldsky

Arbitrum One

Q: What is Arbitrum One?

Arbitrum One is a blockchain network supported by Goldsky for real-time data indexing and streaming. Goldsky makes it easy to access Arbitrum One data through subgraphs, data pipelines, and RPC endpoints, so your team spends less time on infrastructure and more time building your product.

Q: How do I start indexing Arbitrum One data with Goldsky?

Sign up for a free Goldsky account, then deploy a subgraph or pipeline against Arbitrum One in minutes. Goldsky handles node infrastructure, reorg detection, and data freshness automatically.

Q: Can I run a subgraph on Arbitrum One?

Yes. Goldsky Subgraphs run on Arbitrum One and are fully compatible with The Graph protocol, so you can migrate existing subgraphs with a single CLI command. Queries are served via a standard GraphQL API with sub-second indexing latency.

Q: How do I stream Arbitrum One data to my database or data warehouse?

Goldsky Turbo Pipelines stream Arbitrum One blockchain data in real time to destinations like PostgreSQL, ClickHouse, S3, and Kafka. You define a pipeline in a YAML config and Goldsky handles delivery, reorgs, and schema management. No custom ETL code required. Turbo Pipelines is the successor to Mirror.

Q: Does Goldsky offer a Arbitrum One RPC endpoint?

Yes. Goldsky Edge provides a low-latency Arbitrum One RPC endpoint with global edge distribution, high availability, and automatic failover. It is a drop-in replacement for any standard EVM JSON-RPC provider.

Q: How much does it cost to index Arbitrum One data with Goldsky?

Goldsky offers a free $100 in credit to try out Goldsky, so you can start building right away. Paid plans scale with usage. Creating an account is free and no credit card is required to get started.

Q: How fresh is the Arbitrum One data available through Goldsky?

Goldsky indexes Arbitrum One blocks as they land on-chain, typically delivering data with sub-second latency after confirmation. Reorgs are handled automatically, so your application always reflects the current canonical chain state.

Arbitrum One is a leading optimistic rollup on Ethereum, offering secure, low-fee transactions and full EVM compatibility. It's widely adopted across DeFi, infrastructure, and gaming — and serves as the flagship chain in the Arbitrum ecosystem.

Start indexing

See Arbitrum One datasets →

Goldsky powers the web3 products you use

How to index Arbitrum One data with Goldsky

Turbo Pipelines

Stream Arbitrum One data with the latest blockchain data streaming engine. Vectorized processing, instant deployment, and live data inspection without needing an enterprise team.

Ideal for:

Instant deployment – pipelines spin up in seconds; index Arbitrum One instantly
Live data previews – inspect what every part of your pipelines produce in real-time
TypeScript transforms – execute custom logic with WebAssembly
Dynamic tables – unlimted filtering on addresses & contracts without redeploying
Local debugging – iterate on Arbitrum One data on your machine

Subgraphs

Query Arbitrum One data with an instant GraphQL API. Perfect for familiarity, fast setups, on-chain data queries, and getting to market quickly.

Ideal for:

Teams building on Arbitrum One who want quick setup & minimal infrastructure overhead
Production-ready Arbitrum One API endpoints
Moderate traffic and throughput scenarios
Predefined data models and standard query patterns
On-chain data from EVM-compatible chains

Website

arbitrum.io

EVM Compatible

Yes

Products

Subgraphs Edge Turbo Compose

Supported Networks

Mainnet, Arbitrum Sepolia

Get an Arbitrum One RPC endpoint

Edge RPC

Create an instant Arbitrum One RPC endpoint with global edge distribution. Built for apps that demand reliable, low latency access without running your own node infrastructure.

Key benefits:

<10ms latency from tip-of-the-chain CDN
<50ms latency from 8+ global edge regions
99.9% uptime with automatic failover
Data integrity mechanisms & cross-validation
Optimized for indexing
Built-in observability
Compatible with your existing RPC endpoints

Try Edge for free or learn more

Deploy your Arbitrum One data stack by --:--

Creating an account is free. No credit card needed.

Get started for free

Arbitrum One data: frequently asked questions

What is Arbitrum One?

Arbitrum One is a blockchain network supported by Goldsky for real-time data indexing and streaming. Goldsky makes it easy to access Arbitrum One data through subgraphs, data pipelines, and RPC endpoints, so your team spends less time on infrastructure and more time building your product.

How do I start indexing Arbitrum One data with Goldsky?

Sign up for a free Goldsky account, then deploy a subgraph or pipeline against Arbitrum One in minutes. Goldsky handles node infrastructure, reorg detection, and data freshness automatically.

Can I run a subgraph on Arbitrum One?

Yes. Goldsky Subgraphs run on Arbitrum One and are fully compatible with The Graph protocol, so you can migrate existing subgraphs with a single CLI command. Queries are served via a standard GraphQL API with sub-second indexing latency.

How do I stream Arbitrum One data to my database or data warehouse?

Goldsky Turbo Pipelines stream Arbitrum One blockchain data in real time to destinations like PostgreSQL, ClickHouse, S3, and Kafka. You define a pipeline in a YAML config and Goldsky handles delivery, reorgs, and schema management. No custom ETL code required. Turbo Pipelines is the successor to Mirror.

Does Goldsky offer a Arbitrum One RPC endpoint?

Yes. Goldsky Edge provides a low-latency Arbitrum One RPC endpoint with global edge distribution, high availability, and automatic failover. It is a drop-in replacement for any standard EVM JSON-RPC provider.

How much does it cost to index Arbitrum One data with Goldsky?

Goldsky offers a free $100 in credit to try out Goldsky, so you can start building right away. Paid plans scale with usage. Creating an account is free and no credit card is required to get started.

How fresh is the Arbitrum One data available through Goldsky?

Goldsky indexes Arbitrum One blocks as they land on-chain, typically delivering data with sub-second latency after confirmation. Reorgs are handled automatically, so your application always reflects the current canonical chain state.