DeDust: TON swaps, pool fees and liquidity exit mechanics

DeDust is a TON exchange built around token swaps, liquidity pools and a router that can use other TON trading protocols. Its own protocol pools and an aggregated route are distinct execution sources. The official exchange, its identical app.dedust.io mirror and its Telegram Mini App are access points to the same service.[1]

Router defaults allow up to four parallel routes with two steps each. STON.fi v1, STON.fi v2 and TONCO are listed as enabled liquidity sources; memepad sources are disabled by default. Users can change individual sources and apply minimum-liquidity, volatility and minimum-savings filters. A more complicated route may improve the quote while increasing network costs and execution complexity.[4]

TON routes are not atomic: one step may finish while a later step fails. For an A-to-B-to-C conversion, the wallet can end up holding B rather than the original A or intended C. That intermediate holding remains the user’s exposure and may need a separate swap. The initial quote should not be read as a promise that every leg will finish together.[4]

Each pool used by a route applies its own fee to the amount passing through it; the quote reflects those deductions. The published split sends 80% of trading fees to liquidity providers and 20% to the protocol. There is no universal DeDust default applicable to every pool or third-party route.[7]

Illustratively, 1,000 units entering one pool at a 0.25% trading fee incur 2.50 units of pool charges: 2.00 for LPs and 0.50 for the protocol under that split. This assumes the stated input-fee basis and excludes token tax, extra creator charges, other route legs, network costs and price movement.[7]

TON’s official documentation identifies Gram as its native currency following Toncoin’s renaming. This distinguishes the coin’s current name from the blockchain’s name. A historical ticker in a guide should not be assumed to identify an unrelated asset; the contract and signing screen remain important when identifying what is actually transferred.[34]

The default swap slippage is 1%, with custom values from 0.01% to 50%. Separately, the interface restricts trades whose estimated USD value difference exceeds 15% unless Expert mode is enabled. Expert mode also removes the ordinary confirmation prompt. Raising either tolerance or permissions changes the loss a user can accept; it does not improve the underlying market price.[6]

Deposit and withdrawal slippage are configured separately, with a 1% default described for each. Classic and stable-swap deposits produce LP tokens needed for redemption; CPMM v2 records the position directly in the contract. Review the pool family before moving a receipt token or assuming that an existing position can be transferred to another wallet.[9]

Permanent locking is an optional CPMM v2 deposit action with no expiry, unlock or partial release. Once signed, neither the provider nor the DeDust team can redeem that locked liquidity. Fees and boost rewards remain claimable, but token-price exposure continues with no ordinary exit. The guide requires withdrawing and redepositing an existing unlocked position if the owner later wants to lock it.[12]

Withdrawing CPMM v2 principal does not collect or forfeit its separately accrued trading fees. Boost accrual stops when liquidity leaves, while already earned rewards remain claimable. Classic and stable-swap fees instead return inside the redeemed position. These distinctions matter when reconciling the wallet receipt with the total value shown before exit.[10]

The developer guide describes swaps through asset vaults and pool contracts: one vault receives the input, the pool computes the exchange and another vault sends the output. Wallet self-custody therefore should not be interpreted as assets never entering contracts. The documented architecture explains the transaction path; it is not a finding that the deployed code is free of defects.[32]

The safety guide stresses offline recovery material, official wallet software and checking links before connecting. A lost recovery phrase cannot be replaced by a DeDust support password reset. Protecting the signing device and checking the transaction remain separate responsibilities: retaining a backup does not make a transaction to the wrong contract reversible.[27]

DeDust’s token selector distinguishes verified contracts from manually imported assets. Verification concerns identity, not investment quality or the creators’ future conduct. A manually imported token can have a familiar name and hidden transfer behaviour. The contract address is therefore essential, especially when two assets use the same ticker or logo.[13]

The protocol-level swap guide explicitly requires checking that the relevant pool and vault are deployed before sending assets. It warns that transfers to inactive contracts can be irretrievable. Its older examples use SCALE and TON names, so developers should verify present contract identities and readiness rather than copying a demonstration amount or address as a current trading instruction.[32]

