Installing Rise Testnet on Ubuntu 16.04


  • administrator

    Installing Rise Testnet on Ubuntu 16.04


    Port Reference


    Mainnet
    HTTP: 5555
    HTTPS: 5556
    
    Testnet
    HTTP: 5566
    HTTPS: 5567
    

    This article will guide you through the installation of a Rise testnet node. To receive the required RISE and get voted into testnet, Sign Up or Sign In on the Rise Slack and ask in the #testnet channel.

    Testnet Wallet

    Testnet Explorer

    Prerequisites


    After preparing your server with the Initial Server Setup with Ubuntu 16.04 guide, you can now install Rise Testnet on your server. To complete this tutorial, you will need:

    • One Ubuntu 16.04 server set up by following the Ubuntu 16.04 initial server setup guide, including a sudo non-root user and a firewall.
    • A wallet with a second passphrase and at least 25 Test RISE
    • Find your own public IP here
    • To have the en_US.UTF-8 locales generated:
    sudo locale-gen "en_US.UTF-8"
    

    Installation


    1. First of all you’ll need to login into your server with the username you created in the Ubuntu 16.04 initial server setup guide:
    ssh -p ssh_port username@your_server_ip
    
    1. Automatic install script for Debian based systems Ubuntu, Mint, Debian to install Rise (Testnet)
    cd $HOME
    
    wget -q -O RISEcommander.bash "https://downloads.rise.vision/commander/testnet/RISEcommander.bash"
    
    chmod +x RISEcommander.bash
    

    Then start the commander with this line and choose option 1:

    ./RISEcommander.bash
    
    1. For the next step, change to the newly created rise-node folder and start your node:
    cd rise-node
    
    ./rise_manager.bash start 
    
    1. Rise Testnet is now installed. However, you’ll need to modify the config.json to your own values.
    nano config.json
    

    Edit the “api “part by replacing the dummy IP 1.2.3.4 shown in the example with your own public IP:

    "api": { 
        "enabled": true,  
        "access": { 
            "public": false,  
            "whiteList": ["127.0.0.1", "1.2.3.4"] 
        }
    }
    

    After that, edit the “forging” part by replacing the dummy IP 1.2.3.4 once more and replacing [“secret secret …”] with your first passphrase (the 12 words you use to login). It is important that you keep the same format as shown [] with quotation marks:

    "forging": { 
        "force": false, 
        "secret": ["secret secret secret secret secret secret secret secret secret secret secret secret"] 
        "access": { 
            "whitelist": ["127.0.0.1", "1.2.3.4"] 
        } 
    }
    

    After editing the file press Ctrl+O and confirm with Enter. Now exit nano with Ctrl+X.

    1. To apply the changes made in the config.json, make sure to always reload Rise:
    ./rise_manager.bash reload
    
    1. Since your node has to catch up with the blockchain, rebuild it with a verified snapshot to speed this process up:
    ./rise_manager.bash rebuild
    

    To make sure your node is alright, open http://yournodeIP:5566. It should show you the Rise Wallet UI. When your node is done syncing, it is ready to forge blocks. However, you’ll need to register your delegate now. Otherwise no one can vote for you and therefore start forging blocks.

    Registration


    Note: Registration should not take place on your own node, unless you have setup HTTPS properly. Otherwise your first and second passphrase will be sent unencrypted over the network, thus making it very easy for anyone to steal your coins!

    Login into your wallet over a secure and trusted node, such as the official wallet.

    1. After logging in, click on “Forging”.

    2. Now click on “Delegate Registration”.

    3. Type in the name of your delegate and send the registration fee. If you have setup a second passphrase, it will ask you for it.

    By Nytrobound, licensed under CC BY-NC-SA 4.0


Log in to reply
 

Looks like your connection to     Rise Community Forum was lost, please wait while we try to reconnect.