This article explains how STON.fi uses interface labels to help users better understand non-standard tokens without compromising decentralization. Readers will learn what labels like Fake, Honeypot, Taxable, and Suspicious, and DMCA Notice mean, how labeled tokens are handled in the interface, and why contract-address-only access gives users clearer context before interaction.
Whу does token labeling matter?
DeFi is open by design. That is one of its strengths, and it also means users may encounter tokens with very different properties, behaviors, and presentation styles.
Anyone can deploy a token. As a result, the blockchain can contain established community assets, experimental tokens, tokens with unusual contract mechanics, assets that imitate familiar brands or tickers, and tokens that are the subject of legal complaints — all at the same time. The challenge for users is whether they can understand what they are interacting with before they click.
This is where interface-level labeling matters.
STON.fi does not decide what should or should not exist onchain. Instead, its interface uses labels to mark tokens with specific characteristics that users should understand before interacting with them. These labels are based on observable signals and documented inputs — including user complaints, manual monitoring, honeypot alerts, and official legal requests — and are designed to give users clearer context.
What kinds of tokens are labeled in the STON.fi interface
STON.fi labels tokens that have characteristics users should be aware of before interacting with them.
- Fake tokens. Such tokens are designed to imitate a popular token or well-known asset in a way that can mislead users. This usually involves a copied or lookalike name, ticker, or visual identity intended to make the token appear to be something like USDT, BTC, TON, or another recognizable asset. Such tokens try to make users believe they are interacting with the real asset when they are not.
- Honeypot tokens. These tokens can usually be bought, but cannot be sold normally afterward. This is one of the clearest scam patterns in DeFi.
- Taxable tokens. This label is applied when the token contract contains an extra swap-fee mechanism.
- Suspicious tokens. Tokens that raise concerns and require additional attention, but do not fall into a stricter category. This label is applied automatically, including cases where a token uses a brand, character, or celebrity identity but there is no official complaint against it.
- DMCA Notice tokens. Tokens associated with an intellectual property complaint from a rights holder or their authorized representative. Such tokens do not necessarily try to impersonate a popular token itself, they may represent a separate contract that users can intentionally interact with. That is why they still remain swappable in the interface while carrying a clear label for user awareness.
| Read more on tax tokens here: Tax tokens on TON: what they are and why they aren’t on STON.fi |
What happens when STON.fi labels a token?
Tokens in all labeled categories can only be found by entering their smart contract address manually. This adds deliberate friction and helps ensure that interaction with such tokens is a conscious decision rather than an accidental one.
Tokens from some labeled categories are not available for interaction in the STON.fi dApp interface. This includes Fake and Honeypot tokens. These assets cannot be swapped through the STON.fi dApp, even if the contract address is entered manually.
At the same time, this does not mean the token disappears from the blockchain. A labeled token still exists onchain and may be accessible through other interfaces or through direct smart contract interaction.
Taxable tokens are in a special-risk category. STON.fi provides limited support for taxable tokens when they can be handled within strict technical safeguards. A taxable token may be supported only as the asset the user directly sends or receives, not as a middle step in a route. Some of these assets may be searched by their names and be swapped in the STON.fi dApp. If a token’s transfer tax is above 10%, swaps involving that token are not supported.
Other flagged categories, such as Suspicious and DMCA Notice, may still be swapped in the STON.fi dApp. In these cases, the label functions as a warning and a context marker: it tells users that the token has some specific characteristics.
Token labels in the STON.fi interface
To make token characteristics more transparent, STON.fi uses clear labels in the interface.
Here is the core flag system:
| Flag | What it means | Why it is labeled | Available for search by name? | Can be swapped in STON.fi dApp? |
| Fake | The token imitates a known asset, project, or brand | Helps prevent confusion with legitimate tokens and misleading branding | No | No |
| Honeypot | The token can be bought but cannot be sold normally | Protects users from a classic scam pattern | No | No |
| Taxable | The token contract charges additional swap fees | Warns users about hidden or non-obvious costs | Yes, if aligns with the interface policy | Yes, if aligns with the interface policy and the token’s transfer tax does not exceed 10% |
| Suspicious | The token raises concerns but is not fully blacklisted in the interface | Warns users about assets that may misuse recognizable identities, branding, or other misleading signals without a confirmed hard restriction case | No | Yes |
| DMCA Notice | The token is subject to an intellectual property complaint | Marks assets using protected names, logos, or copyrighted material without authorization | No | Yes |
Where the labels come from
STON.fi labels rely on specific signal sources.
These include:
- submitted user complaints,
- manual token monitoring,
- automatic honeypot alerts,
- and legal notices from rights holders or their authorized representatives.
Flagged cases are reviewed, recorded, and then the appropriate label appears in the app interface.
What users should do before interacting with a labeled token
If you choose to interact with a token that is only accessible by contract address, slow down. A few checks matter:
- verify the contract address from an official source,
- do not rely on the token name or logo alone,
- check whether the project has real official channels and links,
- understand whether the token includes special swap mechanics or extra fees,
- treat manual address entry as a signal to review the asset more carefully.
The rule is simple: DYOR before proceeding.
Final thoughts
STON.fi’s approach is straightforward: keep the protocol open and decentralized, and make the interface more transparent for the people using it.
These token labels are interface-level context markers based on specific inputs and observable criteria. Their purpose is to help users understand what they are dealing with before interaction.