The June 2024 terms require legal age and capacity, local-law compliance and territorial restrictions. Prohibited jurisdictions include Belarus, Cuba, Iran, North Korea, Syria and others listed in the agreement. They also prohibit location masking by restricted residents or nationals and US persons. A working wallet connection does not establish eligibility.[28]

Token verification is a separate listing process. Anyone may request it, but review has no promised deadline. Verification can make the contract searchable, surface its pools and include it in routing. These visibility decisions do not amount to customer identity verification or a financial-service permission for the platform.[25]

DeDust says it has no private support service: help occurs openly in the community chats linked from its official guide, and staff do not contact users first. The guide identifies administrator titles as a check on community moderators. A private message offering recovery is inconsistent with that published support model.[1]

The terms list [email protected] for questions about the agreement. They also say the operator cannot cancel or modify blockchain interactions.[28]

No exchange-specific authorisation, statutory compensation scheme or scoped private insurance policy was established from the reviewed documents. The contractual description of a decentralised service does not establish regulatory permission.[28]

The terms define a generic ecosystem operator maintained by companies without naming a legal corporation. The Scaleton contact domain does not establish incorporation, headquarters or a licensed entity.[28]

DUST was renamed from SCALE on 21 October 2024; the official token page gives the continuing contract address. The naming change explains SCALE references in older terms and SDK examples. It should not be mistaken for a separate exchange or an instruction to send tokens to a new contract.[19]

The official guide identifies x1000 as a separate trading terminal built by the DeDust team, with its own interface and documentation. This profile does not transfer that terminal’s capabilities or conditions to the DeDust exchange.[1]

CPMM v2 arrived on 17 November 2025, when creation of new Classic pools ended in the interface. Existing Classic pools continue to function. The change therefore distinguishes new pool creation from continued access to an older position; it is not evidence that every user’s liquidity was automatically migrated.[8]

Operator

DeDust ecosystem operator; precise legal company not identified

Exchange model

Decentralised

Service scope

TON swaps, multi-DEX routing, liquidity pools and DUST staking.

Client types

Retail clients

Pricing publication

Public pricing

Pricing scope

Pool fees, route steps, network charges and token-contract taxes may all affect the result.

Funding scope

TON wallet assets and native gas; ordinary and permanently locked liquidity positions differ.

Custody and asset handling

User-signed wallet access; assets interact with protocol vaults and pool contracts.

Client eligibility

Territorial restrictions and legal-capacity requirements apply.

Support

Public community chats; no private support service. Contract questions use [email protected].

Authorisation and registration scope

Exchange authorisation not established.

Exchange metadata checked 21 Oct 2026Source 1Source 2Source 7Source 8Source 12Source 19Source 20Source 28Source 32Source 15Source 14

The DUST page describes protocol-fee conversion into the native token for staking distributions. Its initial supply is 21 million and it says minting ownership was revoked. These token mechanics are distinct from a bank balance or compensation reserve: reward funding depends on the stated protocol activity and the token’s market value remains variable.[19]

Boosted CPMM v2 pools distribute additional tokens proportional to the provider’s share, without a separate LP-token staking step. More liquidity divides a fixed incentive budget among more participants, reducing the displayed boost APR. Multiple reward tokens can run concurrently, and earned rewards remain claimable after the campaign ends. Extra incentives do not remove the position’s price-divergence risk.[16]

A newly created token needs at least 50 USDT or $50 worth of GRAM on the quoted side, plus the matching token amount, before DeDust’s interface derives a usable fiat price and permits ordinary swapping. That is a minimum visibility and pricing condition, not evidence of depth for a meaningful order. Wallet applications can apply different display and verification rules.[26]

Portfolio links reveal public holdings and positions more conveniently; they are not private account statements. The inspected guide does not establish a complete downloadable tax report. Reconciliation should preserve the actual token amounts and transaction identifiers rather than treating a changing USD valuation as the original cost or a realised gain.[23]

The advanced-mechanics guide distinguishes a fulfilled swap, which sends funds to the nominated recipient or sender, from a rejected one, which returns funds to the sender. Custom payloads can chain further actions. That flexibility makes transaction content material: connecting to a familiar interface does not justify ignoring an unfamiliar recipient or additional contract operation.[33]