Aptos — Move VM, resource-based accounts
Aptos uses the Move VM with a resource-centric account model. Each account holds typed resources rather than a single balance — and the audit trail shows the same.
Aptos's account model treats every asset as a "resource" stored under an account address. APT, fungible tokens, NFTs, and custom Move resources all live in the same account but as distinct typed objects. Cost basis tracks per resource. Staking on Aptos is delegator-based with per-epoch reward distribution. The DeFi ecosystem is led by PancakeSwap on Aptos, Thala, Liquidswap, and Aries — each a Move package we decode for transaction-level detail.
What's tracked on Aptos
APT and fungible asset transfers
Resource-level cost basis for APT and Aptos fungible tokens.
APT staking
Per-epoch reward accrual against delegated validators.
Move package decoding
Function calls decoded against published Move modules.
PancakeSwap, Thala, Liquidswap, Aries
Swap and lending positions tracked end-to-end.
Aptos NFTs (Token V1 and V2)
Mint, transfer, sale events with cost-basis tracking per token.
Common Aptos transaction patterns we classify
- Send / receive APT
- Fungible asset transfer (Aptos Fungible Asset standard)
- Coin transfer (legacy Aptos Coin standard)
- Delegation staking deposit / withdrawal
- Validator reward receipt (per-epoch distribution)
- Liquidswap swap
- Thala protocol swap or liquidity position
- PancakeSwap on Aptos swap
- Aries Markets supply / borrow / repay
- Add / remove liquidity (Liquidswap or Thala LP)
- NFT mint / transfer (Token V1 or Token V2)
- Move module entry function call (generic contract interaction)
What changes when you book Aptos
Aptos uses two parallel token standards
Aptos has both the legacy Aptos Coin standard (the original fungible-token format) and the newer Fungible Asset (FA) standard introduced in later versions of the Move framework. Many protocols are migrating from Coin to FA. Wag3s tracks both and maintains continuous cost-basis history across the migration without creating spurious income events.
Gas fees are denominated in APT and scale with compute units
Aptos gas is calculated as gas-units consumed multiplied by a gas-unit price set by the network. Both components appear in the transaction receipt. Wag3s decomposes the fee into its components and books the total as an operating expense or adds it to cost basis depending on transaction type and your jurisdiction configuration.
Staking rewards land in the delegation pool, not your main wallet
When you stake APT via a delegation pool, rewards accrue inside the pool and are only realised when you withdraw. Wag3s tracks per-epoch reward accrual inside the pool and surfaces it as staking income on the date earned, consistent with accrual-basis treatment. On withdrawal, the cumulative booked rewards are reconciled against the actual transfer to avoid double-counting.
Aptos accounting questions
How does Aptos's resource model affect cost basis?
Each resource type is a separate accounting line. APT, USDC on Aptos, and a custom Move resource all live in the same account but track separately. Cost basis is per-resource, the same way it's per-asset on Ethereum.
Is the Move-based accounting different from Ethereum?
Mechanically yes (no smart-contract-deployed-token model — assets are first-class resources), but practically the audit trail looks similar from a finance team's perspective. We decode Move packages so the function calls are readable.
How does Wag3s handle storage deposits on Aptos?
Aptos charges a storage deposit (in APT) when creating new on-chain resources — for example, registering a new token in your account. Wag3s tags these as refundable deposit events, not gas fees, so they do not inflate your operating cost lines. The deposit is restored to your spendable balance when the resource is deleted.
Other chain coverage and tax guides relevant to this network.
Book Aptos the right way
Free during Alpha. Connect a wallet, see every transaction reconciled to journal entries.