Goldsky

Goldsky for Trading

Know who holds your tokenized security right now

A holder register that stays current as of the latest block, round-the-clock pricing built from every trade, and pro-rata dividends paid straight from the register.

Talk to our team

Read the guide

Highlights

A holder register current as of the latest block, per token
Round-the-clock pricing built from every trade on the venue
Pro-rata dividends paid automatically, with a trace for every payment
Transfer agent reconciliation you can run whenever you want

Trusted by leading trading and blockchain teams

Registrar, market data and corporate actions, onchain

Tokenized stocks and ETFs now trade 24/7 and settle into self-custodied wallets. The obligations of a registrar, a market data provider and a corporate-actions agent did not go away, they just moved onchain.

A real-time cap table

Balances net correctly per holder as of the latest block, so a holder enquiry or a transfer agent query is answered from the current register on the day it is asked.

Pricing that runs around the clock

The trade feed and its rollups run continuously, so your team has a reference series to evidence best execution on a trade that happened at three in the morning.

Auditable corporate actions

Dividends and splits execute as code, with a durable trace for every payment, so what was paid and to whom is a record rather than a spreadsheet.

Registry, market data and corporate actions

Registry, market data and corporate actions, each landing in infrastructure you own.

Live holder registry

Every transfer becomes a credit and a matching debit, so balances net correctly per holder and token and the current holder set is one query.

Round-the-clock price feed

Index trades from the venue and roll them into OHLC and VWAP, in ClickHouse for time-series queries or as a live last price maintained in Postgres.

Automated dividends

A task reads the registry at the record-date block, computes each holder’s pro-rata amount and pays in a stablecoin from a gas-sponsored wallet.

Splits and other actions

Ratio math and multi-step distributions, including splits, reverse splits and mergers, follow the corporate-actions distributor pattern rather than bespoke scripts.

Transfer agent reconciliation

Because the registry sits in your own database, reconciling onchain holders against the books of record is a query, and breaks surface immediately in either direction.

Chain agnostic

The same pattern covers Robinhood Chain, ERC-3643 securities on Ethereum or Polygon, and RWA chains such as Plume and Mantra.

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 a holder registry 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 the data layer for a tokenized equity 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/tokenized-equities

Help me:

1. Build a live holder registry from token transfers, emitting a credit and a debit per transfer so balances net correctly
2. Maintain those balances incrementally with the Postgres aggregate sink
3. Index trades into an OHLC and VWAP price feed in ClickHouse
4. Add a Compose task that reads holders at a record-date block and pays pro-rata dividends in a stablecoin

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

Holder registry

The full guide

AI Skills

For coding agents

MCP

Connect your agent

Ready to see your register in real time?

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

Talk to our team

Read the guide

Frequently asked questions

Who is the system of record, you or our transfer agent?

Your transfer agent, and your registrar obligations do not move. What changes is that you can check the onchain holder set against their books whenever you want instead of once a day, so a break is something you catch the same morning rather than something you discover during a reconciliation cycle. The registry lives in your database, not ours.

Is there anything to watch out for with dividends?

Yes, and it is important: pay on the network the token actually lives on. Paying on a different network sends dividends to look-alike addresses that never held the security. The guide calls this out explicitly.

What about identity for permissioned securities?

For ERC-3643 tokens you decode the contract’s own logs rather than a plain transfers dataset, and capture identity events too, so the registry links holders to verified identities instead of bare addresses.

Should the registry live in a subgraph or a pipeline?

Either. A pipeline into your own database suits reconciliation and analytics; a subgraph is often cleaner when you mainly query per holder, because you get a GraphQL API for statements and positions without running another service.

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. Holder identity data stays in your systems, since the registry is built from public transfer events and joined to identity on your side.

Where does the register live, and who owns it?

You own it, in a database you choose. The holder registry and every dividend batch you have paid sit in your own Postgres or ClickHouse under schemas you control, with the full trace behind each payment. A corporate action you executed last year stays auditable out of your own records.