Janzeer blog ยท
The first token: one transaction type, five operations, and an afternoon on mainnet
Third article of the series. How tokens work on Janzeer, and what happened when the first real one was created on 9 November 2026.
Yesterday was about validators. Today is a detour I did not plan, because something happened on the chain on 9 November that is worth telling while it is fresh: the first token was created on Janzeer mainnet, and every rule the token system has was exercised in one afternoon.
What a token is here
Most chains get tokens from smart contracts: a program holds a table of balances, and "sending a token" means calling that program. Janzeer has no virtual machine, on purpose. Tokens are a native feature of the ledger, specified as one transaction type with an operation byte, called JZT-1. The five operations are create, mint, burn, set cap and transfer.
A token has a symbol, a name, a number of display decimals, a maximum supply (the cap) and an issuer. Its identity is the hash of the transaction that created it, so there is no registry to squat and no name to fight over; two tokens may share a symbol, and the id tells them apart. Every token is its own ledger: minting a billion units of something changes nothing about the fixed 100,000,000 JNZ supply, the treasury or the block rewards. Fees for token operations are paid in JNZ like any other fee.
Three rules give the system its shape:
- Only a registered validator's wallet can create a token. The fee is an exact 5 JNZ. This is a spam gate, not a privilege: anyone who runs a node and pays the 2,000 JNZ deposit described yesterday may issue tokens. An ordinary wallet that tries is refused at submission, before a block is wasted.
- Only the issuer can mint, burn or change the cap, and the ledger enforces two invariants on every path, live or during sync: the supply can never exceed the cap, and the cap can never drop below the minted supply.
- Anyone can hold and send a token. A transfer costs the normal minimum fee of 0.01 JNZ and is final in one block like a JNZ transfer.
What happened on 9 November
I had never created a token on mainnet; the feature had only run in the automated integration test and on the local developer network. So I did it the way a user would, from the web wallet inside the explorer, using the wallet that registered one of my validators.
The result is called DEMO, "Janzeer Demo Token", two decimals, a cap of one million, an initial supply of one hundred thousand. Its page on the explorer shows everything below.
Then I ran through the operations in an order chosen to hit the rules:
- Sent 1,000 DEMO to a second wallet. Transfers from the Python SDK and the TypeScript SDK moved some of it on to two more addresses, final in blocks 221,511 and 221,514.
- Minted 100,000. Supply 150,000.
- Burned 50,000. Supply back to 100,000.
- Tried to set the cap to 100,000 while the supply stood above it. Refused: "cap below the minted supply". No fee, because the node rejects it at the door.
- Set the cap to 200,000. Accepted.
- Tried to mint 60,000, which would have pushed the supply past the new cap. Refused.
- Minted 50,000. Supply 200,000, exactly at the cap.
Every acceptance and every refusal matched the specification. The explorer's token page lists the holders and the operations in order, and the SDKs read the same numbers through REST and JSON-RPC. The whole run is recorded in the project's test guide.
What it cost and what it is worth
Creating the token cost 5 JNZ. The six accepted operations cost 0.01 JNZ each. The two refusals cost nothing.
DEMO itself is worth nothing, and I want to be plain about that. It exists so that the feature has a real example that anyone can look at, send, and build against. It is not for sale, it will not be listed anywhere, and if someone offers you DEMO for money they are not from this project.
What I learned from the wallet
Doing it as a user found two rough edges in the web wallet within minutes, which the test suite could never have shown me. After each operation the Tokens panel kept showing the old balances until I reloaded the page, because the wallet never re-read the chain after a submit, and a transaction lands one or two slots after it is accepted. And the assets list had no way to copy a token id. Both are fixed: the wallet now re-reads the chain every few seconds until the committed state changes, shows a small "waiting for the next block" line while it does, and every asset row has a copy button. They ship with the next node release, since the explorer is built into the node binary.
The mobile wallet, which had tokens switched off since launch, got them back in version 1.2.8 the same evening: a Tokens tab that shows what you hold, a send page with paste, scan and a review step, and receive at your usual address. The issuer operations are one level deeper, behind an "Issuer tools" link, because most people will only ever send and receive.
Try it
The DEMO token is on the explorer, and if you hold a few JNZ for fees any of the five SDKs, the jz command-line client or the wallet can send it. A transfer is about twenty lines in Python:
from janzeer import Account, JanzeerClient, JanzeerRpc, TxBuilder, wait_for_finality
import os
NODE = "https://explorer.janzeer.org"
TOKEN = "a125c23c403f992c36a472050e5709a43b359dda6bc9113e2bc39050ba8a19c6" # DEMO
client, rpc = JanzeerClient(NODE), JanzeerRpc(NODE)
me = Account.from_mnemonic(os.environ["MNEMONIC"])
tx = me.sign_tx(TxBuilder.token.transfer(
sender=me.address, token_id=TOKEN, amount=2500, # 25.00 DEMO, in base units
recipient="0x598b1301acef3baba6ce25e38dd17b723f7b98b1",
nonce=client.nonce(me.address), network_id=client.info()["networkId"]))
client.submit(tx)
final = wait_for_finality(rpc, tx.hash)
print("final in block", final["blockHeight"])
That script, recorded live, is the one-minute token video. The token section of the developer guide has the byte layout and every rule.
Tomorrow we return to the plan: what happens inside those fifteen seconds, and why a committed block is final.
Janzeer is built with AI assistance (Claude Code); every number here is from the live chain, and the text is mine. JNZ is the network's unit, it is not listed anywhere, DEMO has no value, and nothing in this series is financial advice.
Also published on: