How to contribute to Mordor Testnet


Mordor is a PoW Ethereum Classic testnet. A testnet allows developers to perform specific tests. Developers may want to test protocol changes, test a smart contract, or interact with the network in anyway that does not require real EthClassic (ETC)—just don’t test on mainnet, mainnet is for production.


Install Core-geth

Running geth --help will show a plentiful amount of usage and commands. Under ETHEREUM OPTIONS: you’ll see all the Ethereum Classic, Ethereum, and related testnet flags. We need to use the --mordor flag when we rungeth.

Create an account on Mordor

Mordor is a PoW testnet, so we can make an account to mine and receive testnet-ETC. Creating a new account in geth will create a public/private key pair and you’ll be prompted to create a password for that account.

geth --mordor account new

List the account(s)

geth --mordor account list

You’ll notice listing the account will print the keystore file location. For example: keystore:///home/USER/.ethereum/mordor/keystore/UTC...

Run Mordor with Mining Enable

Now, we can run geth, but that would not be meaninful. We need to tell geth to run Mordor, mine testnet-ETC, and of course we'll add some optional connectivity commands/ flags.

Run mordor testnet with mining and rpc enabled. We want to enable mining to mine testnet ETC and enable RPC to access our node.

geth --mordor --miner.extradata "MINERNAME" --mine --minerthreads=1 --etherbase 0x11039699406158d152b5ca1b69d31dd20aae9379 --rpc --rpcport "8545" --port "30303" --rpccorsdomain "*" --nat "any" --rpcapi eth,web3,personal,net

This command will initialize geth to run a --mordor node. We'll provide a short string identifying our miner (or pool) on the network --miner.extradata "NAME", enable --mine and configure the nuumber of CPU threads we want mining --minerthreads=1. Now, we'll specify the mining address --etherbase 0x11039699406158d152b5ca1b69d31dd20aae9379. Geth will send mining rewards to the default account (Account #0) if --etherbase is not defined. Finally, we can add to optional connectivity --rpc --rpcport "8545" --port "30303" --rpccorsdomain "*" --nat "any" --rpcapi eth,web3,personal,net. By enabling RPC we can communicate with our node with other tools and services.

Check Mordor Balance on

So, you’re running a Mordor node and mining testnet ETC. Woohoo! An easy way to double check you’re actually growing a Mordor testnet balance is on Just search the account address you created earlier.

Connect your node to

If you enabled RPC connectivity to your node. You can have Expedition connect directly with your node. This has plenty of benefits for a development enviorment. However, you can use it to determine immeditate node information such as; current block height, chainID, mining stats, etc...

Simply pass your node's RPC endpoint ?rpcUrl=http://localhost:8545 in the url like so:

Add your Mordor Account to a Wallet?

You can use your keystore file to import your wallet into a wallet application such as MetaMask. In MetaMask

  • Select localhost:8545 under network selection. This will connect the wallet to your local Mordor node.
  • Under your account profile select import account > select type (JSON) > upload your keystore file. You may need to enter the account password.

Tip (optional)

One way to avoid typing or copy and pasting this

geth --mordor --rpc --rpcaddr "localhost" --rpcport 8545 --mine --minerthreads 1

is creating a shell script file. touch to create the file && echo “the contents” into the shell script file && chmod +x to add executible permissions.

touch && echo "geth --mordor --miner.extradata "MINERNAME" --mine --minerthreads=1 --etherbase 0x11039699406158d152b5ca1b69d31dd20aae9379 --rpc --rpcport "8545" --port "30303" --rpccorsdomain "*" --nat "any" --rpcapi eth,web3,personal,net" > && chmod +x

Run it


Stop it

Ctrl + C

More Mordor Resources