Helios Protocol Node
This is the beta stage of the HeliosProtocol node. It is currently under active development and is not yet complete.
Install
Py-helios-node install instructions:
Make sure you have the correct version of python installed. The version is listed at the top of this document. Caution: do not upgrade your system python from 2 to 3 as this can cause massive problems. Instead, we recommend installing a new version of python using pyenv. To install pyenv, use the setup script found here. For completeness, we will summarize the current setup steps here:
Install
$ curl -L https://github.com/pyenv/pyenv-installer/raw/master/bin/pyenv-installer | bashEdit .bashrc
$ vi ~/.bashrcadd the lines
export PATH="~/.pyenv/bin:$PATH" eval "$(pyenv init -)" eval "$(pyenv virtualenv-init -)"Reload .bashrc
$ source ~/.bashrcInstall python 3.6
$ pyenv install 3.6.5
Install git
$ sudo apt install gitor
$ sudo yum install gitClone this repo
$ git clone https://github.com/Helios-Protocol/py-helios-nodeSet python environment
$ cd py-helios-node $ pyenv local 3.6.5Install the Helios Node
$ pip3 install -e .Ensure that the slow version of RLP is uninstalled, and install a fresh copy of the fast one. This will force all external libraries that use RLP to switch to the fast one.
$ pip3 uninstall rlp $ pip3 uninstall rlp-cython $ pip3 install rlp-cython
Configure
The Helios Protocol consensus mechanism is partially based on PoS. This requires that all nodes are associated with a wallet address that has a non-zero stake in order to run. So at this point, you have to configure the node software to use your wallet as a source of coins to stake.
Create keystore file. This is an encrypted file that stores your private key. You will be able to create this with our wallet when it is released. But for now, you can just create a new wallet using MyEtherWallet, then save the wallet file. This file will work with Helios Protocol.
Place keystore file within the directory helios/keystore
Configure node to use your keystore file. Copy helios/helios_config.template.py to helios/helios_config.py. Then edit the new file and tell it the filename of your keystore file to use.
Open Ports in Firewall
The node software needs to have an open path for communication with other nodes on the network. If you have firewall software enabled, such as iptables, then you might have to open some ports to ensure this. The default installation of Ubuntu and Debian probably already have the ports open. Other distros such as Centos likely have most ports closed by default.
Debian and Ubuntu
$ sudo iptables -I INPUT -p tcp -m tcp --dport 30303 -j ACCEPT
$ sudo iptables -I INPUT -p tcp -m tcp --dport 30304 -j ACCEPT
$ sudo iptables-save
Centos 7
$ sudo firewall-cmd --permanent –zone=public --add-port=30303/tcp
$ sudo firewall-cmd --permanent –zone=public --add-port=30304/tcp
$ sudo firewall-cmd --reload
Start the node
$ helios
Then enter your keystore password when prompted. This password is never saved, it is only used to initially decrypt your keystore file.
This document is still a work in progress. More details will come soon.
Metadata
Release files for py-helios-node 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| py-helios-node-0.3.0.tar.gz | 390.7 kB | Without provenance | Details for py-helios-node-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| py_helios_node-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for py_helios_node-0.3.0-py3-none-any.whl |
Total release size: 912.7 kB
Release files / py-helios-node-0.3.0.tar.gz
| Download URL | py-helios-node-0.3.0.tar.gz |
|---|---|
| Size | 390.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c421f5b8c8a3b526bfac3c1b80cba52f9e14fb71a68918dd28bf6e9916ee30f1
|
|
BLAKE2b-256 checksum How to use checksums |
4e307302e6f10a4e3af84c1329c3ea0ec01970816b28d97aa8accc3df44b13a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.4.2 requests/2.21.0 setuptools/40.9.0 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.5
|
Release files / py_helios_node-0.3.0-py3-none-any.whl
| Download URL | py_helios_node-0.3.0-py3-none-any.whl |
|---|---|
| Size | 522.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
33879da92d74fc386598a28110ed872883b12055c5f9b1377744395567835d58
|
|
BLAKE2b-256 checksum How to use checksums |
d8262445b8af8c76d281b1831cb52e0607509b7f997e1f5d2416ec0b51ce0ae8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.4.2 requests/2.21.0 setuptools/40.9.0 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.5
|
Security for py-helios-node 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.