Goldsky

Goldsky for Banking

An onchain data pipeline built for compliance monitoring

An onchain data pipeline for compliance monitoring reads transfer events from public chains and screens both counterparties of every transfer against a watchlist, in near real time. Goldsky streams stablecoin transfers into your database, screens sender and recipient against a table you can update at runtime, and pushes hits to your case-management system through a webhook. A Compose task verifies each hit with your sanctions provider and writes a tamper-evident attestation onchain, so a decision is a record, not a reconstruction.

Talk to our team

Read the guide

Highlights

Sanctions listings enforced within seconds of being added
Sender and recipient screened on every single transfer
Hits pushed to your case management system as they happen
Your watchlist and flagged transfers in your own database

Trusted by leading financial and blockchain teams

Public networks make continuous screening possible

Every stablecoin transfer is public and available in real time. What remains is operational: watching every flow as it happens, applying a sanctions change within minutes, and showing afterwards exactly what you did and why.

Change the list without touching the pipeline

A sanctions update reaches production as a row in a table rather than a deploy. The running pipeline applies it on its next batch, so you can tell an examiner a listing was enforced the day it was published.

Decisions you can defend

Each decision carries a full execution trace, recorded onchain. When an examiner asks how you decided, you have a record rather than a reconstruction.

Regulated data stays yours

The watchlist and every flagged transfer live in your own database, which keeps regulated data inside your compliance boundary and makes residency and retention obligations tractable.

What continuous screening gives your compliance team

Screening, escalation and attestation running as managed infrastructure, with your watchlist and your provider in the loop.

Both counterparties screened

Every transfer is screened against the watchlist for both sender and recipient. Each hit identifies the matching party for your analysts.

A watchlist you update at runtime

Insert an address from any Postgres client and the running pipeline applies it on its next batch. No redeploy, and no re-sync of history.

Straight into case management

A webhook sink pushes each hit to your case management system one row at a time, while a Postgres sink keeps the durable record for audit.

Issuer enforcement events

A second pipeline decodes token-policy events into a ledger: updates, blocked transfers and burns, and pauses.

Verified and attested

A Compose task calls your sanctions or KYC provider with durable retries, then writes a tamper-evident attestation onchain through a gas-sponsored wallet.

One pattern across chains

Screening runs off transfer events, which every fungible token standard emits, so the same pipeline shape covers every chain and asset you support rather than one surveillance layer per rail.

Where Goldsky's screening pipeline sits

Table 1. Where Goldsky's screening pipeline sits relative to KYT/attribution vendors and policy-enforcement tools.
Layer	Example providers	What they own	What Goldsky adds
Attribution & risk scoring (KYT)	Chainalysis, TRM Labs, Elliptic	Linking an address to a real-world entity, plus sanctions and risk lists	Streams the underlying transfer events these vendors screen, decoded and joined, into your own database
Policy enforcement	Predicate, Blockaid	Programmable transaction rules before execution	Decodes issuer-level policy events (freezes, blacklists) alongside plain transfers for standards that emit them
Data + attestation infrastructure	Goldsky	Watchlist table, flagged-transfer pipeline, webhook to case management, onchain attestation of each decision	—

82–99%

of stablecoin transfers fall under $3,000 on every rail measured

1 in 6+

Ethereum stablecoin transfers is address-poisoning spam, across 100,137 clusters

Sourced from The Fintech Guide to Stablecoin Data Infrastructure

Built for regulated environments

Controls, documentation and support your reviewers expect, ready before they ask.

SOC 2 Type II

Independently audited controls, with reports available for your security review.

Dedicated infrastructure

Isolated compute and single-tenant options for your production workloads.

Granular access controls

Role-based permissions and audit logging across your whole organization.

Full observability

Monitoring, alerting and data-lineage visibility your auditors can follow.

Data residency

Cloud, on-premise or co-located, so data sits where your obligations require.

Regulation-ready data

Structured for MiCA, FATF Travel Rule and BSA/AML/KYC, with retention you set.

Deliver on your timeline

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

Scoping call

We map your use case, the chains involved and the systems the data lands in, then give you a delivery estimate.

Technical deep-dive

Our engineers work with yours to confirm the design and the integration points.

Kickoff and go live

We stand up your integration and validate the data against your systems, ready for your team to build on.

Ongoing support

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

Scoping call

We map your use case, the chains involved and the systems the data lands in, then give you a delivery estimate.

Technical deep-dive

Our engineers work with yours to confirm the design and the integration points.

Kickoff and go live

We stand up your integration and validate the data against your systems, ready for your team to build on.

Ongoing support

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

Book a scoping call

Build AML screening today

Everything your team (or AI agents) need to build a working solution today. Read the guide or copy the prompt below to have your agent help you ship it.

Hand this to your coding agent

Open in Claude Code

I'm building stablecoin AML screening 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/compliance-monitoring

Help me:

1. Set up a Turbo pipeline that streams stablecoin transfers and screens both counterparties against a watchlist
2. Hold the watchlist in a Postgres-backed dynamic table we can update at runtime
3. Write flagged transfers to our database and push each hit to our case management webhook
4. Add a Compose task that verifies a hit with our sanctions provider and attests the decision onchain

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

AML screening

The full guide

AI Skills

For coding agents

MCP

Connect your agent

Ready to screen every flow in real time?

Bring your screening stack to a 30-minute call and leave with a concrete plan.

Talk to our team

Read the guide

Frequently asked questions

What is an onchain data pipeline for compliance monitoring?

A pipeline that decodes transfer events from public chains, screens both counterparties against a watchlist, and writes an attested record of every decision, instead of a periodic manual review.

Which lists and vendors can we screen against?

Anything you can write to a table: OFAC and SDN lists, vendor feeds such as Chainalysis, TRM, or Elliptic, and your own internal blocklists can all populate the same watchlist.

How do we prove a decision to a regulator?

Every verification runs as a traced Compose task, and the decision is recorded onchain, so "how did you decide" is a record, not a reconstruction.

Is this tied to a particular chain or token standard?

No. The screening logic reads transfer events, so it works the same on any chain Goldsky supports and against any token standard, including standards that emit issuer policy events natively.

Where does our compliance record live, and who owns it?

You own it, in a database you choose. Flagged transfers and attestations land in Postgres, MySQL, or ClickHouse, and the watchlist is a Postgres table hosted by you or by us.

The Fintech Guide to Stablecoin Data Infrastructure Proof of reserves and treasury Securities compliance

Goldsky for Fintech Compose