Getting Started with dApp Development
This section aims to give developers an idea on how to get started with development on Zilliqa.
We try to make this guide concise, but yet easy enough for a developer with no experience in blockchain development. As many applications developers are
zilliqa-js which we'll be using in our examples.
What are dApps?
Decentralised Apps ("dApps") are applications that interact with smart contracts on the blockchain. As Zilliqa blockchain is a decentralised network that is not hosted by a single entity, application that sits on the blockchain is decentralised.
An application can have a user-facing components ("client"), which could be a web application or mobile app. These applications can interact with smart contracts on the Zilliqa blockchain.
The entry to Zilliqa blockchain lies on the RPC interface. SDKs are not compulsory for you to interact with the blockchain, but they do make your life easier.
0x2 on the entities on the blockchain? Those are addresses.
Addresses are an identifier to an entity on the blockchain. An entity on the blockchain can be either a user or a contract.
Zilliqa currently supports two address formats.
ByStr20: 20 byte hexadecimal string (e.g.
bech32: A bech32 with a human-readable prefix of
The reason behind this design is to prevent confusion with Ethereum addresses. For more detailed explanation on the address, refer to this post
We strongly recommend that developers use
bech32 formatted addresses for token transfers. This prevents users from mistaking Zilliqa addresses from Ethereum addresses. All wallets and exchanges that deal with token transfers currently use the
bech32 standard for security purposes.
ByStr20 checksummed addresses are supported by RPC, SDKs and
How do you know if an address is a smart contract or an account? One way to go about it is to send a
GetSmartContractInit POST request to check.