Integrate with Trestly
These guides are for teams that want to support kUSDT or send their users to the bridge. Each one is short and links to the reference pages for the details.
What you can integrate
Section titled “What you can integrate”| You want to | Guide | Reference |
|---|---|---|
| Show and send kUSDT in a wallet | Wallets | KCC-20 tokens, The kusdt-tx CLI |
| Let your site’s users bridge USDT, swap or redeem | Websites and apps | The web app, Wallet provider |
| Take kUSDT deposits, pay kUSDT out, hold it for users | Exchanges and custodians | Finality, Reserves |
| Quote and build KAS⇄kUSDT swaps through KasPool | Websites and apps | KasPool, Swap |
| Read the bridge’s state and its stop signal | Reading the bridge’s state | Coordinator API, The monitor |
| Tell your users what can go wrong | Risks to tell your users | Known limits, Threat model |
| Use the name and the logo | Brand and media kit |
The parts, in one line each
Section titled “The parts, in one line each”- kUSDT is a KCC-20 token on Kaspa Layer 1, with 6 decimals. Its covenant ID is its identity: any token can call itself “kUSDT”. See The kUSDT token family.
- The vaults, one on Ethereum and one on BNB Chain, hold the USDT. A deposit there is minted as kUSDT on Kaspa; a kUSDT burn on Kaspa is paid out by a vault. See Deposits and mints and Redemptions and releases.
- KasPool is the KAS⇄kUSDT pool on Kaspa L1. See KasPool.
- The coordinator’s API is a public, read-mostly JSON API. Nothing in it moves funds. See Coordinator API.
- The monitor watches every chain and pauses the bridge on any alarm. Its public status includes a signal for integrators. See The monitor.
- kUSDT Wallet is the browser extension. It injects
window.kusdtfor sites. See The wallet.
Where things are today
Section titled “Where things are today”| Item | Where |
|---|---|
| Networks | Kaspa mainnet, Ethereum (chain ID 1) and BNB Chain (chain ID 56) (Networks) |
| Web app | https://trestly.io, which opens once the launch is verified |
| Coordinator API | The address on Status: Addresses, published once the launch is verified |
| Monitor status | The address on Status: Addresses, with /health, /api/v1/signal and /api/v1/monitor |
| Covenant IDs, the pool, the vaults | Status: Addresses, the API’s GET /status, and the web app’s Bridge status (/network) |
No mainnet address is written into these pages. Don’t copy one into your code from anywhere else: read the IDs and
addresses from GET /status and check them against Status, or make them a setting.
The public testnet ended on 14 November 2026. To try everything before you go to mainnet, run the whole stack on your own machine: Run the simnet flow and Build and test.
Where to ask
Section titled “Where to ask”Ask in the Telegram group t.me/trestly. It is also the security contact: to report a vulnerability, don’t post the details there, say you have one and ask an admin for a private channel (Audit status).