On-host installation
Supported distro
Ubuntu 20.04 x86_64
Ubuntu 22.04 x86_64 (but see notes below)
Installation
Run in your host console on behalf of root user the following command:
curl -s https://raw.githubusercontent.com/quantum-sp8de/quantra-installer/master/install_qrandom.sh | sudo bash -s -- -r generator
At the end of the installation you should see the similar output in your console:
Installation OK
Run 'quantra' to start working
Device registration
In case you are running first time, before running main quantra console application, it is required to register you device. Run quantra-registration script to do that, for example:
sudoquantra-registration --device /dev/ttyUSB0 --server_url <URL>
where
--device - path to USB device in Linux host (usb-inserted)
--server_url - url of registration server
After registering the device, register the new generator in the network.
First run and random generation
To start generating randoms, run quantra application in your console:
quantra
If you have not configured the application before or do not have configuration file in quantra configuration directory ( ~/.quantra/) yet, quantra will ask you to input configurations on startup. First time you have to input the following configurations:
application password - enter any password than will be used for consequent quantra runs
account - your user account name in blockchain
blockchain url - the url of blockchain
private key - private key of account to operate
Further quantra runs will use this saved configuration from ~/.quantra/quantra.yaml. Only application password will be prompt, which must match the one entered on first run.
See help and descriptions for additional options of quantra
quantra --help
Notes:
If you have error accessing QCicada device like the following:
could not open port /dev/ttyUSB0: [Errno 13] Permission denied
do not forget to add user to dialout group to access serial devices:
In case errors are showing while running qunatra on Ubuntu 22.04 like the following:
ValueError: unsupported hash type rmd160
make sure the following fixes are made for enabling old crypto algorithm support in your /usr/lib/ssl/openssl.cnf:
Last updated