Launching a Token on KUB

When launching a token on KUB, you can choose between two standards: KAP-20 or ERC-20. This guide will help you decide which option suits your needs and provide a step-by-step process for deploying a KAP-20 token.

Choosing Your Launch Path

KAP-20

KAP-20 is the fungible token standard specific to KUB, based on the ERC-20 model but tailored with unique KUB features. Opt for KAP-20 if you require:

• KUB Wallet Compatibility - Utilize KYC-aware processes to seamlessly integrate KUB Wallet into your project.

• Asset Recovery - This feature allows the token's governance committee to reverse fraudulent transactions (e.g., following a legal directive), giving token developers control over recovery actions.

• Ecosystem Alignment - Tokens such as kKUB, kBTC, kETH, and others in the KUB ecosystem use the KAP-20 standard.

KAP-20 operates at the contract level: you’ll deploy the official version from kub-chain/kub-contracts and connect it to a shared set of contracts (including the KYC registry, AdminProjectRouter, and TransferRouter).

ERC-20

The KUB network also supports ERC standard tokens. Use a standard OpenZeppelin ERC-20 token if you need:

• Consistency with Other EVM Chains - Ensure your token functions identically to those deployed on different EVM networks.

• No Admin Recovery or KYC Functions - Keep your contract simpler without these additional complexities.

• Minimal Constructor Surface - Reduce the number of parameters required for deployment.

Deploying an ERC-20 token follows the same process as on any EVM chain: just adhere to the typical deployment guidelines with your OpenZeppelin contract.