Getting HOT Tokens For Testing

Just wanted to post my experience getting HOT tokens, since a few users may be confused if they aren’t too familiar with wallets, Ropsten Test Network and gettting ROP (Testnet version of ETH) on the Ropsten faucet.

I’m a Metamask user (and their Beta Android app is GREAT by the way – try it here), and I’m also experienced using MyEtherWallet (MEW), so for me this process was actually pretty fast.

The full HOT Faucet guide is on the SubstratumNetwork github (link here) but you actually only need the following to make this quick and painless:

  1. ETH Wallet set up with MetaMask plugin on your browser – make sure you are logged into the plugin so it is actively running in backgrounds on your browser
  2. Your Wallet address
  3. 5-7 minutes of time

Here’s my RUN-THROUGH, with links and pretty pictures:

STEP ONE – Get your ROP (Ropsten ETH)

Ropsten is a Test Ethereum network that runs on a duplicate blockchain to real Ethereum.

To get Ropsten ROP, you need to go to the Ropsten Faucet Page and enter in your wallet address of the wallet you want the HOT tokens in for using with Substratum Node (SubNode). Keep in mind that the normal Ethereum and Ropsten Networks run in parallel and the wallet addresses are interchangeable – your wallet will show different balances depending on what network you are viewing them from:
NOTE: always check what network you have activated when you do ANY transactions with your wallet, unless it is a ‘burner wallet’

Copy and paste your wallet address into the Ropsten Faucet window and press “Send me test ether”

VOILA! Within about 60 seconds you will have Test ETH on Ropsten network


This part is a bit technical for some, but with MetaMask and a bit of copy-paste on the MEW classic website, this can be EASY!

Make sure you are logged in to your MetaMask plugin in the browser, and also ensure that POP-UPs are NOT BLOCKED for the site, or else your MetaMask plugin may not appear

First, navigate to the Classic MyEtherWallet page – as a general rule, always type out the URL for this and don’t trust any links online to navigate to this page – you could get Phished!

Go to (don’t trust, VERIFY 😉 )

Double check that Gas Price is set to 1 Gwei, and the Network is selected as Ropsten

  • Click on the Contracts tab.
  • Copy the HOTSwap contract address:
    0x1D735051A431c06185927C27AEcea99520634832 and paste it in the “Contract Address” field
  • Also copy the buyTokens() JSON Interface text:
  • [{"constant": false, "inputs": [{"name": "beneficiary", "type": "address"}], "name": "buyTokens", "outputs": [], "payable": true, "stateMutability": "payable", "type": "function"}]
  • Paste it in the “ABI / JSON Interface” field.

It should look like this:

  • Click the Access button
  • When presented with the “Select a function” drop-down, select buyTokens.
    See the image below
  • Selecting buyTokens will expand the form to reveal a “beneficiary” address field. Enter the wallet address from which you will send test Ether (ROP). This the same address you used in STEP ONE to Get Your ROP above.
  • Scroll down slightly – you should now see this area of the page about how to access your wallet.

Click “Connect to MetaMask” – don’t worry as the screen doesn’t change much, but the Access options may disappear

Now click the blue “Write” button – a window will appear to ask you how much ROP you want to send to the buytoken function. Each ROP will buy 5000 HOT tokens. Remember there are still gas fees, so hold back a small fraction of ROP to make sure there is enough. The Gas Limit will usually fill in a number automatically.

Click “Generate Transaction” – the windows expands showing the raw and signed transaction data.

Verify everything looks correct and then click “Yes, I am sure! Make transaction”

A Pop-Up windows will open from your MetaMask plugin, where you can confirm the transaction. When you click the green “SUBMIT” button it will submit the transaction to the blockchain and the smart contract will convert your ROP into HOT tokens!

And that is that! In about 2 minutes (depending on network congestion and your gas limit) you should see the HOT tokens.

Don’t forget to add ‘Custom Token’ in your MetaMask plugin so you can view the token balance for HOT.

The token address is: 0xcd6c588e005032dd882cd43bf53a32129be81302
And you can find it on at this link

Not so hard if you use MetaMask and these instructions 😉

Exciting New Wiki Update 30-Jul-19

Greetings SUB-Nation!!

A lot of background work has been going on from the Development team of Substratum which is absolutely exciting!

At the same time, we are building out the Substratum Wiki website with new features to help support the Community.

The Community has been absolutely amazing with their support and contributions so far!

Here are a number of exciting updates – please get involved everyone!:

  • The Community has already started asking about contributing to support the Wiki site! – we have set up a Public ETH address to help support the website hosting and other initiatives.
  • Our Wiki site is now a verified Brave Publisher! Many of us really love the whole Brave project and their browser is great! You can now tip BAT to the Wiki site and help support our content. If you aren’t already using the awesome browser, click this link to download and further support both Brave and the Substratum Wiki
  • We have set up a Community Forum page and built out that feature, so you can both register to our Blog and also start to participate in the Forum to get help on the Testing, Roll-out and use of Substratum Node and more!

None of this is possible without all of you, so special thanks to the following people who really helped me out in the last week:

Wernigerode, Stu G, ToddMeow, BrianM, Microoo, Isabel Beebe and any others I may have forgotten!

Subscribe to our Wiki to get Updates!

How to Build a Node on CentOS

Instructions for setting up a Build Environment on CentOS for compiling SubstratumNode to run in CLI mode

  1. Install CentOS 7.6
  2. Do all system updates
    sudo yum -y update
  3. Do a reboot
    sudo yum reboot
  4. Set the TimeZone so the logfiles show the correct date and time, example:
    sudo timedatectl set-timezone America/New_York
  5. Install dependencies part 1
    sudo yum -y install git openssl-devel
  6. Install dependencies part 2
    sudo yum -y groupinstall "Development Tools"
  7. Install Screen utility. This is optional, but very useful for keeping SubstratumNode running and disconnecting your terminal
    sudo yum -y install screen
  8. Install Rust environment
    curl --proto '=https' --tlsv1.2 -sSf | sh
    source $HOME/.cargo/env
    rustup component add rustfmt
  9. Clone the SubstratumNode repo
    git clone
  10. Build the binaries
    cd SubstratumNode

    Building will take some time. ~15 minutes on a 1 CPU system

    Configuring and Running the node will be covered in another post

The Safe Maker – unlocking wallet dynamics?!

Have you sat there confused about wallets, mnemonic passphrases, seed words, public and private keys – all the jargon around blockchain – and felt your head about to explode?

Well you aren’t the only one! Thankfully after a number of years in the crypto scene, many hours of reading and questioning a few developers, I think I’ve found a way to simplify things with a pretty good analogy!

Hopefully after this read you will have a good understanding of what all these components do, and how they behave together on blockchain.

For the sake of simplicity as well, we will take away the concept of sharing the wallet address publicly so others can anonymously deposit money – I think many people do understand the blockchain concept that a wallet address does not reveal who the owner is, and also won’t reveal the private key or other details.

We are going to call this the Safe Maker Analogy

Safe maker

For this analogy, let’s say this expert Safe Maker’s name is Ian Coleman (the creator of this awesome BIP39 generator that shows how these components interact to create mnemonic codes).
Ian is an expert in making Safes (the kind that have a barrel dial on the front which locks with a combination) with various different qualities.

Customers contact him and ask him to make custom Safes that cannot be replicated, and also are impossible to open without the correct information.

In making these Safes, Ian uses a variety of components and choices to make these unique, and also to ensure that his customer is the only one who can access the safe (even after he makes/gives it to the customer) – BUT most importantly the customer can contact Ian with certain parts of the information about the Safe and it can be unlocked or recreated in some situations.

While making the Safes, Ian also creates them in a variety of shapes (square, rectangle, circular etc) using moulds with different code names, stamps the Safes with a unique serial number and matches that serial number to the Safe unlocking combination using a special calculator.

So here it goes:

Mr Nakamoto wants to get one of these legendary Safes so he can deposit crypto Gold bullion (Also known as Bitcoin) and leave it for his grandchildren to inherit. He calls Ian Coleman the Safe Maker.

Ian tells Mr Nakamoto, that he is happy to do this and explains that Mr Nakamoto needs to take special precautions to ensure that his Safe can be unlocked, if anything should happen to him or his Safe.

Ian organizes Mr Nakamoto to meet at his Workshop and tells him to pick 12 metal ingredients at random from the Periodic Table, and write them down on a piece of paper – this is the Mnemonic Seed Phrase. Ian in this situation cannot lie or cheat, and sadly he also has a rare form of extreme forgetfulness, that erases how he made each Safe once he is finished! So Ian lets Mr Nakamoto know that after he mixes these metals and uses it to make the Safe, he forgets the recipe and destroys any record of how he made it.
Most importantly, Ian also explains that Mr Nakamoto CANNOT lose or forget this recipe of 12 ingredients in exact order, or he will not be able to help Mr Nakamoto if he forgets how to unlock the Safe.

