Get Testnet IOTX Tokens
Last updated
Last updated
This documentation portal is currently undergoing updates to align with the IoTeX 2.0 Whitepaper release. Information provided here may be incomplete, or out-of-date. Please use this portal for preliminary reference only, and check out the official IoTeX 2.0 Whitepaper for updated information.
.2024 | IoTeX
The IoTeX testnet is a separate network from the mainnet, although it has equivalent functionalities, including the presence of an 'IOTX' token along with XRC20 tokens.
The IoTeX testnet is frequently reset and is susceptible to bugs during the deployment of beta releases of the blockchain. Since testnet wallet balances and smart contract balances can be reset or wiped out at any time, test tokens do not hold any real 'value.'
Testing dApps functionalities consumes IOTX tokens, which can become very expensive if you develop on the IoTeX mainnet directly. The IoTeX mainnet is used for real-value transactions involving tokens with actual value.
If you develop or test your contracts directly on the mainnet you not only consume gas fees when running transactions but also risk potential serious monetary loss due to any bugs or mistakes.
As blockchain developers, it's advisable to use the IoTeX testnet for your development. Here, any dApp can be deployed to a production-like network where tokens don't have any real value.
It's important to note that testnet IOTX tokens are not tradable on exchanges, serving exclusively as a valuable tool for development and testing.
The best way for any developer to have access to testnet IOTX is to create a developer account on the IoTeX Developer Portal and claim test tokens in their personal profile. Simply connect your wallet on IOTX testnet and start claiming test IOTX immediately.
Another way to obtain test IOTX tokens for users that may need them for different purposes, other than developing, is to request them on the IoTeX public faucet:
Another option to get some test IOTX tokens is to join our Discord Server and ask an admin in the #developers-chat channel:
