# Token overview (https://docs-i0yym09dy-ton-core-docs.vercel.app/llms/standard/tokens/overview/content.md)



This article compares different kinds of Tokens in TON.

The TON blockchain supports three distinct categories of digital tokens, each designed to serve different purposes within the ecosystem.

* [Fungible tokens](/llms/standard/tokens/jettons/overview/content.md) (Jettons) - this is a web3 way to create new currency on your own
* [Non-Fungible Tokens](/llms/standard/tokens/nft/overview/content.md) (NFTs) - like Jettons, but each token is unique and represents a distinct entity
* [Soul-bound Tokens](/llms/standard/tokens/nft/comparison/content.md) (SBTs) - like NFTs, but not-transferable, bound to a single owner

## Comparison table [#comparison-table]

| Feature              | Jettons           | NFTs                 | SBTs                  |
| -------------------- | ----------------- | -------------------- | --------------------- |
| **Fungibility**      | Fungible          | Non-fungible         | Non-fungible          |
| **Transferability**  | ✅ Transferable.  | ✅ Transferable      | ❌ Non-transferable   |
| **Divisibility**     | ✅ Divisible      | ❌ Indivisible       | ❌ Indivisible        |
| **Primary use case** | Currency, utility | Art, collectibles    | Credentials, identity |
| **Value type**       | Monetary value    | Unique value         | Reputational value    |
| **Ownership model**  | Liquid ownership  | Verifiable ownership | Permanent binding     |
| **Standard**         | TEP-0074          | TEP-0062             | TEP-0085              |

## Token verification [#token-verification]

* A token is marked as "unverified" if it is not included in the [token asset list](https://github.com/tonkeeper/ton-assets).
* A token may be marked as "scam" if it contains misleading metadata or has been reported.

Token verification is managed through the public repository [`tonkeeper / ton-assets`](https://github.com/tonkeeper/ton-assets). This repository contains approved token metadata.

How verification works:

1. Check whether the token address is already listed in the repository.
2. If it is not present, submit a pull request adding its metadata to the appropriate directory.
3. Maintainers review the submission.
4. Once merged, the token status will be updated.