Goldsky

Proof of reserves for your stablecoin

Goldsky records your token’s mints and burns and checks supply against your custodian’s reserve figures as often as you schedule it. Healthy results are published on the blockchain.

Talk to our team

Read the guide

At a glance

Circulating supply by chain, in your database
Supply checked against reserves on your schedule
An alert if backing drops below your threshold
Optional automatic pause on a shortfall

Trusted by banks, issuers and blockchain teams

Show your backing between attestations

An attestation tells holders where reserves stood on one date. A scheduled check gives your team a new backing ratio each time it runs.

A current backing ratio
Each run compares tokens in circulation with reported reserves. Your treasury team sees the ratio without waiting for the next report.
An audit trail for each check
Every check logs what it read and what it calculated, and healthy results go on the blockchain with a date.
An alert on a shortfall
If the ratio falls below your threshold, your operations team gets an alert. You can also let the check pause the token or stop payouts.

Proof of reserves on Goldsky: supply, reserve checks and alerts

Goldsky runs the supply tracking and the scheduled check. You set the threshold, connect your custodian and decide what happens when reserves fall short.

A supply ledger

Mints and burns are decoded into a table per token and per chain. Circulating supply is a query.

Scheduled reserve checks

A task built with Goldsky Compose reads supply, calls your custodian’s or bank’s API and works out the ratio.

Alerts and pauses

Below the threshold, the task alerts your team. With your token’s pause permission, it can also pause the token.

A public record

Healthy ratios are written to a smart contract, so holders can look them up themselves.

Treasury reporting

Send the same data to ClickHouse or your warehouse to see who holds the token and how much sits on each chain.

A reserve feed

If other applications need the figure, publish it through a Chainlink-compatible interface. Your operators can switch it off.

Proof of reserves options compared

Table 1. How Goldsky proof of reserves compares with quarterly attestation reports and oracle-based reserve feeds.
Approach	How often it updates	How reserves are checked	Where the data lives	Best fit
Quarterly attestation report	Quarterly	Third-party audit	A static report you can’t query	Formal reserve reporting on a fixed date
Chainlink Proof of Reserve	Per feed, triggered by the oracle	A decentralized oracle network, about 10–16 nodes per feed	An onchain feed that smart contracts read	Protocols that need a reserve feed other contracts can use
Built on Goldsky	As often as every few minutes	Supply compared with your custodian’s reserve API	Your Postgres, ClickHouse or warehouse, plus a record on the blockchain	Issuers and banks that want a queryable ledger in their own reporting

stablecoin supply outstanding, June 2026: $315B
in USDC and USDT transfers reorged out of Ethereum in 90 days: $6.7B

Source: The Fintech Guide to Stablecoin Data Infrastructure

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 proof of reserves today

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

Open in Claude Code

I'm building continuous proof of reserves for a stablecoin 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/treasury-and-reserves

Help me:

1. Set up a Turbo pipeline that decodes mint and burn events into a supply ledger in our database
2. Maintain circulating supply as a running total per token and per chain
3. Add a scheduled Compose task that reads onchain supply, fetches reserves from our custodian API, and computes the collateralization ratio
4. Alert and optionally pause the token when the ratio falls below our threshold

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

Make your backing ratio a number you can show

Bring your token and custodian setup to a 30-minute call and leave with a concrete plan.

Talk to our team

Read the guide

Frequently asked questions

How is this different from a quarterly attestation?

An attestation covers one date and is done by an outside firm. Goldsky’s check runs on the schedule you set and reads your custodian’s figures each time, so you have a current number between reports. It sits alongside your attestations.

Where do the reserve figures come from?

From your custodian’s or bank’s API. The scheduled task calls it on every run.

How can auditors check the figures?

Each check logs its inputs and its result, and healthy results are recorded on the blockchain. Your team can walk an auditor through how any figure was calculated.

Will it pause our token without asking?

Only if you set it up to and give the task your token’s pause permission. Otherwise a shortfall sends an alert and your team decides.

Where does the supply data live?

In your Postgres database. You can send a copy to ClickHouse or a warehouse for reporting.

The Fintech Guide to Stablecoin Data Infrastructure Goldsky for Fintech Compliance and AML monitoring

Turbo streaming pipelines Compose