aptos-object-model

The Aptos Object Model converts resources into transferable, composable on-chain objects using ObjectCore and Object<T>. This replaces resource-only patterns, enabling controlled ownership, transfer via TransferRef, and lifecycle management through constructor and extension references for Digital Assets, NFTs, and Fungible Assets.

ObjectCore is the foundational abstraction in Aptos's Object Model; Object<T> is a generic wrapper that holds typed data. Together they enable named objects with deterministic addresses, distinct object and owner addresses, and composable on-chain structures with controlled lifecycle management via refs.

These are lifecycle management references in the Aptos Object Model. Constructor refs create objects, ExtendRef enables extension, DeleteRef removes objects, and TransferRef controls transfer semantics. Together they enforce the required typed-reference semantics and ownership constraints for safe object composition.

Yes. The Aptos Object Model provides migration patterns from resource-only designs to object-based architectures. This applies across Digital Assets, NFTs, and Fungible Assets, enabling better composability, transferability, and lifecycle control while maintaining type safety.

In the Aptos Object Model, the object address is the unique identifier of the object itself, while the owner address tracks who controls it. This distinction enables composability and transfer semantics distinct from simple resource ownership, supporting nested and shared object patterns.