KAP Token Interfaces

Smart contract token interfaces define the external surface of a token contract. They tell wallets, dApps, explorers, and other contracts which functions and events they can rely on. An interface does not describe internal storage or implementation details. It defines the public contract between your token and every integration around it.

On KUB, token interfaces are commonly defined through KUB Application Protocol (KAP) standards. KAP extends familiar ERC patterns with KUB-specific roles, KYC-aware transfer flows, and admin-controlled recovery functions where required.

What Token Interface Includes

A token interface usually defines:

• Read functions such as balanceOf, name, and symbol

• Write functions such as transfer, approve, and transferFrom

• Events such as Transfer and Approval

• Expected behavior for approvals, transfers, and ownership

Why It Matters

Interfaces make integrations predictable. They let wallets display balances and metadata. They let dApps request approvals and submit transfers. They let developers verify whether a token supports the behavior they need before integrating it. On KUB, interfaces also help clarify KUB-specific token behavior. KAP standards add functions such as adminTransfer, internalTransfer, and externalTransfer. These functions are not part of standard ERC token interfaces.

KAP Token Interfaces

Use these KAP interface pages when you need the exact function and event definitions for a token standard on KUB:

• KAP-20 - Fungible token interface for KUB with KYC-aware transfer flows and adminTransfer

• KAP-721 - Non-fungible token interface for unique assets on KUB

• KAP-1155 - Multi-token interface for fungible and non-fungible assets in one contract

• KAP-22 - Loyalty points token interface built on KAP-20 with periods and token expiration

How To Use the Interface Pages

Use the interface page when you need to:

• Check supported functions and events

• Review token behavior before integration

• Compare standards before choosing one

Choose the token standard that matches your use case, then review its interface in detail before you deploy or integrate it.