Goldsky

Trade surveillance data for tokenized securities

For venues and issuers of tokenized securities, Goldsky records identity and trading events in your database and flags possible wash trades for your surveillance team.

Talk to our team

Read the guide

At a glance

Registrations and freezes in one table
Possible wash trades sent for review
Off-market fills marked for best execution
Owners looked up in your identity system

Trusted by trading venues, issuers and blockchain teams

Answer who held the security, and when

Tokenized securities built on the ERC-3643 standard record identity checks and freezes on the blockchain. Goldsky turns those records, and the trades, into tables your compliance team can query.

Trades checked as they come in
Each trade is checked against your identity service as it streams in, and possible wash trades go to your surveillance system.
Eligibility in one query
Registrations, freezes and recoveries go into one table, so the question of who was allowed to hold the security on a given date is a single query.
Records in your systems
Compliance events are written to your database, alerts go to your surveillance system, and your identity data is read where it already lives.

Tokenized securities trade surveillance and compliance records

Goldsky keeps track of who may hold the security and how it trades. Your compliance team reviews the flags and makes the decisions.

Compliance ledger

Investor registrations and removals, freezes, forced recoveries and trading pauses are written to a Postgres table.

Wash trade flags

Both wallets in a trade are looked up in your identity service. If they belong to the same beneficial owner, the trade goes to surveillance.

Best-execution checks

Each fill is compared with a market price feed. Fills well outside the spread are marked for your best-execution report.

Ownership updates

Because the identity service is asked on each trade, linking a new wallet to an owner takes effect on the next trade.

Eligibility checks

When a new holder needs checking, a Goldsky Compose task asks your identity provider and records the answer.

Cases

A Compose task adds context to each alert and opens a case in your surveillance system, retrying if the call fails.

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 trade surveillance for tokenized securities today

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

Open in Claude Code

I'm building compliance monitoring and trade 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.

Catch wash trades in your tokenized security

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 happens to a possible wash trade?

Goldsky sends it to your surveillance system with the beneficial owner of each wallet attached. Your compliance team reviews it there.

How are wash trades detected?

A wash trade is one where beneficial ownership doesn’t change. Goldsky asks your identity service who owns each wallet in a trade, and if it’s the same owner on both sides, the trade is flagged.

What do we need to provide?

An identity or KYC service that maps wallets to owners, a surveillance system that can receive alerts, and a database.

Does Goldsky detect spoofing?

No. The securities compliance guide covers wash trading and best execution only.

Does Goldsky have a SOC 2 report?

Goldsky maintains SOC 2 Type II compliance, with the report available under NDA.