Skip to main content
Goldsky for Trading

The data infrastructure behind tokenized real-world assets

Tokenization data infrastructure for real-world assets is the layer that keeps a holder register, a price feed, and corporate-actions logic in sync with onchain transfers, rather than a periodic reconciliation job. Goldsky decodes transfer and identity events, including ERC-3643, into a register that nets correctly per holder, rolls trade data into OHLC and VWAP pricing, and pays pro-rata dividends from a gas-sponsored wallet. Everything lands in your own Postgres or ClickHouse, so transfer-agent reconciliation is a query, not a cycle.

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.

Where Goldsky's data layer sits

Table 1. Where Goldsky's data layer sits relative to issuance platforms and oracle networks.
LayerExample providersWhat they ownWhat Goldsky adds
Issuance & complianceSecuritize, Ondo, Centrifuge, TokenyToken issuance, transfer restrictions, investor onboardingReads the same transfer/identity events these platforms emit and turns them into your own queryable holder registry
Oracle / interoperabilityChainlink, QuantPrice feeds and cross-chain messagingIndexes the underlying trade and transfer data those feeds are computed from, in a database you own
Data infrastructureGoldskyHolder registry, pricing rollups, dividend automation, transfer-agent reconciliation—

$19.9B

tokenized-equity market, measured directly from the contracts

95.3M

Robinhood token transfers read end to end, zero freezes or forced transfers

84%

weekend price called Monday's opening direction, across 443 ticker-weekends

Sourced from The Year Tokenization Went Mainstream

Built for regulated environments

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

AICPA SOC 2 Type II compliance seal

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.

1

Scoping call

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

2

Technical deep-dive

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

3

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.

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

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.

Ready to see your register in real time?

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

Frequently asked questions

The layer beneath issuance platforms: a holder registry, a pricing feed, and corporate-actions logic built from onchain transfer and identity events, landing in a database you own rather than a vendor dashboard.
Your transfer agent. 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 surfaces the same morning.
Yes: 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.
For ERC-3643 tokens, Goldsky decodes the contract's own logs rather than a plain transfers dataset, capturing identity events so the registry links holders to verified identities.
You own it, in a database you choose. The holder registry and every dividend batch sit in your own Postgres or ClickHouse, with a full trace behind each payment.

© Endless Sky Inc. All rights reserved.

PrivacyTermsSecurity

System status