To further make this more secure, Ian gives Mr Nakamoto the option to pick a 13th ingredient without Ian watching, and mix it into the other 12 ingredients – this is the Mnemonic passphrase. Whether or not Mr Nakamoto does this, the recipe for the Safe has now been created.

Before pouring the metal into one of his special Safe moulds, Ian gives Mr Nakamoto a briefcase with a combination lock on it, which he can keep the metal recipe safe (remember, this is the Mnemonic Seed).
This keeps the metal recipe and the 13th ingredient extra secure for Mr Nakamoto, so even if he lost the briefcase containing the recipe copy, it cannot be accessed – this briefcase combination is the Encryption Password.

As Ian pours the metal mixture into a specific mould, he tells Mr Nakamoto that this mould has a unique code to identify it. Other customers may get a Safe made from the same mould, but each Safe is still unique despite being the same shape and dimension – one of these moulds is known as the derivation path.

Once the metal forms and sets, Ian brings out a special calculator he created (see again his Mnemonic code generator) and enters in the 12 metal recipe in exact order. He also asks Mr Nakamoto to enter in his 13th ingredient if he picked one. Lastly, Ian enters the code on the mould he used to form the Safe. The special calculator gives Ian two unique character sequences and a printed receipt:

Note: when we are stating that a sequence is created, keep in mind that in the crypto realm, this is a combination of alpha/numeric characters

  1. The first number is a serial number that is etched onto the front of the Safe – this is the Wallet Address
  2. The printed receipt is signed by Mr Nakamoto showing he owns the safe, and it is glued to the bottom of the safe out of view – the is the Public Key
  3. The second number is the combination to unlock the safe itself – this is the Private Key

(Note this is how the Ian Coleman “Mnemonic Code Converter displays the outputs)

Before the extreme forgetfulness sets in for Ian, he firmly reminds Mr Nakamoto that he should also store the combination to the Safe somewhere where no one can find it, or memorize it himself.

Now you may be asking yourself, why does Ian make Safes this way?

Well, here are a number of dynamics that will help this all fit together:

  • Due to his rare Alzheimer’s Ian forgets everything about the creation of the Safe – the only way he can make that exact safe again is if Mr Nakamoto returns with the 12 metal ingredients in exact order, and a 13th ingredient if he picked one, and also points out what mould his Safe was made from! – the mnemonic seed, mnemonic passphrase and derivation path
  • Ian will have to use this unique recipe to replicate the Safe, but without it, it can never be remade.
  • If Mr Nakamoto forgets the combination to his safe, he can contact Ian and use his special calculator to generate his combination again if he provides the mnemonic seed, passphrase and derivation path – but only Mr Nakamoto knows this information
  • As long as Mr Nakamoto doesn’t forget his Safe combination, no one else knows how to unlock it, and no one can make the exact same Safe either
  • The serial number (wallet address) on the Safe lets an onlooker know it’s uniqueness, but not how to unlock it
  • The signed receipt (Public Key) on the bottom is not normally seen by any onlookers, and proves that Mr Nakamoto owns the unique Safe and the serial number, but cannot be used to unlock the Safe.
  • If someone steals the Safe, none of the visible information helps them unlock it. Even if they stole the briefcase Mr Nakamoto has with the recipe of how its made – remember the briefcase is locked with a combination (Encryption Password)


Hopefully this sheds some light on how the different parts of cryptography tie together with Mnemonic code and key pairs in the blockchain space!

Feel free to keep up with our Blog and Community Content:

“From the Community, For the Community”

Summary of Terms Used for the Safe-Maker

  • Mnemonic seed phrase = Safe metal recipe – 12 random metal ingredients
  • Mnemonic passphrase = extra 13th ingredient
  • Encryption Password = briefcase combination lock code for the metal recipe
  • Derivation Path = Mould of Safe
  • Wallet Address = serial number on safe
  • Public key = signed receipt on bottom of safe
  • Private key = combination to unlock safe

Here is another resource which helps distinguish between the differences between Public Key and Wallet address, that helped me:

What is the difference between the Public Key and Wallet Address?

TLDR; Private Keys produce Public KeysPublic Keys produce Wallet Addresses… However, Wallet Addresses cannot be used to produce/reveal Public KeysPublic Keyscannot be used to produce/reveal Private Keys.