Create a native reward token

Before you start

• A verified signed-in account and enabled native launch wallet.
• The current required COMPUTER holdings and enough separate SOL in that selected native wallet.
• Artwork you have permission to publish and a current source capability check.

Choose an admitted source explicitly

Open Create and wait for the source-specific availability check. Native reward issuance is the admitted new-token path, but account, custody, resources and runtime gates still apply. A top-level configuration flag is not the availability verdict for every source.

Standard escrow is recovery-only; new Pump launches, adoption and X launch are deferred. An old draft is not automatically converted. If the draft’s mode is unavailable, explicitly review the mode choice or keep the draft unchanged.

1. Sign in and open the web launch form from Create.
2. Wait for configuration to load. Use Retry if availability cannot be checked.
3. Select the native reward mode and confirm the form labels it available before continuing. Follow the displayed current hold and SOL requirements rather than a fixed amount from an old guide.

Choose the permanent identity

The five-step wizard starts with name and ticker. The form validates permitted characters and lengths; inspect the recorded name if underscores are normalized. Name and ticker are written into the mint and cannot be changed later.

A ticker is not a unique token identity. After creation, use the mint and launch receipt to identify your asset. A page banner or explorer request does not rename the token.

1. Enter a valid name and ticker and read any field error.
2. Check spelling and the displayed recorded name before advancing.
3. Use Back to correct unsaved choices before saving an intent. Do not expect identity edits after issuance.

Separate rewards from the strategy

In Quote / mode, verify the selected native launch wallet, reward asset and available thesis choices. The launch hold must be in that native wallet; linking an external wallet or retaining COMPUTER in Turnkey does not satisfy it.

A selected thesis records intent, not a live position. Injective admission does not prove funded, armed or live execution. Phoenix and other unsupported venues are not silently substituted. The current new reward path requires no compulsory reward-token reserve purchase or pre-existing reward-token balance.

1. Check the exact reward asset and available strategy configuration in the form.
2. Review any source, reward or venue blockers before advancing.
3. Keep the COMPUTER holding requirement distinct from SOL costs and from historical reserve-acquisition obligations.

Prepare artwork and any optional personal buy

Use the image step’s actual type, size and upload validation. The launch publishes public artwork and metadata, so do not upload private information or artwork you cannot legally publish.

A personal/dev buy is optional. If chosen, it adds a separate purchase amount and applicable costs to the review. It is not the same as the COMPUTER hold gate, a fee or a mandatory reward reserve.

1. Select artwork and resolve any upload validation error; inspect the preview.
2. Choose whether to include an optional personal buy and check its amount and asset.
3. Review these choices before saving. If an upload succeeds, still wait for verified public metadata before signing.

Saving an intent is not minting

Review the wizard choices and save one launch intent. The saved attempt has its own durable reference and freezes the draft; it is not a confirmed mint or a completed payment. Keep its link, especially if the browser reports draft-storage failure.

Preparation publishes the image and metadata JSON and checks their exact public URLs before mint signing. An upload receipt alone is insufficient. Resume that same attempt when offered; closing the page or discarding a local draft does not cancel it.

1. Review the wizard summary and save the intent once.
2. Open the saved attempt and retain its link. Read its current publication, cost and signing status.
3. If preparation is blocked, use the attempt’s status or resume controls rather than starting a duplicate token.

Authorize only the reviewed maximum

The launch dialog itemizes service fee, optional personal buy and its fee, rent and network costs as applicable. Inspect exact amounts versus ceilings, quote validity and any selected allowance. Confirming a cost maximum is not itself proof of a signed or submitted mint.

Use the current account, source and signing gates. Native signing is server-managed, not a universal original-browser Turnkey owner-key flow. Do not accept a different amount, source, mint or expired packet to bypass a blocker.

1. Wait for fresh costs and verified publication. Refresh costs if the review is stale.
2. Read the maximum authorized spend, nonrefundable terms and all itemized costs. Choose an offered allowance deliberately.
3. Acknowledge and use the final create/signing action once when all gates permit it.
4. Follow that same attempt through submission and confirmation. If outcome is unknown, stop and check status; do not resend.

Verify separate completion states

A confirmed mint can still be completing platform adoption checks. Keep the same attempt while it finalizes. Issuance, metadata publication, platform adoption, strategy activation and external logo display are separate outcomes.

Use My launches to revisit the attempt and Manage branding when eligible. Verify the exact mint and receipt on the public token page. Do not create a second token because a wallet, explorer or indexer has not displayed the logo yet.

Related guides