Test Net Setup

To connect to the Test Net, we’ll add a new network to the truffle-config.js, and to make things simple we’ll use the mnemonic passphrase from your local Ganache.

The example repo for this section is at:


We’ll be using the code at tag “client-initial” for now.

1. Get Your Mnemonic Passphrase

This isn’t real crypto of any value so don’t worry about security for now. When you started Ganache you should see:

HD Wallet
Mnemonic:      word1 word2 ...

Copy paste that mnemonic into a secrets.json file and add it to the top of the truffle-config.js.


  "mnemonic": "word1 word2 word3 ..."

Remember to npm install --save @truffle/hdwallet-provider the HDWallet Provider too.

const secrets = require('./secrets.json')
const HDWalletProvider = require('@truffle/hdwallet-provider');
const mnemonic = secrets.mnemonic

Basically now you should have the same addresses on the TestNet as you had locally.

2. Add the Elastos ETH Sidechain Testnet Network Config

Now in the networks section you want to add the elaethTest network:

elaethTest: {
  host: 'https://rpc.elaeth.io',
  port: 8545,
  network_id: '*',
  provider: () => new HDWalletProvider(
    mnemonic, 'https://rpc.elaeth.io'
  gasLimit: 8000000,
  gasPrice: 1000000000

You can double check the example repo here: https://github.com/crregions/ela-eth-sidechain-doc/tree/client-initial

3. Test the Connection, Check Addresses and Get Test ELAETHSC

Test with the console again, this time ensure you specify the correct network.

| => truffle console --network elaethTest
truffle(elaethTest)> accounts
[ '0x243C7B804a1CB650c3f584FaC5e33FdB61Cd26CE',

You should notice your accounts are the same too since we used the same mnemonic. In my case I have my first address ending in "…26CE”, this is what I want to send test cryptocurrency to, but all of the listed addresses are yours and linked to the mnemonic passphrase.

On Elastos we call ETH by ELAETHSC

For Elastos ETH Sidechain, as a EVM network we are designated as chain ids 20 & 21, with the short name ELAETHSC - https://chainid.network.

This works the same as ETH does on Ethereum, which means it’s also used for gas. Therefore we need to have ELAETHSC in order to deploy smart contracts and send transactions.

For the testnet you can get free “test” ELAETHSC.

Go to: https://faucet.elaeth.io, enter your address and it will send you 1 ELAETHSC for testing.

Note this is just the TestNet so it’s not real cryptocurrency.

4. Deploy a Simple Storage Smart Contract

Now let’s create a very basic smart contract which we’ll build on in the next two tutorials.


pragma solidity >=0.4.22 <0.7.0;

 * @title Storage
 * @dev Store & retrieve value in a variable
contract Storage {

    uint256 number;

     * @dev Store value in variable
     * @param num value to store
    function store(uint256 num) public {
        number = num;

     * @dev Return value
     * @return value of 'number'
    function retrieve() public view returns (uint256){
        return number;

This simple smart contract allows you to store and retrieve a number.

Notice how the store function doesn't return anything.

Changing state on the chain requires that the transaction gets accepted and confirmed, this means that these methods act like Javascript asynchronous functions, but can have no return. Although we can await the "sendTransaction" it will only return the transaction hash.

Read more here: https://web3js.readthedocs.io/en/v1.3.0/web3-eth-contract.html#methods-mymethod-send

Now hopefully you’ve learned how Truffle works, if not please read up here:

You’ll be adding a second step to the migration:


const Storage = artifacts.require("Storage");

module.exports = function(deployer) {

Now assuming you have test ELAETHSC, you should be able to deploy it to the Elastos ETH Sidechain TestNet.

| => truffle migrate --network elaethTest

Compiling your contracts...
> Compiling ./contracts/Migrations.sol
> Compiling ./contracts/Storage.sol


Migrations dry-run (simulation)


Starting migrations...


Migrating 'Storage'
   > transaction hash:    0x246068657b7c4aa079fca053f98ac8db72c4fc7c9573568e5933a47b9c0a072a
   > Blocks: 0            Seconds: 9
   > contract address:    0x654Ff88970F04B8C2A75dfeEB0B133dE8024c671

> Total deployments:   2
> Final cost:          0.000340896 ETH

All of this should take a minute or two, when it’s done you can verify it worked by checking the TestNet explorer:

Where you should see your most recent contract deployments and transactions.

But what does this really mean?

Your smart contract is now on-chain at the contract address shown under the 'Storage' contract address.

Now search for that contract address and you should see something like this:

This shows your smart contract on the testnet accessible at that smart contract address.

5. Interacting with your Smart Contract

There are three general ways to interact with your smart contract:

1. A Command Line Tool (CLI) like truffle console

2. Via a programmatic script or process, usually this is used by tests

3. A client-side dApp that works with your smart contracts

Tutorial 1: Interacting with Smart Contracts

Let's walkthrough these 3 general ways to connect with your newly created Storage contract.