token-standards_skill

This skill helps you navigate Aptos token standards across fungible and non-fungible tokens, enabling correct minting, transfers, and royalties.

62

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill raintree-technology/claude-starter --skill token-standards

  • SKILL.md5.9 KB

Overview

This skill is an expert reference for Aptos token standards covering fungible tokens (Coin, Fungible Asset) and NFTs (Digital Asset / Token V2). It explains creation, minting, burning, transfers, collections, metadata, royalties, and recommended patterns for production systems. It targets developers building on Aptos who need practical, production-ready guidance.

How this skill works

The skill inspects and explains core Move primitives and Aptos framework modules used to implement tokens: coin, fungible_asset, aptos_token_objects, collection, token, property_map, royalty, and object transfer refs. It summarizes code patterns for initializing modules, generating and storing capability refs, minting/burning, registering accounts, and managing metadata and royalties. It also contrasts legacy Token V1 with current Digital Asset (Token V2) and highlights when to choose Coin vs Fungible Asset.

When to use it

  • Start new NFT projects with Digital Asset (Token V2) for composability and metadata features.
  • Use Coin framework for simple fungible tokens like APT or straightforward ERC20-like tokens.
  • Use Fungible Asset when you need advanced controls: freeze, transfer refs, or configurable supply.
  • Implement royalties via the royalty helper when secondary-sale fees are required.
  • Prefer object-model tokens when you need on-chain mutable properties or composable assets.

Best practices

  • Store mint/burn/transfer capability refs securely inside module-hosted resources.
  • Validate metadata and typed properties before minting to avoid immutable mistakes.
  • Prefer Digital Asset for new NFTs; avoid Token V1 except for legacy compatibility.
  • Design upgrade or migration patterns early; include tests for supply and permission flows.
  • Test on devnet/testnet with full lifecycle: create, mint, transfer, freeze, burn, and royalty settlement.

Example use cases

  • Create a utility token with Coin for in-platform payments and simple balances.
  • Launch a game NFT collection with Digital Asset, using property_map for level and rarity upgrades.
  • Issue a capped fungible asset with Fungible Asset for tokenized in-game currency that supports freezes.
  • Mint collectibles with per-collection royalties to enforce creator fees on secondary markets.
  • Implement soul-bound or composable assets using Token V2 object patterns.

FAQ

Choose Coin for simple tokens and broad compatibility; choose Fungible Asset for advanced controls (freeze, transfer refs, custom supply) and richer administration.

Are Token V1 tokens still supported?

Token V1 is deprecated; only use it for legacy compatibility. Use Digital Asset (Token V2) for all new NFT projects due to the object model and composability.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational