# How To: Launch a Token on Verus

Create your own currency token using the Verus DeFi protocol.

Estimated time: 15–20 minutes
Cost: ~200 VRSCTEST (testnet) or ~200 VRSC (mainnet) for currency definition
Difficulty: Intermediate

• Verus CLI installed and daemon fully synced
• A registered VerusID with the name you want for your token (create one first)
• ~200 VRSCTEST/VRSC in your wallet for the definition fee
• The VerusID must NOT already have an active currency defined on it

./verus -testnet getidentity "YOUR_TOKEN_NAME@"

The identity name will become the token name.

./verus -testnet getcurrency "YOUR_TOKEN_NAME"

Should return an error like Currency not found. If it returns data, this ID already has a currency.

You control minting and burning. Good for loyalty points, project tokens, platform currencies.

./verus -testnet definecurrency '{
  "name": "YOUR_TOKEN_NAME",
  "options": 32,
  "proofprotocol": 2,
  "idregistrationfees": 0.01,
  "idreferrallevels": 0,
  "preallocations": [{"YOUR_ID@": 1000}]
}'

Flags explained:

• options: 32 — TOKEN type
• proofprotocol: 2 — Centralized (you can mint/burn)
• idregistrationfees — Cost for sub-identities under this namespace
• idreferrallevels: 0 — No referral rewards for subIDs
• preallocations — Tokens minted to specified identities at launch

No one can mint after launch. Supply is set by preallocations only.

./verus -testnet definecurrency '{
  "name": "YOUR_TOKEN_NAME",
  "options": 32,
  "proofprotocol": 1,
  "idregistrationfees": 0.01,
  "idreferrallevels": 0,
  "preallocations": [{"YOUR_ID@": 1000000}]
}'

An automatically-managed liquidity pool backed by reserve currencies.

./verus -testnet definecurrency '{
  "name": "YOUR_TOKEN_NAME",
  "options": 33,
  "currencies": ["VRSCTEST"],
  "weights": [1.0],
  "initialsupply": 100000,
  "initialcontributions": [1000],
  "idregistrationfees": 1,
  "idreferrallevels": 3,
  "preallocations": [{"YOUR_ID@": 10000}]
}'

Additional flags:

• options: 33 — FRACTIONAL (1) + TOKEN (32)
• currencies — Reserve currencies backing the basket
• weights — Relative weight of each reserve (must sum to 1.0, minimum 0.1 per reserve)
• initialsupply — Total supply after initial contributions convert
• initialcontributions — Amount of each reserve deposited at launch

Expected output:

{
  "txid": "abc123...",
  "tx": { ... },
  "hex": "0400..."
}

./verus -testnet gettransaction "YOUR_DEFINITION_TXID"

Wait for at least 1 confirmation for the definition tx to be mined. Then wait a minimum of 20 blocks (~20 minutes) for the currency to become active and usable. During this launch period, preconversions can occur for basket currencies.

./verus -testnet getcurrency "YOUR_TOKEN_NAME"

Should show your token definition with supply, options, etc.

If you used proofprotocol: 2, you can mint additional tokens:

./verus -testnet sendcurrency "YOUR_TOKEN_NAME@" '[{
  "address": "RECIPIENT_ADDRESS_OR_ID",
  "amount": 500,
  "currency": "YOUR_TOKEN_NAME",
  "mintnew": true
}]'

⚠️ The fromaddress must be the token's controlling identity (e.g., "YOUR_TOKEN_NAME@").

./verus -testnet sendcurrency "*" '[{
  "address": "recipient@",
  "amount": 10,
  "currency": "YOUR_TOKEN_NAME"
}]'

Options are combined by adding values:

Common combinations:

• 32 = Simple token
• 33 = Fractional basket token (32 + 1)
• 40 = Token with ID referrals (32 + 8)
• 256 = PBaaS chain (base)
• 264 = PBaaS chain with referrals (256 + 8)

• Definition fee: ~200 VRSC (same as testnet equivalent)
• PBaaS chain definition: ~10,000 VRSC
• Test on testnet first — currency definitions are permanent
• Once a currency is defined on an identity, it cannot be redefined

Last updated: 2026-02-07