Background
Reporting tools and datafeeds for Tellor oracles.
The package telliot-feeds version 0.1.14 forked from:
https://github.com/tellor-io/telliot-feeds
Initial Setup
Prerequisites
The following tools are expected to be installed on your system to run this project:
- Python 3.9.x
- Pip 23.3.x
- Git
Setup
python3.9 -m venv tenv
source tenv/bin/activate
pip3.9 install .
Test
Install development requirements:
pip3.9 install -r requirements-dev.txt
Run automated testing in all environments:
tox
Run py39 testing:
tox -e py39
Run style testing:
tox -e style
Run typing typing:
tox -e typing
Publish
- Create the
$HOME/.pypircfile:
[pypi]
username = __token__
password = pypi-AgEIcHlw... (your PyPI token)
- Build distribution:
python3.9 -m build
- Deploy distribution to PyPI repository:
twine upload dist/*
Usage
Using Docker
- Create & start container in the background:
docker compose up -d
- Execute commands in a running Docker container:
docker exec -it telliot sh
Configuration
- Create the default configuration files:
telliot config init
The default configuration files are created in a folder called telliot in the user's home folder.
- View your current configuration:
telliot config show
Using Telliot
- Add Reporting account:
telliot account add fantomacct1 5d18c4aabe8f0ee841e2e0ee504c7d9ec98d2aa9edb2e44d5e8825ec0670f896 4002
- Check Reporting account:
telliot account find
-
Using StakingToken smart contract address provided below, mint 1000 TTRB tokens to the
fantomacct1account:
0x8e4E5eDab27Df5a93B25AC3a62b80beec1CfEBd0 -
Report data with the
fantomacct1account to the Tellor Oracle:
telliot report -a fantomacct1 -ncr -qt trb-usd-spot
Contributing
Bug reports and pull requests are welcome on GitHub at:
https://github.com/SELISEdigitalplatforms/l3-solidity-bcts-tellor
Metadata
Release files for bcts-telliotfeeds 1.0.3
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 |
|---|---|---|---|---|
| bcts_telliotfeeds-1.0.3.tar.gz | 226.6 kB | Without provenance | Details for bcts_telliotfeeds-1.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bcts_telliotfeeds-1.0.3-py3-none-any.whl | Python 3 | none | any | Details for bcts_telliotfeeds-1.0.3-py3-none-any.whl |
Total release size: 453.9 kB
Release files / bcts_telliotfeeds-1.0.3.tar.gz
| Download URL | bcts_telliotfeeds-1.0.3.tar.gz |
|---|---|
| Size | 226.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
626357953f4947030c89597cf0f0b75b5135ee99d9d26f6c7e0a356c72cf50c8
|
|
BLAKE2b-256 checksum How to use checksums |
ab00155f916e7532b9937cacb281e0f4fb71754a03d1130a495ba2da4f48c188
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Release files / bcts_telliotfeeds-1.0.3-py3-none-any.whl
| Download URL | bcts_telliotfeeds-1.0.3-py3-none-any.whl |
|---|---|
| Size | 227.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6495e95364a9589dc11d7edbcadcaaa73207dfc132b1200d0a35b4d05ebf6755
|
|
BLAKE2b-256 checksum How to use checksums |
c34a6de44a3d68355f9febf4e4107075fe3a54e09099695b0cfa98ee5f81dbc8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Security for bcts-telliotfeeds 1.0.3
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.