Create a token on Solana, without writing code

Token image

or drag the file here

PNG, JPG, GIF, WEBP or SVG · up to 5 MB · goes straight to IPFS.

Name 0/32

Symbol 0/10

This is what shows up in wallets and explorers, next to the balance.

Description 0/500

Total supply

1,000,000 tokens, all of them to your wallet.

What this costs

38bits feethis is what makes the tool free: US$ 0.00
Token depositlocked in your own token; comes back if the account is closed: ≈ 0.003145 SOL
Your account's depositwhere the supply is held: ≈ 0.001514 SOL
Solana network feegoes to the validators, no markup: ≈ 0.000010 SOL
Total leaving your wallet: ≈ 0.004668 SOL

Amounts worked out here from Solana's rent rule. The network node confirms next and the ≈ disappears, with the exact figure on screen before you sign.

None of these amounts is ours. Both deposits are the network's requirement for the accounts to exist and come back to you if they are ever closed; the fee goes to the validators.

Connect to create

Looking for wallets…

The transaction is assembled here and signed inside your wallet. Your key never leaves it.

What happens when you sign

Creates the token with name, symbol and image
Writes the 38bits signature inside the contract
Opens your holder account
Issues the supply to you
Revokes minting, if you asked for it

All in a single transaction: either it all happens, or nothing happens. There is no such thing as a token created without its supply.

What gets written inside the contract

criado_por: 38bits.tech
plataforma: https://38bits.tech
convite: Criado de graça com as ferramentas da 38bits — conheça em 38bits.tech

These are fields of the mint itself. Anyone can read them in an explorer, and they stay there if this site goes offline. They say where the token came from and invite whoever opens it to look at the project. Two extensions are used, MetadataPointer and TokenMetadata: the intersection of what Orca, Raydium and Meteora accept without prior authorisation, so your token is born able to have a pool.

The signature lives in the metadata

The only sign it passed through here, and it lives inside the token itself.

The symbol is whatever you choose, with nothing added: type MEU and the token is born as MEU.

The only mark the tool leaves sits inside the contract: two fields saying who made it, plus an invitation to look at the project. They live in the mint itself, as chain state, rather than in an external file that can go offline. Anyone can read them in an explorer, and they stay there even if this site disappears.

It is the same discipline 38BITS applies to itself: what matters gets written where it does not depend on us. It is described in the whitepaper and verifiable in the transparency record.

What this tool cannot do

Four limits you can check on your own, in an explorer.

We hold no key whatsoever

The transaction is assembled in your browser and signed inside your wallet. Your private key never leaves it.

We keep nothing of your token

The full supply goes to your wallet. There is no transfer to us anywhere in the transaction, and you can check before signing.

Nobody freezes anybody's wallet

The token is born with a null freeze authority. It is not a promise: it is the absence of the key that would make it possible.

Only two extensions, and that is deliberate

MetadataPointer and TokenMetadata, exactly the intersection of what Orca, Raydium and Meteora accept without prior authorisation. They are the two that let name, symbol and fields be written inside the mint itself. A token with an extension outside that list is born unable to have a pool, and the owner only finds out later. This tool does not open the pool: it guarantees your token can have one.