The network
Zilliqa
A public blockchain: a shared, append-only record of transactions maintained by a distributed set of participants rather than one company.
Shared record · distributed participants
Network
The record your wallet reads from.
A wallet is only as understandable as the network underneath it. This page explains Zilliqa in practical terms — what ZIL is, what changed with Zilliqa 2.0, and how a transaction travels from your screen to the shared record.
Fundamentals
Four ideas behind every balance.
Transaction lifecycle
From your screen to the shared record.
Every transfer follows the same path. Knowing it helps you interpret what the wallet shows at each stage.
Stage 1 of 5 — Compose
Start with a clear intention.
A transfer begins as an intention: a recipient address and an amount, reviewed on your screen before anything leaves the device.
- Recipient and amount entered by you
- Network and fee shown before you continue
- Nothing is sent at this stage
EVM compatibility
What "EVM-compatible" means for you
The Ethereum Virtual Machine is a widely used standard for running smart contracts. A network that supports it can run contracts written for that standard and work with tools designed around it.
For a wallet user, the visible effects are simple: addresses use the 0x format, networks are identified by a chain ID, and many applications follow conventions you may already recognise.
Compatibility does not make networks interchangeable. An address on Zilliqa EVM and the same-looking address on a different network are separate contexts. Always check which network you're on.
Network informationMainnet
- Network
- Zilliqa EVM mainnet
- Chain ID
- 32769
- Native token
- ZIL
- Address format
- 0x… (EVM)
- Consensus
- Proof-of-Stake
Compatibility concerns execution and tooling — it does not make networks interchangeable.
Proof-of-Stake
Validators, stake and accountability.
Validators
Operators who run the software that proposes and confirms blocks. They commit ZIL as stake to participate.
Stake
Committed ZIL acts as a security deposit. Validators have a financial incentive to behave correctly.
Delegation
Holders who don't run validators can delegate ZIL to one, adding to its stake. See the staking page.
Finality
Once a transaction is included and confirmed under consensus, it becomes part of the shared record and is generally irreversible.
Addresses
Addresses belong to a network context.
Historically, Zilliqa addresses were displayed in a bech32 format beginning with zil1. On Zilliqa EVM, the 0x format is standard. The same underlying account can sometimes be written either way, but the network you transact on still matters.
Legacy context
zil1x7k9d4m2vq8r0w3n5c6y7te8f2q
bech32 format — seen in older records, exchanges and documentation.
Zilliqa EVM context
0x8f2qC41a9eB307dF62c57a1E
EVM format — the standard on Zilliqa EVM mainnet, chain ID 32769.
A change in how an address is written does not, by itself, move funds. The network you transact on is what matters — always check it before confirming.
Explorers
An independent view of the record.
Block explorers display blocks, transactions and addresses directly from the network. Paste a transaction hash from Zilliqa Wallet into an explorer to confirm its status yourself, without relying on the wallet's display alone.
The hash is the reference: it identifies one transaction uniquely, and anyone can resolve it against the shared record.
FAQ
