How it works

You sign,
start to finish

Six steps in the console, then you approve the deploy from your own wallet. Here's exactly what happens at each stage, how many approvals to expect, and what never happens.

The flow

Idea to a mint you own

The console walks you through each of these. Everything stays a draft until the final signature.

Basics

Choose the essentials

Name, symbol, total supply and decimals. Deploys run on Solana and Eclipse and 18 EVM chains. On Solana the console starts from a standard SPL mint with 9 decimals, and on an EVM chain from a standard ERC-20 with 18.

Identity

Add metadata and socials

Logo, description, website and social links. On Solana the name, the symbol and a link to a file holding the rest are written on-chain through the Metaplex metadata program, the record wallets and explorers read to display your token. We host that file and your logo for you. On an EVM chain the token contract holds the name and symbol and points to a document with the rest, which wallets do not read yet.

Authorities

Set your trust flags

Revoke mint and freeze authority so supply is provably fixed and no account can be frozen. These are the signals holders check first. On an EVM chain the one switch renounces ownership, which ends minting for good. All optional, all permanent once set.

Advanced

Plan, but stay transparent

Taxes, transfer limits and pausing are not part of the standard token that gets deployed, on any chain, because they're the mechanics scam tokens use to trap buyers. On Solana a transfer tax is a separate tool, Tax Token, which sets a fee anyone can read on-chain, so it is never switched on by accident here.

Liquidity

Seed the first pool

Turn on the pool plan and the deploy creates the pool itself, straight after the token: on Solana a Raydium pool, whose LP you can lock for 30 days, 90 days or a year, or burn; on Ethereum, BNB Chain, Base, Polygon, Arbitrum, Optimism, Avalanche and Unichain, on mainnet, a pool on that chain's own DEX, whose LP you can burn. Anywhere else you add the first pool yourself afterwards.

Review & deploy

Approve it in your wallet

Review the summary and estimated network cost, then approve in your wallet. On Solana that is three approvals: the mint, the metadata, then your supply with the platform fee and any authorities you chose to give up. On an EVM chain it is one, because the supply, the fee and the renounce ride in the contract's creation. A pool made with the deploy adds up to two more on Solana, and up to four on an EVM chain, which the Review screen lists.

What gets deployed. On Solana, a clean, standard token and no custom contract at all: the mint is created by Solana's own SPL Token program, the same token type every Solana wallet and exchange already understands. On an EVM chain, our own standard ERC-20 contract, the same one for every token: its only owner power is minting, which the renounce switch gives up for good, and it has not been independently audited. Nothing about the deploy can trap, freeze or drain holders beyond the standard, transparent behaviour you configured.

See it in Deploy

Flip the console to testnet and rehearse the whole flow for free before you spend anything on mainnet.

Open Deploy →

You sign,start to finish