How to Create a Move-Native Sui Coin with Slingzero

What Slingzero publishes when you create a Sui Coin

The Sui Coin Creator turns the details entered in the form into a Move package and a wallet-signed publish transaction. The same transaction includes the disclosed Slingzero service fee, creates the initial supply, and returns the resulting capability objects to the connected creator wallet.

That structure is different from deploying an EVM token contract. A Sui Coin is identified by a Move type inside a published package, while supply and package changes depend on owned capability objects such as TreasuryCap and UpgradeCap. This guide follows the fields, network selector, publish sequence, and management handoff in Slingzero's current Sui creator.

Before using Mainnet: run the same form on Sui Testnet, keep the transaction digest, and confirm that the resulting Coin type and capability objects can be found from the connected wallet.

What the Sui Coin Creator does

The creator replaces the local package-generation and command-line steps with a web form. The connected wallet still reviews and signs the on-chain transaction.

The creator currently helps you:

• Define the Sui Coin name, symbol, description, logo, decimals, and initial supply.
• Choose Sui Mainnet for a live launch or Sui Testnet for a rehearsal.
• Upload a logo file or provide an image URL.
• Pin the logo to IPFS through Slingzero's Pinata-backed upload flow.
• Generate and compile the Move coin package through Slingzero's backend.
• Review the service fee before publishing.
• Sign and execute the publish transaction from your connected Sui wallet.
• Capture the transaction digest and explorer link.
• Redirect into the Sui Coin Manager after indexing.

The creator displays the applicable service fee before publishing. Network gas is separate and should be checked in the final wallet prompt.

Why Sui token creation is different

Sui uses a Move-native object model. That means a coin launch has different moving parts than a Solana SPL token, Ethereum ERC-20 token, or BNB Chain BEP-20 token.

For a standard Sui Coin launch, the important concepts are:

• Package: The published Move package that defines the coin type.
• Coin type: The canonical identifier, usually shaped like 0xpackage::module::COIN.
• TreasuryCap: The capability object used for supply operations such as minting and, depending on the coin model, burning.
• UpgradeCap: The capability object tied to package upgrade authority.
• Transaction digest: The public transaction reference used to verify the publish event.

The official Sui Coin Standard documentation explains how Sui represents Move-native coins. The Sui Currency Standard documentation explains TreasuryCap behavior in more detail. Slingzero's role is to make those mechanics usable from a wallet-first interface.

Step-by-step: create a Sui Coin with Slingzero

1. Open the Sui Token Creator

Go to Create Sui Token. The page is designed around a direct launch workflow: token identity, supply settings, wallet connection, and one publish transaction.

Use Sui Testnet first if you want to rehearse the process. Use Sui Mainnet only when your metadata, supply, and launch wallet are ready.

2. Enter token identity

Fill in:

• Name: The public token name.
• Symbol: The ticker shown in wallets and dashboards.
• Description: A short explanation of the token's purpose.
• Logo: Upload a file or paste a URL.

Slingzero resolves logo URLs and can upload token images through the existing Pinata-backed media flow, which helps keep the coin metadata stable for wallets and token pages.

3. Set supply and decimals

Enter the initial supply and decimals. The Sui creator previews raw on-chain units so you can see how the display amount translates into the integer amount used on-chain.

The current creator defaults to 9 decimals. Use a different value only when the asset model requires it: decimals are part of the published currency definition and should be treated as a launch-time decision.

4. Connect a Sui wallet

Connect the wallet that should publish the package and receive the capability objects. Slingzero does not custody your Sui token authority. The transaction is signed through your wallet.

Before publishing, confirm:

• The connected wallet is the intended creator wallet.
• The selected network matches your launch plan.
• The wallet has enough SUI for gas and service fee.
• The token name, symbol, supply, decimals, description, and logo are final.

5. Compile and publish the Move package

When you submit, Slingzero runs the creation flow in three stages:

• Compile Move package: Generate the package modules and dependencies.
• Approve wallet transaction: Transfer the service fee and publish the package.
• Publish and index coin: Resolve the created package, coin type, and capability objects.

After the transaction confirms, the creator shows the success state and records the created coin details.

6. Manage the Sui Coin after launch

Once the coin is indexed, Slingzero redirects to the Sui management route for the created coin type. You can also open Manage a Sui Coin manually and paste the coin type in the format 0xpackage::module::COIN.

Use the Sui Tools page as the hub for supported supply, capability, and security actions.

What gets transferred to the creator wallet?

The Sui creator is designed so the connected creator wallet remains the authority holder after publishing. The flow resolves the created package and identifies the coin type from transaction object changes and Sui effects.

The launch output includes:

• Published package ID.
• Canonical coin type.
• TreasuryCap object when it can be resolved.
• Transaction digest.
• Explorer URL for the selected network.
• Activity record for the Sui launch.

That output is the evidence needed to distinguish the asset from another coin with the same name or symbol. A public launch record should include the Coin type, package ID, transaction digest, capability policy, and a read-only explorer link such as Sui Explorer or Suiscan.

Public verification checklist for a Sui Coin launch

If you are launching a Sui token publicly, do not rely only on social posts. Create a permanent page on a domain the project controls and link it from official channels.

Your public launch page should include:

• Official coin name and symbol.
• Chain: Sui Mainnet or Sui Testnet.
• Coin type in 0xpackage::module::COIN format.
• Package ID.
• Transaction digest.
• TreasuryCap and UpgradeCap custody policy.
• Initial supply and decimals.
• Logo and metadata links.
• Explorer links for verification.

This gives holders a stable source of truth that is easier to verify than a copied ticker or logo.

Launch-day checklist

Before you publish the Sui Coin:

• Rehearse on Testnet when possible.
• Confirm your token name, symbol, description, logo, decimals, and initial supply.
• Keep the logo under the creator's upload limits.
• Use the wallet that should receive the package capabilities.
• Make sure the wallet has SUI for gas and the Slingzero service fee.
• Save the transaction digest and explorer URL after publishing.
• Copy the coin type immediately after the launch succeeds.
• Open Sui Manage and verify the coin type loads.

After publishing:

• Add the coin type to your official website.
• Share the package ID and explorer link.
• Document TreasuryCap and UpgradeCap custody.
• Keep launch actions visible in Activity.
• Link back to Sui Tools for future management operations.

How Sui differs from Slingzero's other creators

The interface pattern is consistent across Slingzero, but the on-chain result is not the same on every network:

• Create Solana Token for SPL token launches.
• Create Ethereum Token for ERC-20 launches.
• Create BNB Chain Token for BEP-20 launches.
• Create Sui Token for Move-native Sui Coin launches.

Solana produces an SPL mint, Ethereum and BNB Chain produce EVM contracts, and Sui publishes a package with a canonical Coin type. Use the complete network-specific identifier when documenting the asset.

Next step

Open Create Sui Token and begin with Testnet if this is your first package publish. Move to Mainnet only after the metadata, supply, decimals, wallet, and capability policy are final.