Integration

Hello Canton Network Technical Team,

We are SK Information Technologies Limited (SKIT), UK.

We have already created our asset-backed RUSDT tokens on Ethereum Mainnet (ERC-20), supported by underlying asset documentation, existing ledger references, transaction IDs and asset lock identifiers.

We are currently integrating with Canton Network and require technical guidance on the following:

  1. Existing Token Integration

Can we integrate or represent our existing RUSDT tokens and their underlying asset rights directly within Canton Network, or must we create new Canton-native tokens?

  1. Existing Asset Locks

We already have asset lock identifiers and transaction references. Can these existing locks be recognized or referenced during Canton integration without creating additional locks or duplicate asset claims?

  1. Tokenization and Smart Contracts

What is the recommended step-by-step technical architecture for connecting our existing tokenized assets to Canton through Daml smart contracts, the Canton Token Standard and our existing .NET integration?

  1. Institutional Liquidity Provider

Our ultimate objective is to obtain genuinely spendable Canton Coin (CC), USDC, USDT or another supported cryptocurrency against our independently verified and institutionally accepted underlying assets.

Can Canton Network introduce us to an appropriate institutional liquidity provider, financial institution or settlement participant capable of evaluating our assets and facilitating a funded settlement transaction?

  1. End-to-End Settlement

We require technical guidance covering:

Existing Asset → Verification → Canton Integration → Institutional Asset Acceptance → Funded Settlement → Spendable Cryptocurrency.

Could a Canton technical specialist or ecosystem representative connect with our team for a direct discussion?

We would appreciate an early response.

Thank you.

SK INFORMATION TECHNOLOGIES LIMITED
United Kingdom
Email: info@skinfotech.co.uk
Website: www.skinfotech.co.uk

Hi SKIT team! A few points that may help:

  1. A bridge architecture could connect Ethereum ERC-20 tokens to corresponding Canton tokens. This creates a Canton representation rather than automatically importing the Ethereum contract. ChainSafe documents this approach, but support for RUSDT would need confirmation.

  2. You can reference existing identifiers, but recording them doesn’t automatically validate or enforce those locks. Whether they can be reused needs a technical review, including controls against duplicate claims. CIP-56 supports custom workflows involving external authoritative ledgers.

  3. I would suggest: verify backing and custody → arrange access through a Canton validator → implement the bridge/registry and Daml workflows → connect your .NET backend through the JSON Ledger API → test transfers and settlement. The Token Standard integration guide explains the APIs and recommends generating clients from OpenAPI.

  4. Integration alone doesn’t guarantee funding. A buyer or lender still needs to accept your assets and agree commercial terms. Agree the payout token and network upfront: Circle confirms USDCx on Canton, backed by USDC, but that doesn’t establish acceptance of RUSDT.

  5. Next step: Contact Canton’s team and request a review for your Ethereum integration, existing lock mechanism and settlement design. Include your token contract address, custody arrangements and current .NET architecture