ARC-20
Abbreviation: ARC-20
Pronunciation: AY-AR-SEE twenty
Also known as: ARC-20
Definition
ARC-20 is an Algorand Request for Comments specification for smart-contract-controlled Algorand Standard Assets. It defines an interface that associates an ASA with application logic capable of enforcing custom transfer, freeze, clawback, or related behavior. ARC-20 should not be confused with unrelated token standards that use the same label in other ecosystems.
Overview
Meaning and scope
ARC-20 is an Algorand Request for Comments specification for smart-contract-controlled Algorand Standard Assets. It defines an interface that associates an ASA with application logic capable of enforcing custom transfer, freeze, clawback, or related behavior. ARC-20 should not be confused with unrelated token standards that use the same label in other ecosystems.
Mechanism and operation
Algorand Standard Assets are created at the protocol level and can include management roles such as manager, reserve, freeze, and clawback addresses. ARC-20 describes a pattern in which a smart contract controls relevant asset behavior and exposes a consistent application interface. The ASA can continue to serve as the ledger-level asset representation, while the associated application implements programmable transfer rules. This supports features that resemble contract-based tokens without replacing Algorand’s native asset accounting. The asset’s control addresses and metadata must point to the intended application according to the standard. If administrator roles remain under unrelated keys, users may have more trust assumptions than the ARC-20 interface suggests.
Practical payment example
An Algorand issuer deploys an application to enforce additional asset-transfer conditions while the ASA remains the ledger-level asset. Reviewers inspect both the asset control addresses and the application logic before accepting the token.
Operational checks
They should use the specified contract methods and verify the application ID, asset ID, network, and permissions. Standards can evolve, so integrations should rely on the current ARC specification and compatible tooling. The same name “ARC-20” is also used informally in other blockchain communities, which can create confusion.
Distinctions and limits
Wallets and applications need to understand that an ordinary ASA transfer path may not represent the complete intended logic. ARC-20 is best treated as an Algorand application interface for controlled ASA behavior, not a universal fungible-token protocol across all chains.
Related reading
Related definitions: smart contract, blockchain.
Example
An Algorand issuer deploys an application to enforce additional asset-transfer conditions while the ASA remains the ledger-level asset. Reviewers inspect both the asset control addresses and the application logic before accepting the token.
Comparison
Wallets and applications need to understand that an ordinary ASA transfer path may not represent the complete intended logic. ARC-20 is best treated as an Algorand application interface for controlled ASA behavior, not a universal fungible-token protocol across all chains.
Key Takeaway
Algorand ARC-20 links native ASA accounting with smart-contract-controlled behavior, requiring exact application, asset, metadata, permissions, and governance verification practices.
Sources
- Ethereum Documentation: Smart Contracts — Ethereum Foundation (2026-07-30)
- Ethereum Documentation: Transactions — Ethereum Foundation (2026-07-30)