01
Create the asset
Deploy a native Aptos Fungible Asset with image, metadata, decimals, initial supply and optional permanent supply lock.
Open creator ->
SolCreate
Aptos mainnetNative FA workflow5 APT / action
Aptos launch stack
Move-native assets from creation to market
Create Aptos Fungible Assets, control supply and wallet permissions, then open or manage concentrated-liquidity positions on Hyperion.
Aptos route overview
Move-native assets from creation to market is the planning role of this Aptos overview: it connects Fungible Asset creation, controller decisions, supply actions, recipient distribution and Hyperion market preparation without treating the page as a single wallet form.
02
Manage controls
Mint, burn, freeze, unfreeze or permanently destroy mint authority through explicit wallet-approved Move calls.
Open controls ->03
Distribute supply
Send one selected asset to as many as 100 validated Aptos recipients in a single atomic batch.
Open multisender ->04
Open the market
Create an APT market with initial liquidity or add to an existing concentrated-liquidity position on Hyperion.
Open liquidity ->Native Move architecture
One control path, clear ownership
Fungible Asset metadata object
Creator-owned AssetController
MintRef can be destroyed permanently
BurnRef and TransferRef remain explicit
APT-paired Hyperion positions
One wallet prompt per complete action
Aptos token creation and liquidity in one launch stack
SolCreate uses the Aptos Fungible Asset standard rather than disguising Aptos operations as an EVM contract flow. Each created asset receives a dedicated controller under its metadata object. The connected creator wallet remains the controller, while SolCreate only prepares the transaction that the wallet displays and approves.
Hyperion integration continues the same launch path. A new asset can move directly from creation to an APT market with initial concentrated liquidity. Existing position holders can add more liquidity or withdraw a precise percentage. The SolCreate service fee and Hyperion operation are composed atomically, so a reverted DEX action cannot leave behind a successful service-fee payment.
Every operation is a blockchain transaction and carries Aptos network gas in addition to the displayed SolCreate fee. Token creation and market creation do not guarantee price, liquidity, demand or safety. Always verify metadata addresses, wallet recipients, asset order, price parameters and final wallet details before approval.
Aptos route decision record
Separate the Aptos token creator from live supply and Hyperion tools
Aptos builders often compare “create Aptos token,” “mint Aptos token” and “Aptos liquidity” in the same planning session. SolCreate keeps those routes connected, but the overview explains which wallet action belongs to first deployment, which action belongs to an existing Fungible Asset, and which action belongs to a Hyperion market position.
Use the Aptos token creator for first deployment
The creator route is for a new Aptos Fungible Asset. Prepare the asset name, symbol, decimals, image, starting supply, controller wallet and optional supply-lock decision before opening the live form.
Open Aptos creator ->Use mint and burn only after the asset exists
Minting adds authorized supply to an existing asset, while burning removes held supply from the connected wallet. Those actions should reference the original metadata object instead of replacing the first-deployment record.
Review supply tools ->Keep Hyperion liquidity separate from creation
Hyperion routes belong after the token exists. Builders should review token order, APT pairing, price parameters, fee tier, slippage and position ownership before opening or adjusting concentrated liquidity.
Plan Hyperion liquidity ->Route wallet controls to the matching evidence trail
Supply lock, wallet freeze and multisender pages answer different launch questions. Keep each Aptos action tied to the asset metadata address, controller status, recipient list and wallet-confirmed transaction.
Check controls ->Aptos builder checklist before wallet approval
Use this checklist to keep the Aptos Token Creator, live creator, mint, burn, multisender, supply-lock and Hyperion liquidity pages from overlapping in the launch record.
- Start on the Aptos overview when choosing between first deployment, supply control, distribution and Hyperion liquidity.
- Open the Aptos token creator only when the project needs a new Fungible Asset metadata object and first supply record.
- Use Aptos mint for authorized supply increases on an existing SolCreate asset, not as a shortcut for creating a new asset.
- Use Aptos burn for wallet-held supply reductions, not for liquidity-position withdrawal or market cleanup.
- Use Aptos supply lock only when the team is ready to permanently remove future minting capability.
- Use Aptos multisender for reviewed recipient batches after token identity and balances are already clear.
- Use Hyperion add or remove liquidity after reviewing token/APT order, price, position share and the connected wallet's approval details.