KuCoin Lists EVAA Token for USDT Trading
KuCoin lists EVAA Protocol for EVAA/USDT trading on October 5, adding centralized exchange access to the TON-based DeFi lending platform.

KuCoin has opened spot trading for EVAA Protocol’s native token, adding another centralized exchange venue for the TON-based lending project. According to KuCoin’s official listing announcement, EVAA/USDT trading began at 10:00 UTC on October 5 following a one-hour call auction. The exchange currently accepts EVAA deposits through BSC-BEP20, even though the underlying EVAA lending protocol operates natively on TON and integrates directly with Telegram.
Withdrawals are scheduled to open at 10:00 UTC on October 6. KuCoin also enabled EVAA/USDT across several automated trading services when the spot market opened, including Spot Grid, Infinity Grid, DCA, Smart Rebalance and other trading bots. The rollout expands trading and distribution infrastructure for the EVAA token, but it does not represent a new deployment of the EVAA lending protocol or direct access to its TON-based credit markets.
EVAA Trading Uses BSC While Lending Runs on TON
EVAA describes itself as a Telegram-native decentralized liquidity protocol built on TON. Users can supply assets to liquidity pools, earn variable interest generated by borrowing demand and use supported collateral to take overcollateralized loans. Its official documentation says these positions are managed through smart contracts on TON, with access available through both a web application and a Telegram Mini App. The lending application and the exchange-listed token should therefore be treated as separate layers of the EVAA ecosystem.
KuCoin’s network choice makes that distinction especially visible. The exchange currently specifies BSC-BEP20 for EVAA deposits rather than a native TON deposit route. Moving an EVAA token into KuCoin through BNB Smart Chain does not move lending collateral into EVAA’s TON smart contracts or create a borrowing position. Users interacting with the lending protocol still operate through its TON-based infrastructure.
The listing follows a familiar exchange rollout model in which deposits open first, an auction establishes initial price discovery and continuous spot trading follows. KuCoin used a similar staged structure when it recently [listed DIAM alongside an exchange launch campaign], although the economics and underlying applications of the two tokens are unrelated. A new centralized listing can increase market access and potential turnover without demonstrating additional protocol deposits, borrowers or lending liquidity.
Exchange Liquidity and Protocol Adoption Remain Separate
That distinction matters particularly for lending protocols. EVAA’s economic activity ultimately depends on supplied assets, borrowing demand, collateral quality, utilization and liquidation mechanisms rather than token trading alone. Higher EVAA/USDT turnover on KuCoin would not necessarily indicate greater lending usage on TON. Lending markets also carry dependencies such as collateral pricing and oracle infrastructure, an issue relevant across DeFi and examined separately in [the risks created by oracle dependencies in onchain lending markets].
EVAA’s own website reports more than 300,000 unique wallets, over $1.4 billion in transaction volume and peak deposits exceeding $118 million. Those are project-reported historical metrics rather than measurements of activity generated by the KuCoin listing. The exchange launch should therefore be assessed primarily as an expansion of EVAA token distribution, while protocol adoption requires separate evidence from deposits, loans, users and recurring activity on TON.
For now, the operational change is straightforward: EVAA/USDT is live on KuCoin, deposits are supported through BSC-BEP20 and withdrawals are due to begin on October 6. The listing gives traders another venue for EVAA exposure, while the protocol’s lending activity remains anchored to its separate TON and Telegram infrastructure.
This article is for information only and is not investment advice. We report under our Editorial Policy; to flag an error, see our Corrections Policy.


