Goldsky

A settlement ledger for cross-chain USDC

When you move USDC between chains, Goldsky records both ends of each transfer in your database. Treasury and payments teams can see what has arrived, what’s in transit and what’s late.

Talk to our team

Read the guide

At a glance

Each transfer as one row, with both ends matched
Money in transit shown against where it’s headed
An alert when a transfer passes your deadline
Settlement times for each route you use

Trusted by payment companies, fintechs and blockchain teams

Account for USDC while it’s between chains

Circle’s Cross-Chain Transfer Protocol (CCTP) burns USDC on one chain and mints it on another. In between, the money isn’t on either chain’s balance, and that’s the part that’s hard to report on.

A full cash figure
Settled balances on each chain plus what’s still in transit, from one query. When finance asks where the money is, the answer is in one table.
Late transfers flagged
Transfers past your deadline are checked with Circle and flagged with the transfer ID and sending transaction, so someone can look into them.
Numbers for liquidity planning
Volume and settlement time for each route help you decide how much USDC to keep on each chain.

USDC settlement on Goldsky: matched transfers, status and late alerts

Both ends of each transfer, matched, in your Postgres database.

Matched burns and mints

The burn on the sending chain and the mint on the receiving chain are joined by transfer ID into one row.

Status

Each transfer is settled, in transit or past your deadline, with the time it left and the time it arrived.

Cash by chain

Add settled balances to in-transit amounts by destination to see where your working capital is.

Late-transfer checks

A scheduled Goldsky Compose task asks Circle about each late transfer and escalates any that haven’t completed. Each check is logged.

More chains

Adding a chain is one more source in the same pipeline.

Route timing

With both timestamps in your database, you can report the typical and slowest settlement time for each route.

Built for regulated environments

SOC 2 Type II, dedicated and on-premises deployment, and access controls for banks, payment companies and trading firms.

SOC 2 Type II

Goldsky maintains SOC 2 Type II compliance.

Dedicated infrastructure

Single-tenant infrastructure in Goldsky-managed cloud accounts, with static IPs for allowlisting, on Enterprise.

On-premises and BYOC

Run the full stack on-prem or in your own cloud, so data and compute stay inside your boundary.

Access controls

Role-based access on every plan, plus SAML SSO and audit logs on Enterprise.

Complete, validated data

Every block is checked for completeness before delivery, and daily validation repairs any gaps.

Data for your compliance program

Transfer and identity data for MiCA, Travel Rule and BSA/AML: Goldsky supplies it, your team owns the program.

Deliver on your timeline

Banks, payment companies and trading firms use Goldsky to get onchain products live in weeks. Our engineers work with yours from the first call to production.

Scoping call

We learn what your digital asset product needs and give you a delivery estimate.

Proof of concept

Our engineers and yours build a working version on your own data.

Kickoff and go live

We launch it together and check the numbers against your systems.

Ongoing support

24/7 support in a shared channel with the engineers who run your infrastructure.

Step 1
Scoping call
We learn what your digital asset product needs and give you a delivery estimate.
Step 2
Proof of concept
Our engineers and yours build a working version on your own data.
Step 3
Kickoff and go live
We launch it together and check the numbers against your systems.
Ongoing
Ongoing support
24/7 support in a shared channel with the engineers who run your infrastructure.

Book a scoping call

Build a USDC settlement ledger today

Copy the prompt into your AI coding agent and build a working version today.

Open in Claude Code

I'm building a cross-chain USDC settlement ledger using Goldsky.

## Set up your tooling first

```bash
npx skills add goldsky-io/goldsky-agent
```

That installs to Claude Code, Cursor, Codex, Windsurf and 30+ other agents. Then connect Goldsky's MCP server at `https://docs.goldsky.com/mcp` however your tool does it — per-client setup is at https://docs.goldsky.com/mcp-server

Finally, use the `auth-setup` skill to install the Goldsky CLI if it's missing, and confirm I'm logged in before you start.

## What I'm building

Follow the Goldsky guide at https://docs.goldsky.com/solutions/cross-chain-settlement

Help me:

1. Set up a Turbo pipeline that indexes CCTP burn events across the chains I use into one table
2. Set up a second pipeline for the mint side on each destination chain
3. Write the reconciliation query that joins them on source domain and nonce and returns settled, in-flight and delayed
4. Add a scheduled Compose task that checks Circle's attestation API for transfers older than my settlement deadline and alerts on incomplete ones

## How to work

- Confirm dataset names yourself rather than assuming them
- Write the files, and create any Goldsky secrets the pipeline needs
- Validate locally — `goldsky turbo validate` for pipelines, a local task call for Compose
- Ask me for anything you can't determine: contract addresses, endpoints, thresholds, which database we're writing to
- Put credentials straight into Goldsky secrets, never into this chat

**Stop before deploying anything live**, then show me the commands to run.

See your whole USDC position, including what’s in transit

Bring your routes and settlement deadlines to a 30-minute call and leave with a concrete plan.

Talk to our team

Read the guide

Frequently asked questions

How long does a CCTP transfer take?

It depends on the transfer type and the sending chain. The ledger records when each transfer left and arrived, and you choose the deadline that counts as late.

Which chains does the settlement ledger cover?

The chains you add as sources, as long as both Circle’s CCTP and Goldsky support them.

Is this native USDC or a wrapped token?

Native USDC. CCTP burns USDC on one chain and mints the same amount on the other, with no wrapped token or bridge pool in between.

Who sets the rules?

Your team. The ledger is in your Postgres database, and the matching query and the late-transfer deadline are yours to change.