Vision Client Library
1. Introduction
1.1 Overview
Welcome to the documentation for Vision Client Library, a powerful tool for engaging with the Vision system. This documentation aims to provide developers with comprehensive information on how to use the features offered by the library.
1.2 Features
The Vision Client Library API exposes the following functionalities:
- Loading the private key from a keystore file
- Retrieve the service node bids
- Retrieve the balance of a token
- Transfer tokens
- Deploy PANDAS tokens
2. Installation
2.1 Prerequisites
Please make sure that your development environment meets the following requirements:
Keystore File (Wallet)
The library requires a private key encrypted with a password.
Since, for the moment, the Vision protocol supports only EVM blockchains, only an Ethereum account keystore file is sufficient. It can be created with tools such as https://vanity-eth.tk/.
One of the most significant advantages of using Vision is that the protocol has been designed to require minimal user friction when cross-chain operations are performed. Therefore, when using the Vision products, you must top up your wallet only with VSN tokens.
Python Version
The Vision Client Library supports Python 3.12 or higher. Ensure that you have the correct Python version installed before the installation steps. You can download the latest version of Python from the official Python website.
2.2 Pypi package
The Vision Client Library is available as a package from Pypi.
$ virtualenv env
$ source env/bin/activate
$ pip install vision-client-library
2.3 Source code
The Vision Client Library has been tested with the library versions specified in poetry.lock.
Poetry
Poetry is our tool of choice for dependency management and packaging.
Installing: https://python-poetry.org/docs/#installing-with-the-official-installer or https://python-poetry.org/docs/#installing-with-pipx
You can use the following lines to install poetry using virtualenv.
$ virtualenv env
$ source env/bin/activate
$ pip install poetry
By default poetry creates the venv directory under under {cache-dir}/virtualenvs. If you opt for creating the virtualenv inside the project’s root directory, execute the following command:
poetry config virtualenvs.in-project true
Clone the repository
Clone the repository to your local machine:
$ git clone https://github.com/vision-web3/client-library.git
$ cd client-library
Libraries
Install the project dependencies:
$ poetry install --no-root
3. Usage
3.1 Configuration
The configuration can be found in client-library.yml.
The library already has a set configuration for our testnet environment, but feel free to adapt it to your needs.
3.2 Examples
The api.py exposes the public functions of the library.
The following example leverages all the functionalities of the library:
#! /usr/bin/env python
"""Example usage of the Vision client library.
"""
import decimal
import getpass
import pathlib
import vision.client as pc
# Example retrieval of token balance
try:
token_balance = pc.retrieve_token_balance(
pc.Blockchain.POLYGON,
pc.BlockchainAddress('0xaAE34Ec313A97265635B8496468928549cdd4AB7'),
pc.TokenSymbol('vsn'))
print('Token balance: {}'.format(token_balance))
except pc.VisionClientError:
# Handle exception
raise
# Example retrieval of service node bids
try:
service_node_bids = pc.retrieve_service_node_bids(pc.Blockchain.AVALANCHE,
pc.Blockchain.CRONOS)
print('Service node bids: {}'.format(service_node_bids))
except pc.VisionClientError:
# Handle exception
raise
# Read private key from file
if not pathlib.Path('my_client.keystore').exists():
raise FileNotFoundError('Keystore file not found')
with open('my_client.keystore', 'r') as keystore_file:
keystore = keystore_file.read()
# Example token transfer
password = getpass.getpass('Keystore password: ')
try:
private_key = pc.decrypt_private_key(pc.Blockchain.ETHEREUM, keystore,
password)
token_transfer_response = pc.transfer_tokens(
pc.Blockchain.ETHEREUM, pc.Blockchain.BNB_CHAIN, private_key,
pc.BlockchainAddress('0xaAE34Ec313A97265635B8496468928549cdd4AB7'),
pc.TokenSymbol('vsn'), decimal.Decimal('3.1'))
print(f'Token transfer response: {token_transfer_response}')
except pc.VisionClientError:
# Handle exception
raise
# Example of getting a token transfer status
try:
token_transfer_status = pc.get_token_transfer_status(
pc.Blockchain.ETHEREUM, token_transfer_response.service_node_address,
token_transfer_response.task_id)
print(f'Token transfer status: {token_transfer_status}')
except pc.VisionClientError:
# Handle exception
raise
# Example of deploying a token contract
password = getpass.getpass('Keystore password: ')
try:
private_key = pc.load_private_key(pc.Blockchain.ETHEREUM,
pathlib.Path('my_client.keystore'),
password)
deployment_blockchains = [pc.Blockchain.ETHEREUM]
payment_blockchain = pc.Blockchain.ETHEREUM
task_id = pc.deploy_vision_compatible_token('Test_cli', 'TCLI', 7, True,
False, 54321,
deployment_blockchains,
payment_blockchain,
private_key)
print('Task ID deployment: {}'.format(task_id))
except pc.VisionClientError:
# Handle exception
raise
4. Contributing
For contributions check our code of conduct.
Metadata
Release files for vision-client-library 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vision_client_library-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / vision_client_library-0.2.0-py3-none-any.whl
| Download URL | vision_client_library-0.2.0-py3-none-any.whl |
|---|---|
| Size | 49.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
591229e19b31af1b8768d2a48949daad3a0eaf2fa18191bb445481738e8f232a
|
|
BLAKE2b-256 checksum How to use checksums |
75de54ef2a9acf44161a8f15b8b7f6bbde3cce07031e0013c9c9edbbf3060e2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 4, 2025.
Transparency log