Skip to main content

Token listing due diligence for exchanges

What is token listing due diligence?

Token listing due diligence, also called asset due diligence, is checking a token’s holders, supply, trading volume and links to risky wallets before an exchange lists it, and again while it trades.

Exchanges run it because a token they list is offered to their customers, and the listing committee needs evidence from the chain behind its decision.

Goldsky snapshots every holder’s balance at one block and keeps your risk provider’s verdict with the snapshot it used; working out concentration and volume, and deciding whether to list, stay with your team and your listing committee.

Who runs token listing due diligence?

Regulated crypto exchanges and brokers, and the risk data vendors that review assets for them.

How token listing due diligence works

The diagram follows one token from the listing request, through the holder snapshot and risk scores, to your committee’s decision and the checks rerun while it trades. Your setup may differ.

Your business, step 1: Listing request arrivesAn issuer or your team proposes a token
Goldsky, step 2: ComposeSnapshot holdersBalances at one block, from backfilled transfers
Your business, step 3: Measure supply and volumeSupply, volume and concentration from those rows
Your business, step 4: Screening providerScore linked walletsDeployer and top holders rated
Your business, step 6: Decide on listingYour listing committee approves or declines
Goldsky, step 5: ComposeRecord the verdictKept with the snapshot it used
Your business, step 7: Recheck while it tradesThe same checks rerun after listing
  • Goldsky
  • Your provider

How to run token listing due diligence

A task Goldsky hosts snapshots every holder of the token at one block and records your risk provider’s verdict on the wallets that matter, both kept against the same block. Your team works out supply, volume and concentration from the snapshot.

What you’ll need

  • Goldsky Turbo
  • Goldsky Compose
  • The token’s contract address and the chains it’s on
  • A blockchain risk provider that rates wallets
  • A database for the snapshot, where your team runs its totals
  • A listing committee and the policy it reviews tokens against
  1. Take in the listing request

    The review starts from a specific token, on specific chains, that someone wants to list.

    The issuer or your own team names the token, its contract on each chain and the reason to list it. A contract address taken from an unofficial source can point to a copy of the token, so confirm it with the issuer.

  2. Snapshot every holder at one block

    Handled by Goldsky Compose

    Concentration and supply only make sense measured at one fixed point, so every figure in the review uses the same block.

    Each holder’s balance has to be rebuilt from every transfer of the token up to the chosen block. A snapshot built from a partial history gives wrong balances without any sign that it’s wrong.

    A Compose task can start a one-time Turbo Pipelines job with ctx.turbo, filtered to the token’s transfers up to the review block, then sum each address’s credits and debits from the rows it wrote to the Postgres database behind the Compose app.

    Run pipelines from a task (opens in a new tab)
  3. Measure supply, volume and concentration

    The committee needs a few clear numbers: how much exists, how much trades and how much sits with a handful of wallets.

    Your team totals supply, transfer volume and the share held by the largest holders from the snapshot rows, in your database. Contracts such as exchanges, bridges and the issuer’s own treasury hold large balances for many people, so label them before you call the token concentrated.

  4. Score the deployer and largest holders

    A token whose creator or biggest holders are tied to scams or sanctioned parties carries that risk onto your platform.

    Your risk provider rates the wallet that deployed the contract and the top holders from the snapshot. Send it the same block’s list, so the ratings describe the wallets the committee sees.

  5. Record the verdict with the snapshot it used

    Handled by Goldsky Compose

    Months later, someone may ask why the token was listed, and the answer has to show what was known at the time.

    Each provider answer is kept with the request, the block and the snapshot it was based on. A verdict stored without its block can’t be compared with a later recheck.

    Every ctx.fetch call the task makes to your risk provider is recorded on its run, URL and response included, and the task can save the verdict to a collection next to the snapshot block.

    Make auditable calls with fetch (opens in a new tab)
  6. Decide whether to list the token

    Listing is a business and risk decision that a named committee owns.

    Your listing committee weighs the numbers and the risk verdict against its policy and approves, declines or lists with conditions. Recording the reasons with the evidence is what lets you defend the decision later.

  7. Recheck the token while it trades

    Holders, supply and links to risky wallets change after a listing, and the original review goes stale.

    Your team reruns the same snapshot and scoring on a schedule you set, or when something changes, such as a large mint or a top holder moving funds. Comparing each run with the last shows what changed since the committee approved it.

What you control

Your team
  • Take in the listing request
  • Measure supply, volume and concentration
  • Decide whether to list the token
  • Recheck the token while it trades
Your providers
  • Screening provider

Security and deployment

  • SOC 2 Type IIIndependently audited security controls.
  • Dedicated infrastructureSingle-tenant options for production workloads.
  • Data residencyCloud, on-premises or co-located.

Run token listing due diligence with Goldsky

We’ll map it to your systems and show you what Goldsky runs, so your team builds the product, not the pipelines underneath it.

© Endless Sky Inc. All rights reserved.

PrivacyTermsSecurity

System status