Token Verification

Token verification is an optional process that enhances the visibility and usability of your token in Entangle’s bridge and dApp ecosystem. By verifying your token, it becomes searchable by name rather than by address, improving user accessibility and integration within the platform.

After deploying your token and setting up its cluster, you can use the bridge and associated dApps. By default, users can search for your token using its contract address. Token verification ensures your token is indexed, allowing users to find it quickly by name in search fields.

After deploying and setting up your cluster you can start bridging and using our dApp for this purpose, but by default, you can find your token using address only. This guide will help you to verify your token and after verification, we will index your token and you will have a possibility just to write the name of your token in the search field.

Verification Steps

1

Prepare Your Repository

• Fork the token verification repository.

• Create a project folder in the projects directory and add a CLUSTER_INFO.json file based on the provided template.

{
    "General information":{
        "TokenName":"Mytoken",
        "TokenSymbol":"MTK",
        "DeployedViaFactory": "false",
        "ChainIDs":[1, 42161]
    },
    "Deployments": [
        {
        "ChainId": 1,
        "Address": "0x",
        "Type": "Token",
        "Decimals": 18
    },
    {
        "ChainId": 42161,
        "Address": "0x",
        "Type": "Connector",
        "Decimals": 6  
    }
    ]
}

2

Expand Existing Clusters

• If you’ve already verified your token but added new deployments to its cluster, create a new pull request mentioning the expansion and update the CLUSTER_INFO.json.

3

Submit Your Request

• Fill out the required details in the repository’s README and corresponding Google form.

• Submit a pull request using the provided PULL_REQUEST_TEMPLATE.md file.

Notes

Instructions for Expanding Verified Tokens in Cluster Updates After Token Verification

If your token is already verified but you've expanded your cluster, you can create a new pull request. Please mention that your token is already verified and you only need to expand it. Additionally, ensure that you include the updated information in the CLUSTER_INFO.json file as part of the pull request.

Specifying Entity Types in Deployment Information

In the deployment information's type field, there are two possible entities: Token and Connector.

If the entity is a token, specify Token; if it is a connector, specify Connector.

Guidelines for Setting the DeployedViaFactory Field in Cluster Info

In the cluster information, there is a field called DeployedViaFactory. If you deployed your tokens or connectors through our factory (either manually or via the dApp), set this field to true. Otherwise, set it to false. Deployments using our predefined blueprints via the factory will result in a faster verification process.

Internal Requirements for Verified Tokens: Ensuring User Security

Our internal requirements for verified tokens are straightforward: we reject scam tokens and any other tokens that pose a risk to regular users' funds.

Chain ID Configuration for Solana and TON Deployments

As we prepare to expand to Solana and TON, please use the following chainId values for deployments:

• For Solana: 11100000000000000501

• For TON: 100004503599627370496