Goldsky

Know who holds your tokenized asset

Goldsky updates a holder register for your tokenized stock or other real-world asset after every transfer on the blockchain, keeps it in your database, and can pay dividends to the holders on it.

Talk to our team

Read the guide

At a glance

Holders and balances, updated with each transfer
Prices built from trades on the blockchain
Pro-rata dividends paid in a stablecoin
Checked against your transfer agent with a query

Trusted by exchanges, brokers and blockchain teams

Know who holds your token

Goldsky builds the register and the price series from your token’s transfers and trades, and runs dividend payments from the register.

Current holder data
The register reflects the latest transactions on the blockchain, so questions about who holds what don’t have to wait for an overnight file.
Breaks against your books
Compare holders on the blockchain with your transfer agent’s records whenever you like. An address with no matching book entry shows up in the result.
A record of each payout
Each dividend run is logged, and the batch is written to your ledger, so you can show what was paid and to whom.

Tokenized asset registry, pricing and dividends

The register and price data go to your database, where your systems and reports can read them.

Holder register

Each transfer is recorded as a credit to the receiver and a debit to the sender, so every holder has a running balance.

Price series

Trades from the venue where the token trades are rolled into open, high, low and close prices and volume-weighted averages.

Dividends

A Goldsky Compose task reads holders as of the record date, works out each pro-rata amount and pays it in a stablecoin.

Splits and mergers

Goldsky’s corporate actions guide covers the ratio math and multi-step distributions for splits, reverse splits and mergers.

Transfer agent reconciliation

With the register in your database, matching it against your books of record is a query.

Permissioned securities

For ERC-3643 tokens, which only approved investors can hold, Goldsky also records identity events and links each holder to a verified identity.

Where Goldsky sits in the tokenization stack

Table 1. Where Goldsky’s data layer sits relative to issuance platforms and oracle networks.
Layer	Example providers	What they own	What Goldsky adds
Issuance and compliance	Securitize, Ondo, Centrifuge, Tokeny	Token issuance, transfer restrictions and investor onboarding	Reads the transfer and identity events these platforms emit and turns them into a holder registry you can query
Oracles and interoperability	Chainlink, Quant	Price feeds and cross-chain messaging	Collects the trades and transfers behind those feeds into a database you own
Data infrastructure	Goldsky	Holder registry, price series, dividend payments and transfer agent reconciliation	Not applicable

tokenized equity market, measured directly from the contracts: $19.9B
Robinhood token transfers read end to end, with zero freezes or forced transfers: 95.3M
of weekend prices called Monday's opening direction, across 443 ticker-weekends: 84%

Source: The Year Tokenization Went Mainstream

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 a tokenized asset holder registry today

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

Open in Claude Code

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.

See your holder register as it changes

Bring your instrument and the venues it trades on to a 30-minute call and leave with a concrete plan.

Talk to our team

Read the guide

Frequently asked questions

Does Goldsky issue tokens?

No. Your issuance platform creates the token and enforces its transfer rules. Goldsky reads what happens to the token on the blockchain and builds the register, prices and dividend runs from that.

Can we compare the register with our transfer agent’s records?

Yes. The holder list is in your database, so your team can match it against the transfer agent’s records with a query.

Where does the register live?

In your database, such as Postgres. Goldsky can also host it and serve it to your systems through an API.

What about permissioned securities?

For ERC-3643 tokens, Goldsky reads the contract’s identity events as well as its transfers, so each holder in the register is tied to a verified identity.

Which network should dividends be paid on?

The one the token is on. Paying on a different network sends money to addresses that look the same but never held the security.

Report: The Year Tokenization Went Mainstream Securities compliance Goldsky for fintech

Subgraphs Compose