Launching a token in one signature

02The recipe

• 1,000,000,000 tokens with 18 decimals. The maximum supply is set to that amount and all of it is minted at launch, and the token is sealed at birth, so no contract can ever be attached to it.
• All of it goes into the pool, paired with 250,000 KCAL from your wallet. That pair sets the opening price.
• You choose the pool fee, from 0.3 to 5 percent. Traders pay it on every swap.
• The liquidity is burned. The pool can never be removed and the deposit can never be withdrawn, by you or anyone.

03You own the token and its owner key

Every Phantasma token has an owner key, and that key keeps real power for good. It can mint up to the maximum supply (burned tokens never count as room again), or any amount when there is none. It can add an inflation schedule that anyone can then trigger; its payouts stay under the cap. Unless the token is sealed, it can attach code to the token and later swap that code, and such code can block the transfers DEX contracts make. It can change the token's name, icon, description and link. Sealing gives up the contract part forever; nothing gives up the rest or hands it to another key, and creating the token needs the owner's signature.

Launch makes your passkey wallet the token's owner, as Create token does, and your wallet signs the launch alone, with one passkey prompt. Launch mints the whole cap at once, and burned tokens never count as room again, so no one, you included, can ever mint more of it. The token is sealed at birth, so no contract can ever be attached to it. What you keep as owner: changing the name, icon, description and link, the token's Aetherpost profile and the @handle that matches its symbol, posting on Saturn as the token and opening its community.

• Holders can still burn their own tokens: every Phantasma token allows it, and nothing can switch it off.
• The chain's own governance can still act on any token, this one included. That is a rule of the chain, not a key anyone at Saturn holds.

Every launch is sealed at birth: the creation itself carries the seal. The Launch page will not send a launch without it, and your passkey wallet will not sign one. On devnet, a launch that could also run on mainnet (its symbol free there and your wallet holding enough KCAL there) is refused, because a launch names no network.

04What you get

It is a fair launch: you start with none of the token and buy like everyone else. You keep the pool certificate, which collects the provider share of every swap fee on the pool forever, and the reinvest share keeps compounding into the burned pool. The token page and pool page pick it up as soon as it trades, and on mainnet so does its price chart.

Your fees do not depend on the token's owner key. The pool is burned at launch, and from then on its certificate is the fee key: the fee vault pays the pool's provider fees only to whoever holds that certificate. It is minted to your wallet at launch and stays there unless you sell or give it away. Claim from Liquidity as with any burned pool.

05What it costs

• The chain's token creation fee, about 10,000 KCAL for a long symbol and more for a short one, since the symbol surcharge halves with every extra letter.
• The pool certificate fee, 2,500 KCAL.
• The 250,000 KCAL that goes into the pool.
• Data fees in SOUL, usually under 0.1. The page asks you to hold 5 SOUL, the most the launch can use.
• The launch holds the fee ceiling while it runs and refunds whatever it did not use. The page shows every number before you sign.

06Why passkey only

The launch mixes token-module calls with a DEX script in one transaction. The in-app passkey wallet signs that as one unit. Create one on the Wallet page; it takes a minute and needs no app.

The symbol is checked as you type and again just before signing. If someone takes it in between, the launch fails as a whole and nothing is created.

I launched a token. Can I still claim its rewards?

Yes. The creator's share of swap fees belongs to whoever holds the pool certificate, and you hold it. The token's owner key has nothing to do with it.

Who owns the token?

You do, from the wallet that launched it, as with Create token. As owner you can change the name, icon, description and link, claim the token's Aetherpost profile and its @handle, post as the token and open its community. No one, you included, can attach a contract (it is sealed at birth) or withdraw the burned liquidity. Your share of swap fees comes with the pool certificate, not the owner key.

Do service tokens work the same way?

Mostly. A service token is owned by its launcher too, and linking it to the service checks that owner. It pairs 95% of the supply with TAZ instead, and its profile discloses the 5% the launcher keeps.