Skip to main content

​
Supported Assets

Tonhub displays and supports the following types of assets: native TON, tokens (TON), as well as SOL and tokens on the Solana network. Below is a description of how they are displayed, where the data comes from, and what limitations exist.

​
Tokens on the TON network

Each token has:
  • Master contract — defines the token type (symbol, name, decimal places).
  • Token wallet — a contract at the user’s address that stores the balance of this token.

​
How Tonhub displays tokens

The application gets the list of tokens and balances by TON address from the Tonhub backend: Hints Full request (/hints/full/{address}). The response contains a list of token wallets with balances and metadata. Users cannot manually “add” or “remove” a token in terms of changing the server list: only tokens for which your address has a token wallet and which the API returned are displayed. Hiding or marking as “spam” affects display in the application (see below).
For each token, the following is displayed:
  • Name and symbol (name, symbol) — from master contract metadata (cache/Tonhub API).
  • Amount (balance) — accounting for decimals.
  • Icon (image) — if provided by the metadata API.

​
Gasless for tokens

For some tokens (e.g., USDT) with W5 wallet, fee payment in the token itself (gasless) is available. The application gets the list of such tokens from the gasless config on the server. More details — in the Receiving and Sending section.

​
Spam and risks: marking tokens and addresses

​
Backend verification

For tokens, the API can return a verification field (e.g., whitelist / blacklist / none) and an isScam flag for the wallet. This is used for visual highlighting of suspicious tokens or addresses (e.g., “SCAM” marking in the interface for token or badge on avatar during transfer).

​
Manual list (deny list)

Users can add addresses to a “manual spam filter” (deny list) in settings. Such addresses are displayed with a spam marking (badge on avatar) when sending, but sending to them is not blocked — the user can confirm the transfer. That is, protection from phishing and scammers is in the form of a warning, not a hard ban.

​
TON only

Spam filter logic (automatic marking by amount/comment, known spam wallets, deny list) in Tonhub applies only to TON and tokens. Solana transactions (SOL and SPL tokens) are not marked as spam and do not go through this filter.

​
Solana: SOL and tokens

SOL — native Solana balance; displayed in the Solana wallet section. Data is requested via RPC (balance, history).
Tokens - the application gets the list of tokens by user’s Solana address from the Tonhub backend: POST to /solana/tokens/mainnet (or devnet) with body { address }. The response contains an array of tokens with fields: address (mint), symbol, name, decimals, logoURI, amount (balance), etc.
Who decides which tokens to show: the backend. The application displays only what the API returns; there is no fixed list of “supported” tokens in the application code. There are no display restrictions and by default Tonhub will display all tokens.
Spam filter and deny list for Solana are not used in Tonhub — small or suspicious Solana transactions are not marked as spam.

​
Asset list management

The wallet has two sections for displaying tokens:
  • Savings accounts — section contains known stablecoins and native currencies by default. Editing this section is not available.
  • Tokens — section displays all other TON blockchain tokens. This section supports editing.

​
Editing the Tokens section

The “Hide” action is available on the token card. A hidden token disappears from the main list and moves to a separate “Hidden tokens” block (the block can be collapsed or expanded if needed). The token can be restored directly from this block — the “Show” button on the hidden token card returns it to the main list. The setting is saved locally (synchronized via cloud by jettons-disabled key).
For tokens linked to a Ledger wallet, a separate list of hidden tokens operates with similar logic: hiding moves the token to the hidden block, the “Show” button returns it to the main list.
The function of hiding and displaying individual tokens in SOL is not supported — all tokens from the API response are displayed.
The order of tokens is determined automatically: verification (verified), balance presence, exchange rate, etc. are taken into account. There is no “pin” or “favorite” function to move a selected token to the top of the list in the application.