ICON Service
ICON Service manage state of ICON node including ICX, SCOREs using LevelDB.
Before processing transactions, ICON Service check for syntax errors, balances, etc.
Installation
This chapter will explain how to install icon service engine on your system.
Requirements
ICON SCORE development and execution requires following environments.
- OS: MacOS, Linux
- Windows are not supported yet.
- Python
- Make a virtualenv for Python 3.6.5+ (3.7 is also supported)
- check your python version
$ python3 -V
- IDE: Pycharm is recommended.
Libraries
| name | description | github |
|---|---|---|
| LevelDB | ICON SCORE uses levelDB to store its states. | LevelDB GitHub |
| libsecp256k | ICON SCORE uses secp256k to sign and validate a digital signature. | secp256k GitHub |
Setup on MacOS
#install levelDB
$ brew install leveldb
# Create a working directory
$ mkdir work
$ cd work
# setup the python virtualenv development environment
$ virtualenv -p python3 venv
$ source venv/bin/activate
# Install the ICON SCORE dev tools
(venv) $ pip install iconservice
Setup on Linux
# Install levelDB
$ sudo apt-get install libleveldb1 libleveldb-dev
# Install libSecp256k
$ sudo apt-get install libsecp256k1-dev
# Create a working directory
$ mkdir work
$ cd work
# Setup the python virtualenv development environment
$ virtualenv -p python3 venv
$ source venv/bin/activate
# Install the ICON SCORE dev tools
(venv) $ pip install iconservice
Building source code
First, clone this project. Then go to the project folder and create a user environment and build using wheel
$ virtualenv -p python3 venv # Create a virtual environment.
$ source venv/bin/activate # Enter the virtual environment.
(venv)$ pip install wheel
(venv)$ python setup.py sdist bdist_wheel
iconservice-x.x.x-py3-none-any.whl
Reference
License
This project follows the Apache 2.0 License. Please refer to LICENSE for details.
2 maintainers
Metadata
2 maintainers
Release files for iconservice 1.9.1
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 | |
|---|---|---|---|---|
| iconservice-1.9.1.tar.gz | 214.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| iconservice-1.9.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 529.5 kB
Release files / iconservice-1.9.1.tar.gz
| Download URL | iconservice-1.9.1.tar.gz |
|---|---|
| Size | 214.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f0c67e6eed90ce35914e4f1ba090fc194e112a041b26b6afa6ef6c9ae012775b
|
|
BLAKE2b-256 checksum How to use checksums |
8058cf6ee185dd36c4f42cd893a4bcf5e818fb022569f69fb064b6a3a6018318
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.7.6
|
Release files / iconservice-1.9.1-py3-none-any.whl
| Download URL | iconservice-1.9.1-py3-none-any.whl |
|---|---|
| Size | 314.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b94fe5116ca50ac1211fd9e3a97beb57d5dcb489f16dc384ecc06bef05ff9d10
|
|
BLAKE2b-256 checksum How to use checksums |
5686e9f1ce1f0ee9a1050878c70afefd248e259a62ef8864b364832753c413b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.7.6
|
Security for iconservice 1.9.1
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.
