Get KRC20 Tickers

Supported krc20 list

GET https://api2.chainge.finance/fun/getFun

200:OK

{
    "code": 0,
    "msg": "success",
    "data": {
        "version": 32,
        "list": [
            {
                "id": 3,
                "index": 93,
                "ticker": "RATS",
                "lpTicker": "LPRATS",
                "totalSupply": "100000000000000000000",
                "name": "RATS",
                "creator": "kaspa:qppf9n50jvgusswu3chje4zjmf58dugf7p8c4ctrr6fh5ewqre57zz6m66jg6",
                "createTime": 1737266731,
                "icon": "https://icon.chainge.finance/knot/icon_RATS_color.png",
                "header": "https://icon.chainge.finance/knot/header_RATS_color.png",
                "evmChain": "BASE",
                "evmTokenAddr": "0x71e354c8b01364362879d2fd9f071d0a8b352828",
                "evmTokenDecimals": 8,
                "evmPairAddr": "0x3af55d6e88f3bf8ae320d84bfc05aeec664cba12",
                "isFun": true,
                "flags": 15
            }
        ]
    }
}

For API integrators, you only need to care about two fields.

1. ticker-the unique and immutable identifier once created on kaspa chain

2. flags-control permissions and functionalities available for each ticker using a bitwise flag system.

Each flag represents a specific permission that can be enabled or disabled independently.

const FunFlags = {
    CanAddLp: 1 << 0,    // 1  - Can add liquidity
    CanRemoveLp: 1 << 1, // 2  - Can remove liquidity
    CanSwapBuy: 1 << 2,  // 4  - Can buy token
    CanSwapSell: 1 << 3, // 8  - Can sell token
    CanBridge: 1 << 4    // 16 - Can bridge token cross-chain
};

examples:

flags = FunFlags.CanAddLp | FunFlags.CanRemoveLp  //3, means both add and remove liquidity enabled
flags = FunFlags.CanAddLp | FunFlags.CanRemoveLp | FunFlags.CanSwapBuy | FunFlags.CanSwapSell //15, means add liquidity, remove liquidity, buy, sell enabled(most tokens has this flag)
flags = 0 //no operations can be conducted on this ticker, delisted