How Goldsky Brings Real-Time Onchain Data to Arc

Building on Arc means your contracts can settle in under a second. But settlement is only half the job. The applications, systems, and workflows around your contract (e.g., dashboards, ledgers, alerts, automated logic) need access to that activity in a form they can use. That's the data layer problem. Goldsky has joined the Arc ecosystem with support from the Arc Builders Fund to bring that data layer to teams building on Arc.

Goldsky provides managed subgraphs and real-time data pipelines that turn onchain events into structured, queryable data without requiring you to run your own indexing infrastructure. Goldsky’s infrastructure (which is purpose-built for high-throughput onchain environments) gives developers managed ways to index contract activity, query it through APIs, stream it into the databases and queues their applications already use, and write back onchain when a workflow calls for it.

For Arc builders, this helps address an important gap between deploying a contract and operating a product around it.

What Goldsky is building for Arc

Goldsky offers a full stack for working with Arc data: Edge RPC for reliable node access, subgraphs for queryable application data, Turbo Pipelines for real-time streaming, and Compose for offchain-to-onchain execution. Each handles a different part of the problem of making onchain activity useful to running applications.

Goldsky’s subgraphs turn contract events into a structured data model that applications can query through GraphQL. A team defines the contracts and events it cares about, then retrieves application-specific information without maintaining its own indexing service.

Subgraphs are useful when a product needs clear, repeatable answers of an onchain state: 

• Which payments are settled? 
• What is the current balance? 
• Which accounts interacted with a contract? 
• What changed during a specific period?

Goldsky’s Turbo Pipelines serve a different job and can be thought of as high-speed streaming data solutions. They process and organize onchain data into destinations controlled by the developer, using SQL and TypeScript transformations to shape the data along the way. Instead of repeatedly polling an endpoint, a team can route relevant activity into its operational systems as it arrives.

For example, an Arc payments app could tell Turbo: “Watch for USDC¹ payments to these merchant wallets. Turn each raw transaction into a simple record with the sender, amount, and time. Send it to our database and notify our dashboard.”

Think of a blockchain as a firehose spraying out millions of digital receipts and a Turbo Pipeline as an automated sorting station attached to that firehose that:

1. Watches the blockchain for new activity.
2. Keeps only the events your application cares about.
3. Cleans, decodes, or adds information to them.
4. Sends the finished data to your database, webhook, or other system.

Builders can use these together: a subgraph to power customer-facing queries alongside a pipeline that routes the same events into an alerting system or internal ledger.

Goldsky’s Edge RPC gives Arc builders a multi-region endpoint with cross-node consensus validation and automatic failover, so applications reading Arc state directly aren’t exposed to a single provider’s downtime.

Goldsky’s Compose closes the loop in the other direction. Where subgraphs and pipelines move onchain activity out to your systems, Compose lets teams write TypeScript that moves money, data, and events from offchain systems (e.g., settling a payment, posting collateral, publishing a rate) back onchain with durable, auditable, verifiable execution. For financial applications on Arc, that turns observation into operation.

What Arc builders can create with Goldsky

Goldsky’s infrastructure supports several practical product patterns:

• Payment and settlement tracking: Surface transaction statuses in dashboards, receipts, customer histories, and support tools.
• Treasury reconciliation: Route transfer and contract events into accounting databases or internal ledgers.
• Monitoring and alerting: Watch selected contracts, addresses, or events. Notify an operations team when defined conditions occur.
• Analytics and reporting: Build structured datasets for product metrics, transaction analysis, and ecosystem dashboards.
• Market and risk systems: Feed current onchain activity into tools that monitor balances, positions, liquidity, or contract behavior.
• Automated workflows: Give backend services and agents the event streams they need to respond programmatically to onchain activity, or use Compose to execute the resulting onchain action.

These use cases are a core part of what turns deployed contracts into applications that people and businesses can operate.

Why the data layer matters on Arc

Arc is an open internet platform purpose-built for stablecoin finance, with USDC-denominated gas and deterministic sub-second finality. Those network properties shape how financial applications execute. Goldsky helps carry the resulting activity into the application and operational layers where teams can use it.

Final settlement needs a usable record

Arc transactions reach deterministic finality in under a second. Once a transaction is confirmed, an application can treat the result as final rather than building around a probabilistic confirmation window. Goldsky helps move that final result into the systems surrounding the contract. A payment status can appear in an application. An alert can reach an operations team. The network establishes the outcome; the data layer makes that outcome accessible.

USDC gas makes operational data easier to interpret

Gas fees on Arc are denominated in stablecoins, starting with USDC. For applications that track high volumes of payments or automated actions, this keeps the gas asset aligned with a familiar unit of account. When that activity flows into reporting and analytics systems, teams can review transaction costs without maintaining a separate gas token workflow. Goldsky provides the indexing and pipeline infrastructure needed to organize that activity around the app’s own data model.

Stablecoin applications depend on current information

Payments, treasury tools, markets, and automated financial workflows all depend on timely updates. An accounting system needs transaction records. A market application needs current balances and contract events. An agent needs a reliable signal before proceeding. Arc provides the execution and settlement environment for these applications while Goldsky gives their backends a direct route to the data produced there.

Building readiness before mainnet

The Arc Builders Fund supports teams working on financial applications and services that benefit from Arc’s unique network properties, with capital and hands-on support from Arc’s core teams. Goldsky’s participation focuses that support on a foundational part of the developer stack.

Goldsky's testnet availability gives teams time to design their data models, test operational workflows, and identify bottlenecks before mainnet. Teams using subgraph-based workflows can bring that model to Arc, while teams that need direct control over their data can stream it into their existing systems. Goldsky adds a key part of that data infrastructure foundation for Arc.

Build with Goldsky on Arc

Goldsky support is now available for Arc testnet with expected support for the upcoming Arc mainnet launch. Start today by choosing what fits your application: a queryable subgraph, a real-time pipeline, direct RPC access, onchain execution through Compose, or any combination.

For builders interested in what’s possible on Arc, visit the Arc docs to learn more.

Join the Arc Discord to connect with the Arc team and builder community.