Goldsky

Goldsky for Trading

Catch market abuse while you can still act on it

Tokenized securities trade around the clock. See eligibility, freezes and trading as they happen, and keep a record that answers an examiner the first time they ask.

Talk to our team

Read the guide

Highlights

Identity registrations, freezes, recoveries and pauses in one ledger
Wash trades identified by resolving both sides to their owner
Execution quality measured against a continuous price feed
Alerts carried through to cases and filings, with the record kept

Trusted by leading trading and blockchain teams

Every compliance check is already recorded onchain

The permissioned token standards behind tokenized securities build identity and compliance into the token itself, and every check they perform is recorded onchain. That turns surveillance from a reconstruction exercise into a stream you can act on.

Surveillance that runs in real time

Abuse is flagged as it settles, so your surveillance team can act on an open position while intervention is still possible.

Provable eligibility and freezes

A live compliance ledger plus attested decisions answer the examiner’s question, who was allowed to hold this and why, without reassembling the history by hand.

Compliance data stays yours

Compliance events and identity data live in your own database, inside your boundary, so retention and residency remain under your control.

Transfer compliance and market surveillance

Two halves of the same problem: who is allowed to hold the security, and what they did with it.

Identity and freeze ledger

Identity registrations and removals, address and token freezes, unfreezes, forced recoveries and pause events, all decoded into your own compliance ledger as they happen.

Wash trading by beneficial owner

Both counterparties are resolved to owner identities, and a trade is flagged when there is no change in beneficial ownership, which is what a wash trade actually is.

Best execution monitoring

Join the trade stream to a continuous price feed and flag fills that executed materially outside the spread, which is the raw material for a best-execution report.

One widening net

When an identity graph links a new address to an existing owner, the pipeline picks it up on the next trade. No redeploy or coverage gap.

Attested decisions

Eligibility checks run as tasks that verify against your identity provider and record the outcome in a trusted execution environment, with the full trace saved.

Alert to case to filing

A task enriches each alert, opens a case and, where required, files the regulatory report. Durable execution means a required filing is not dropped because a downstream API blipped.

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 market surveillance 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

I'm building compliance monitoring and market surveillance for a tokenized security 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/securities-compliance

Help me:

1. Set up a Turbo pipeline that decodes ERC-3643 identity, freeze, recovery and pause events into a compliance ledger in our database
2. Set up a second pipeline that resolves both counterparties of each trade to beneficial owner IDs via our identity service
3. Flag trades where both sides share the same beneficial owner, and webhook them to our surveillance system
4. Add a Compose task that enriches an alert, opens a case and attests the decision

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

Market surveillance

The full guide

AI Skills

For coding agents

MCP

Connect your agent

Ready to see abuse as it happens?

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

Talk to our team

Read the guide

Frequently asked questions

What exactly counts as a wash trade here?

A sale with no change in beneficial ownership: the same owner on both sides, usually across two different addresses. That is why the detection resolves addresses to owners first rather than looking at addresses alone.

Why not just check both addresses against a watchlist?

Because that answers a different question. A membership test fires on any trade between two known investors, which floods surveillance with false positives. It tells you the addresses are known, not that they share an owner. Membership checks are still useful as a cheap pre-filter to cut volume before the owner lookup.

What do we have to provide?

An identity or KYC resolver endpoint and the ownership graph behind it, a surveillance webhook to receive alerts, and your own database. Goldsky streams and correlates the onchain side; the identity truth stays yours.

Does this cover spoofing as well?

Not out of the box. Wash trading and best-execution monitoring are covered. Spoofing is something broker-dealers surveil for, but it is not part of this pattern, so treat it as additional work rather than something already included.

What will our security and procurement teams need from you?

Goldsky is SOC 2 Type II audited, with dedicated infrastructure options, role-based access controls and audit logging. We provide the report, DPAs and architecture documentation your reviewers ask for. Your identity graph is queried from infrastructure you control and is never copied into Goldsky, which is usually the first question a securities compliance review asks.

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

You own it, in a database you choose. The compliance ledger, every alert and every attested decision land in a database you choose, under schemas you control, with your own retention policy. Your identity graph stays where it is and is queried in place, so the record you would produce for an examiner is one you hold rather than one you request.