ABI (Application Binary Interface) describes the public interface of a smart contract. It defines which functions the contract exposes, what parameters they accept, and what data they return.
ABI does not contain private data and does not grant control over the token. It is a public technical description used to interact with a deployed contract.
ABI can be useful in the following cases:
• integrating the token into a dApp or custom application
• interacting with the contract via Web3 libraries and tools
• reading on-chain data (balances, total supply, metadata)
• connecting the token to analytics or monitoring services
• building custom interfaces on top of the token
If you do not plan any technical integrations, ABI is not required for normal token usage.
• ABI cannot modify the contract
• ABI does not provide owner permissions
• ABI does not replace the contract source code
• ABI reflects the interface of the template used to create your token
Mintly provides the ABI of the exact template that was used during deployment.
• ABI is generated automatically based on the selected template
• ABI is provided in standard JSON format
• ABI can be downloaded and used in third-party tools
• Mintly does not alter the ABI after deployment
You can safely ignore this section. ABI is not required for holding, transferring, or basic use of your token.