Documentation
  • INTRODUCTION
  • USERS
    • White Paper
    • Main features of CyberWay
    • Bandwidth differences between EOS and CyberWay
    • Bandwidth implementation
    • How to Launch EOS dApps on CyberWay
    • Glossary
  • DEVELOPMENT ENVIRONMENT
    • Core Concepts
    • 1 Before You Begin
    • 2 Install the CDT
    • 3 Create Development Wallet
    • 4 Start keosd and nodeos
    • 5 Create Test Accounts
  • SOFTWARE MANUALS
    • Core
      • nodeos
      • cleos
      • keosd
      • cyberway.cdt
    • How To Guides
      • How To Ban An Unwanted Account
      • How To Calculate Reward For An Author
      • How To Calculate Reward For A Beneficiary
      • How To Calculate Reward For A Curator
      • How To Create A Wallet
      • How To Create An Account
      • How To Create A Proxy Account
      • How To Create Key Pair
      • How To Delegate Resources
      • How To Deploy A Node Using A Snapshot
      • How To Deploy A Smart Contract
      • How To Get Account Information
      • How To Get Block Information
      • How To Get Transaction Information
      • How To Import A Key
      • How To Link Permission
      • How To List All Key Pair
      • How To Stake Tokens
      • How To Stop A Node Using Docker
      • How To Submit A Proposal For HardFork
      • How To Transfer Tokens To A Worker
      • How To Undelegate Resources
      • How To Unlink Permission
      • How To Unstake Tokens
      • How To Vote
    • API Reference
      • Nodeos Chain API
      • Nodeos Producer API
      • Nodeos Net API
    • Cleos Command Reference
      • Convert
      • Create
      • Get
      • Multisig
      • Net
      • Push
      • Set
      • Sign
      • System
      • Transfer
      • Version
      • Wallet
    • Explorer Command Reference
      • How To Check Your Balance
      • How To Find Out Account ID
      • How To Convert Golos To Golos Power And Vice Versa
      • How To Stake Tokens CYBER
      • How To Transfer Funds From One Account To Another
      • How To Transfer Funds From Pending to Liquid
      • How To Bay Stake
      • How To Withdraw Stake
      • How To Vote For A Validator
      • How To Revoke Your Vote For A Validator
      • How To Bay Vesting Using Explorer
      • How To Vote For A Witness
      • How To Revoke Your Vote For A Witness
  • DEVPORTAL
    • System Contracts
      • BIOS
      • Domain names
      • Govern
      • Multi-Signature
      • Stake
      • Tokens
    • Application Contracts
      • Golos Contracts
        • Charge
        • Control
        • Emission
        • Publication
        • Referral program
        • Social
        • Vesting
        • Memo-keys
        • Determining Rewards for a Post
    • Guide to Creating and Deploying an Application on CyberWay
      • 1 Preliminary Work
      • 2 Creating a Simple Contract
      • 3 Creating Tokens
      • 4 Understanding ABI Files
      • 5 Data Persistence
      • 6 Secondary Indexes
      • 7 Adding Inline Actions
      • 8 Inline Action to External Contract
      • 9 Conclusion
    • The cyberway_wallet designed for the Bittrex market
    • The Event Model
  • VALIDATORS
    • Testnet Installation Guide
      • 1 General
      • 2 Configuring the Docker Image
      • 3 Create Container
      • 4 Connecting to a Node
      • 5 List of Commands Applicable to Any Kind of Container
    • Mainnet Connection Guide
      • Docker-Compose Start-up Instructions
      • APPENDIX A
      • APPENDIX B
    • Golos Blockchain Transit
    • How to join CyberWay for those who are interested in being validators ?
    • Stake Usage Guide
    • Regulations for CyberWay validators. Voting for Validators
Powered by GitBook
On this page
  • Step 1: Prepare server
  • Step 2: Clone CyberWay repository
  • Step 3: Run the shell-script
  1. DEVELOPMENT ENVIRONMENT

1 Before You Begin

We appreciate your interest in contributing to the CyberWay platform! We always welcome contributions from our community to make our code and docs better.

This section provides guidance on how to install the CyberWay binaries on your server. To do this, you need to:

  • Prepare server

  • Clone CyberWay repository

  • Run the start_light.sh script.

Step 1: Prepare server

The server where CyberWay binaries are installed, must meet the following characteristics (or above):

  • RAM size (a min. of): 8 GB

  • disk space (a min. of): 20 GB

One of the following operating systems must also be installed on the server:

  • Ubuntu 16.04

  • Ubuntu 18.04

  • MacOS Darwin 10.12 (or later versions)

  • Centos 7

  • Fedora 25 (or later versions)

  • Mint 18

WARNING If you have a private key, it is strongly recommended to save your private key before proceeding.

If you have previous version of CyberWay installed on your system, please uninstall it before proceeding.

Step 2: Clone CyberWay repository

Create a directory where you will upload sources and clone CyberWay repository:

mkdir ~/cyberway.launch
git clone https://github.com/cyberway/cyberway.launch  ~/cyberway.launch

Step 3: Run the shell-script

Please, NOTE The script performs an installation and deployment of CyberWay on your server in automatic mode. By running the script, you connect your server to running block chain.

Go to the created CyberWay space and run the start_light.sh script:

cd ~/cyberway.launch
 ./start_light.sh

Configuration file, genesis data (a snapshot of CyberWay system state) and docker file should appear on your server:

  • /etc/cyberway/config.ini

  • /var/lib/cyberway/genesis-data/genesis.json

  • /var/lib/cyberway/genesis-data/genesis.dat

  • /var/lib/cyberway/docker-compose.yml

During the script execution, the following operations are done:

  • creating the environment for CyberWay configuration on the server;

  • downloading the Docker image;

  • downloading the CyberWay genesis, including the files genesis.json and genesis.dat;

  • creating Docker volumes to store the system state database and chain data;

  • start the services nodeosd and mongo. Setting up these services occurs by docker-compose.yml.

The script runs the current version of CyberWay with the genesis data uploaded which is used as input. Successful completion of the script means a successful server connection to Mainnet as a seed-node.

If you followed all the instructions given in that Appendix A and made sure that your server is fully synchronized with Mainnet, that meant that the server connected to Mainnet as a seed-node.

PreviousCore ConceptsNext2 Install the CDT

Last updated 5 years ago

The procedure for checking a connection of your server to Mainnet as a seed-node is given in .

Appendix A