Pre-deploy checklist
Bring this,we ship the token.
You must have your own Tonkeeper wallet before deploy. Phalanx handles the contract, gas, audit report, and on-chain verification — but your keys stay in your wallet.
Don't have a wallet yet? Follow the Tonkeeper setup guide →
Full guide: how to create your own Jetton on TON without code →
Create and secure your Tonkeeper wallet.
Every deploy is tied to a wallet you control. Create Tonkeeper, save your 24-word phrase offline, then connect via TonConnect in the build wizard.
- *
Tonkeeper installed (mobile or desktop)
Official app only — no third-party APKs.
- *
24-word recovery phrase saved offline
Paper or metal — never screenshots or cloud notes.
- *
Correct network (Testnet or Mainnet)
Match your pricing tier before you fund the wallet.
- *
TonConnect ready
You will connect the same wallet in step 1 of the build wizard.
Tell us who you are.
We don't custody your funds, but we do need a reliable owner of record so the dashboard, the audit packet, and any future support tickets land in the right inbox.
- *
Email account (Google or GitHub)
Used for sign-in and the deploy receipt.
- *
Project owner name or pseudonym
Shown on the public token page. Use your team / brand name.
- +
Telegram or Slack handle
For deploy-day support. Optional but recommended.
Decide who your token is, before you mint.
These fields are written into the metadata cell at deploy time. They are immutable for the life of the contract — worth getting right.
- *
Token name
Full human name, e.g. "Aurum Reserve". Up to 32 characters.
- *
Ticker symbol
3–7 uppercase characters, e.g. AUR. Avoid collisions with majors.
- *
Decimals
9 is the TON convention; 6 if you mirror USDT.
- *
Logo (PNG or SVG)
Square, ideally ≤1024px and ≤256KB so Tonkeeper can render it.
- +
One-line description
Shown in wallets that read TEP-64 metadata.
Figure out the supply story before deploy.
Distribution is the part most teams regret post-launch. The contract admin wallet will be your connected Tonkeeper address.
- *
Total supply
Hard cap, in whole tokens. Example: 100,000,000.
- *
Initial allocations
List of recipient wallet addresses + amounts (CSV is fine).
- +
Vesting schedule (if any)
Cliff + duration, per recipient. Linear release only — we do not encode admin overrides.
- *
Mint policy
Capped at deploy, or open mintable by your admin wallet. Capped is the default.
Pick the rail that suits your treasury.
Your Tonkeeper wallet is required even if you pay with PayPal. Operator gas is on us — you only ever pay the flat tier price.
- *
Connected Tonkeeper (via TonConnect)
Required for all tiers — contract admin is set from this wallet.
- +
PLX (-50%)
Pay with PLX and get half off. The PLX you pay is burned at receipt.
- +
USDT (TON jetton)
Settles to treasury — still requires wallet connect in the wizard.
- +
PayPal (USD/EUR)
Best for accounting trails. Wallet connect still required before deploy.
What separates a launch from a great launch.
None of this is required to deploy, but every item below measurably improves how your token is perceived and used after it goes live.
- +
External auditor coordination
Bring your own, or we can route to Trail of Bits / Certik / OtterSec.
- +
Liquidity-pool plan
Stonfi or DeDust pair + initial liquidity amount. We can script the LP creation.
- +
Public docs page
What the token is, who issued it, how to verify the contract. Hosted in your repo or ours.
- +
Telegram or Discord channel
Holders ask questions; you answer them. Helps long-term legitimacy more than a marketing site.
- +
Tonviewer claim
We hand you the verification snippet; you publish it from the issuer wallet so the token shows up as "verified" in wallet UIs.