**CF-20** is a format and standard of interchangeable tokens developed by us for the Cellframe Network platform. Tokens of the **CF-20** standard can be used for settlements, exchanges, proof of stake and many other functions within the Cellframe Network. > [!NOTE] Important > For more information about the Cellframe Network you can refer to the [[Architecture Overview]] page Every token in the Cellframe network is based on this standard including CELL, KEL, and other tokens (in the test networks). **CF-20** standard is an analogue of ERC-20, but without smart contracts, which could be entangled later with token. - CELL is a native token in the Backbone network CELL can be used for providing functionality of every service in the [[Cellframe Ecosystem]] ## Functional Technical functionality and properties of the **CF-20** standard is described in the `dap_chain_datum_token.c` file of the [Cellframe SDK](https://gitlab.demlabs.net/cellframe/cellframe-sdk). It is integrated in the very blockchain. All our **CF-20** tokens support functions, almost similar to the same in the ERC-20 standard. Some changeable parameters are created in our tokens as mandatory (`total_supply`, `valid_signs`, `type`, `ticker`, etc) while others are realized using different flags. Flags can significantly alter token properties, such as allowing or restricting fund transfers to/from specific addresses and many more. Let's use the [[Node Command - TOKEN INFO|TOKEN_INFO]] [[5. CLI Node Commands|CLI command]] for acquire some information about CELL token: ```actionscript current state: -->Token name: CELL type: CF20 flags: NONE description: The token description is not set Supply total: 0 Decimals: 18 Auth signs valid: 4 Auth signs total: 8 Signatures public keys: #below there is a list of applied public keys and information about token updatings ... ``` Here is the parameters description: ```actionscript -Token name - ticker (name) of the token -type - type of the token (CF20 by default) -flags - different token properties (<ALL_ALLOWED> by default) -description - token description -Supply total - maximum sum limit of all token emissions (if 0 - there is no limit) -Decimals - number accuration after comma (18 by default) -Auth signs valid - quantity of authorized token signatures required for its emission -Auth signs total - quantity of authorized token signatures -Signatures public keys - public certificates which were used to sign token ``` Most of these fields can be changed using [[Node Command - TOKEN UPDATE|TOKEN_UPDATE]] command. > [!NOTE] Important > Additional information about [[CF-20 Functional Application#Flags|flags]] and used [[Data element (Datum)|datums]] you can find in the **[[CF-20 Functional Application]]** article. ### Bridge Also, **CF-20** standard is used for providing bridge communication among our networks, and between ours and other networks. ![[Pasted image 20241109213123.png]] Official site of the Cellframe Bridge - https://bridge.cellframe.net/ ### Explorer Cellframe Explorer also works with **CF-20** standard. All interactions with **CF-20** tokens can be tracked and seen on the site - https://explorer.cellframe.net/. ![[Pasted image 20241018175208.png]] ### DEX As said previously, all **CF-20** tokens are tradable. Not only using our [[1. DEX Manual|Decentralized Exchange]], but on the external exchanges as well. Here is the example in our [[Decentralized Exchange Service (DEX)|DEX]] of token pair CELL/KEL which both have **CF-20** format. ![[Pasted image 20240916145846.png]] ## Interaction All interaction with the Cellframe node and **CF-20** tokens as well is based on the [[5. CLI Node Commands|CLI-Commands]] and [[1. Introduction|JSON-RPC requests]]. For interaction via JSON-RPC we developed [[5. WEB3 API|WEB3 API]], which is must a have for developers and projects. This API is designed for providing following interaction: ![[Pasted image 20240607143256.png]] `Request` is just a usual GET request on `localhost:8045` Interaction with Cellframe node via WEB queries is really efficient and convenient.