Launch a QRC20 token from your wallet

What is a QRC20 token?

The QRL 2.0 execution layer is EVM compatible, so it uses the same smart contract token model as other EVM chains. A QRC20 token implements the ERC20 interface: functions like balanceOf, transfer, approve, and totalSupply, plus a Transfer event emitted on every movement. On QRL the standard is called QRC20, and ZondScan labels these contracts QRC-20.

A QRC20 token is itself a smart contract. Your balance is an entry in that contract's storage, and every transfer emits an event that explorers index. That shared interface is why any wallet or explorer that understands the standard can display your token's name, symbol, decimals, and balances without special support.

Smart contracts on QRL 2.0 are written in Hyperion, a close relative of Solidity. If you want to write and deploy contracts yourself, the deploy and verify guide covers that route. This tutorial takes the shortcut: a factory contract that is already deployed writes the token for you.

Before you start

You need three things:

• A wallet account with an imported seed. Token creation signs a contract call directly, so the wallet needs access to your signing seed. Accounts connected through the browser extension or a paired mobile signer cannot create tokens yet; the form tells you so and keeps the submit button disabled. If you are new to MyQRLWallet, follow Create a QRL wallet first.
• Testnet Quanta for gas. Deployment is a normal transaction and burns gas like any other. The ZondScan faucet funds a fresh address in under a minute; see Get testnet Quanta for the walkthrough. The factory itself charges no fee, so gas is the entire cost.
• A name and symbol.Something like "My Test Token" with the symbol "MTT". Both fields are required, and the wallet screens them for offensive language.

Create the token step by step

1. Open the token creator

   Sign in at qrlwallet.com, open the Tokens panel, click the plus button, and choose Create New Token. A form titled "Create New QRC20 Token" appears.

2. Enter the name and symbol

   The name is the full label wallets and explorers display. The symbol is the short ticker shown next to amounts. Both are fixed at deployment, so check the spelling before you continue.

3. Set the initial supply and decimals

   Enter the initial supply in whole tokens; the wallet converts it to base units using your decimals setting. Decimals default to 18, matching the convention on most EVM chains, and the factory caps them at 18. Unless you have a specific reason to change this, leave it at 18.

4. Choose the optional controls

   Four checkboxes reveal extra fields:

   • Mintable. Reveals a Max Supply field. Leave it unchecked and the maximum supply equals your initial supply, which fixes the supply forever. Check it and set a higher max, and you, as the token owner, can mint the difference later. The maximum supply is immutable once deployed.
   • Change Initial recipient. Mints the initial supply to a different Q-prefixed address. By default it goes to your own account.
   • Max Wallet Amount. A cap on how many tokens a single address can hold, checked on every transfer.
   • Max Transaction Limit. A cap on how many tokens can move in one transfer. Both caps are optional, a value of zero disables them, and the owner can adjust them after deployment. The token owner and the initial supply recipient are exempt from both caps, and the owner can exempt further addresses after deployment.

5. Confirm with your PIN

   Enter your transaction PIN (4 to 6 digits) and press Create Token. On the desktop wallet there is no PIN step: the isolated signer authorizes the transaction. The wallet switches to a status page while your token deploys to the chain.

6. Save the result

   When the transaction confirms, the success card shows the transaction hash, the new token's contract address, its name, symbol, and decimals, the block number, and the gas used, denominated in Quanta. The wallet adds the token to your token list automatically. Copy the contract address: it is the one permanent, unambiguous identifier of your token.

Under the hood the wallet calls createToken on the factory contract. The factory deploys a fresh token contract with your parameters, makes your account its owner, and emits a TokenCreated event carrying the new address. The wallet reads that event from the transaction receipt to show you the result.

Find your token on ZondScan

ZondScan indexes new contract deployments and token transfer events as it syncs, so your token appears without any registration step. Open the contracts page and select the Tokens (QRC-20)tab. You can search by token name or contract address. Each row shows the token's name and symbol, contract address, decimals, total supply, creator, and the block it was created at.

Click through to the token's own page. The header shows the name, symbol, and contract address with copy and QR buttons, alongside stats for total supply, decimals, and creator. Two tabs matter most: Holders lists every address with a balance, and Transfers lists every movement of the token. Right after creation you will see one holder, the initial recipient, holding the full supply.

Individual transfers also show up on the transaction pages themselves, decoded with the token's name and amount. The guide on reading a transaction explains every field, including how token transfers differ from plain Quanta transfers.

Shared code and verification

Every token the factory deploys runs the same contract code. The source is published under the MIT license in the QRC20-Factory repository on GitHub. The factory stamps out a fresh instance for each token, so two factory tokens can differ only in their parameters: name, symbol, supply, decimals, caps, and the account that owns them. That predictability is a feature: anyone inspecting a factory token knows exactly what it can and cannot do.

ZondScan's contract pages include a code section with the bytecode and, once source is published, the verified source and a read/write interface. If you outgrow the factory and want custom behavior, write your own contract in Hyperion, deploy it, and publish the source through the verification page. The deploy and verify tutorial walks through that full workflow.

FAQ