Sui Address

Overview

A Sui address is commonly displayed as a 0x-prefixed, 32-byte hexadecimal value. It can identify an externally controlled account, while packages and objects have related identifier forms within the same address space. Account addresses are derived according to a signature scheme and public key, so derivation includes a scheme marker rather than being a universal raw public-key encoding. Ownership of Sui objects is recorded separately in object metadata and can change through transactions.

Applications must normalize and validate the full value, expected entity type, and target network. Shortened display forms are useful for interfaces but unsafe for final verification. An address does not reveal which signing scheme or object permissions apply without additional data. Private keys and recovery phrases must never be inferred from or shared with an address.

Sui Address must be interpreted with its network, address or account type, encoding rules, and any required routing fields. A string that passes a format check can still belong to the wrong chain, unsupported asset, contract type, or destination that requires a memo or tag. Authorization depends on keys, scripts, contracts, or protocol rules, while custodial systems may expose an identifier without giving the user direct control of the underlying account. Sui Address is an identifier or spendable object, not proof of legal ownership and not a secret credential. Systems storing Sui Address should preserve the exact value together with chain identifiers and type metadata. Normalization, case conversion, truncation, and alias resolution need protocol-aware rules, because a visually similar value can represent a different destination or fail checksum validation.