When developing contracts on Ethereum Classic, as with any EVM Contract System, it is advised to use a local virtual network, which allows you to quickly iterate without having to wait for blocks to be mined. At some point, though, you may wish to allow the public to interact with a beta version of your application, and for this, a testnet can be used.
As Ethereum Classic maintains compatibility with Ethereum's upstream EVM, other than some minor edge cases, contracts will behave identically. This means that popular Ethereum testsnets can, for the most part, be used for public testing of Ethereum Classic contracts, and because of their popularity this may be preferable for user testing.
Additionally, Ethereum Classic has its own testnets that operate the Ethereum Classic version of the EVM, and deploying to one of these networks is also highly recommended before production release. These public testnets also provide faucets, so you can easily acquire testnet ETC and deploy your code.
If a faucet is not functioning correctly, join the Ethereum Classic Community Discord to ping for testnet funds. Someone in the dev-general chatroom will help you. Alternatively, you can easily mine your own testnet funds by locally running core-geth with the "geth --mordor --mine" command.
You can use chainlist.org to configure your web3 wallet with the appropriate RPC endpoints and explorers. Configure Wallet: Mordor
| Name | Type | Algorithm | Consensus Type | NetworkID | ChainID | |
|---|---|---|---|---|---|---|
| Mordor Testnet | Faucet | Testnet | Etchash | Proof of Work | 7 | 63 |
