Aptos Portfolio Tracking: The Move Resource and Object Model

Aptos is not an EVM chain with different gas. It is a Move chain: assets are resources owned by accounts, grouped into Objects with their own addresses. An EVM mental model reads it wrong. This guide is the resource/Object model and what it changes for portfolio tracking.

TL;DR

• Aptos uses the Move resource model: an asset is a resource owned by an account, not a contract balance mapping.
• A resource cannot be copied or deleted without the owning account's permission — strong asset semantics.
• Objects group resources and have their own address — discovery must follow Objects, not just the wallet.
• The reportable quantity is still a number, but it is read from the resource/Object structure.
• Cost basis/tax unchanged — the jurisdiction method applies; the data model differs.
• An EVM-style tracker can miss positions — model resources/Objects or under-report.

Resources, not balance mappings

On an EVM chain a token is a contract with a balanceOf mapping. On Aptos (Move), an asset is a resource: a top-level value stored in a specific account that cannot be copied or deleted without that account's permission. That ownership model is precisely what makes resources good asset representations — and it means tracking reads account-held resources, not a contract-side ledger.

The mental shift: ask "what resources does this account own?", not "what does the token contract say this address holds?"

Objects: grouped resources with an address

Aptos adds Objects — a construct that groups a set of resources and has its own address, usable to address the resources within. For portfolio tracking this means a position or asset can be represented by an Object with its own identity. Discovery must therefore follow Objects and their grouped resources, not assume a single balance field on the wallet address. Missing an Object is missing whatever it groups — the Aptos analogue of an unmapped wallet.

What the figure still is

None of this means balances are unreportable numbers. The quantity you report can still be a quantity. The point is where it lives and how it moves:

• it lives as a resource (possibly grouped under an Object) owned by the account;
• it moves under Move ownership semantics (no implicit copy);
• the tracker must read and reconcile the resource/Object structure, then express the position.

Tax is unchanged; modelling is the work

Aptos does not change the cost-basis method — that stays the jurisdiction-mandated one. What changes is the data model. The tracking work:

• completeness across the account's resources and Objects;
• correctly interpreting resource/Object transfers;
• internal transfers between your own Aptos accounts as non-disposals (see internal transfer vs disposal).

This is the same discipline as multi-chain reconciliation, applied to a non-EVM model.

Practical guidance

1. Drop the EVM mental model — read account-owned resources, not contract balances.
2. Follow Objects and their grouped resources during discovery.
3. Respect Move ownership semantics when interpreting transfers.
4. Ensure completeness across all resources/Objects of the account.
5. Apply the jurisdiction cost-basis method; classify internal transfers as non-disposals.
6. Reconcile the resource/Object set to the chain with an audit trail.

How vendor tools handle Aptos

Koinly and Zerion support Move-chain accounts. Confirm the tool models resources and Objects (not an EVM balance mapping), achieves completeness across an account's Objects, and classifies internal Aptos transfers as non-disposals — an EVM-only tracker will under-report a Move portfolio.

How Wag3s helps

Wag3s Folio reads Aptos holdings as account-owned Move resources, follows Objects and their grouped resources for completeness, interprets transfers under Move ownership semantics, and applies your jurisdiction's cost-basis method with internal transfers classified as non-disposals. See the Folio product page.

Further reading

• Sui Portfolio Tracking
• Solana Portfolio Tracking
• Multi-Chain Reconciliation
• Multi-Chain Portfolio Aggregation Beyond EVM
• Crypto Cost Basis Methods 2026
• Internal Transfer vs Disposal in Crypto

Sources

• Aptos / Move — the resource model (a resource is a top-level value stored in an account; cannot be copied or deleted without the account's permission)
• Aptos Objects — group a set of resources and have their own address used to address the grouped resources
• Move ownership semantics differ from the EVM contract balance-mapping model (read account-owned resources)