Skip to content
LEARN DEVELOPER NODE OPERATOR GRANTS

Integrate with Exchanges

Introduction

This guide shows how to add DUSK to an Exchange by providing all the relevant information. In the first section we outline general details regarding the upcoming mainnet launch and token migration. We will then look into what are the available libraries and APIs to access and interact with the blockchan, as well as providing links to all the relevant resources, and addressing some common requests.

Token Migration

Users will be able to migrate from ERC-20 DUSK and BEP-20 DUSK to native DUSK by using the migration contract to burn their tokens and release an equivalent amount of DUSK on the Dusk mainnet to the specified target address.

More information about the Mainnet migration can be found here.

Current token contracts are:

The migration contract has been audited and will be accessible via the Dusk Wallet.

Connect to Dusk

To access the blockchain you can either:

  • Spin up a node (query data, submit transactions, provide APIs)
  • Use Dusk APIs (events system, HTTP …)
  • Use RPC providers

Spin up a node

You can access the blockchain and submit transactions by running a Dusk node.

The installation instructions can be found here, and requirements are different depending on if the node is a Provisioner or an archive node.

Use Dusk APIs

Dusk exposes the following APIs:

  • RUES: Provides an event system for streamlining information from the network.
  • HTTP API (Work in Progress)

Use RPC providers

You can rely on the RPC infrastructure hosted by the community, or run an archive node yourself.

Token Deposits and Withdrawals

You can subscribe via websocket to deposit and withdrawal events using RUES.

In most cases, 1 block confirmation is sufficient for finality. The only exception to the 1 block finality is when the network is in a rolling finality state, in which up to 5 additional blocks may be required to achieve finality.

Construct, sign and decode transactions

The W3sper SDK provides address generation, transaction building, signing, and decoding functionalities. It can operate completely offline, without the need for an online wallet or node. The W3sper SDK leverages wallet-core to facilitate offline transaction processing and signing, producing both the transaction hash and signed transaction outputs. The library for transaction serialization and decoding is called dusk-bytes.

Cold Storage Method

The multisig contract contains an example of how to do multi-signature transfers, where only N out of M keys must sign a message to transfer DUSK to another account.

Users get to create accounts owned by multiple different BLS keys, where any important action must be signed (agreed upon) by some configurable portion of those keys.

Dusk is fully compliant with key global regulatory frameworks, providing robust adherence to financial and data protection standards:

  • Market Abuse Regulations (MAR)
  • Data Protection Regulations (GDPR)
  • Anti-Money Laundering Directive (AMLD5)
  • MiCA (Markets in Crypto-Assets Regulation)
  • TFR (Transfer of Funds Regulation)

The protocol’s dual-model (Moonlight and Phoenix) offers unmatched flexibility while maintaining compliance.

Moonlight is designed specifically for full transaction transparency, making it ideal for integration with exchanges and ensuring that:

  • CASPs can easily meet compliance obligations under AMLD5, MiCA, and TFR.
  • There is full support for KYC, transaction monitoring, and reporting requirements without any legal or technical barriers.

To reinforce confidence in compliance, there is a comprehensive and detailed legal opinion confirming adherence to applicable laws and regulations. This document is available for review upon request.

Resources

Libraries

Token details

Audits

Q&As

Status of Hardware Wallet Support

Hardware Wallet integration is a work in progress.

Cross-Chain Fees

For token migrations, the Dusk team will cover the fees on the Dusk mainnet. Users are responsible for the fees of Binance Smart Chain and Ethereum.