Aptos Address

Overview

Aptos identifies accounts with 32-byte addresses. User account addresses are established during account creation and are used as the location under which resources and modules can be stored. The address is commonly displayed as a hexadecimal value beginning with 0x, with software able to normalize shorter representations to the full value.

An Aptos address is distinct from an authentication key. Account authentication can change through key rotation or account-abstraction mechanisms while the account address remains stable. This separation allows an account to preserve its on-chain identity even when authorization changes. Modules are identified by the address of the account that publishes them together with the module name. Resources are also stored under accounts and referenced through their type. As a result, the address participates in both user payments and application state.

For transfers, users must ensure that the address belongs to the intended Aptos network and that the receiving account can handle the asset standard being sent. A syntactically valid address is not proof that the recipient controls or expects it. Aptos separates account identity from authentication more clearly than many users expect. An account can rotate its authentication key while preserving the same account address and on-chain resources. This allows security upgrades without changing the public account identifier. Addresses also identify modules and resources within the Move ecosystem. A module is referenced by the publishing account address and module name, while resource types include address-based type information. Applications should normalize addresses consistently and compare their underlying bytes rather than treating different textual forms as different accounts. Before transferring assets, wallets should verify the intended network and asset standard, because a syntactically valid Aptos address does not prove that the recipient expects that token.