dmuhs / web3data-py

A Python library for the amberdata.io API

I work on Ethereum security stuff, independently and through Creed.

Always up for collaborating on bug bounties, security tooling and Python things.

📫 How to reach me: ZG11aHNAcHJvdG9ubWFpbC5jaA==

web3data-py's Issues

Missing files in sdist

It appears that the manifest is missing at least one file necessary to build
from the sdist for version 0.1.4. You're in good company, about 5% of other
projects updated in the last year are also missing files.

+ /tmp/venv/bin/pip3 wheel --no-binary web3data -w /tmp/ext web3data==0.1.4
Looking in indexes: http://10.10.0.139:9191/root/pypi/+simple/
Collecting web3data==0.1.4
  Downloading http://10.10.0.139:9191/root/pypi/%2Bf/84e/f5d4dca531cd4/web3data-0.1.4.tar.gz (28 kB)
    ERROR: Command errored out with exit status 1:
     command: /tmp/venv/bin/python3 -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-wheel-9qvim_yd/web3data/setup.py'"'"'; __file__='"'"'/tmp/pip-wheel-9qvim_yd/web3data/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-wheel-9qvim_yd/web3data/pip-egg-info
         cwd: /tmp/pip-wheel-9qvim_yd/web3data/
    Complete output (5 lines):
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-wheel-9qvim_yd/web3data/setup.py", line 13, in <module>
        with open("requirements.txt", "r") as f:
    FileNotFoundError: [Errno 2] No such file or directory: 'requirements.txt'
    ----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

Dependency Dashboard

This issue provides visibility into Renovate updates and their statuses. Learn more

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency requests to v2.28.0
• Update dependency websocket-client to v1.3.3
• Update actions/checkout action to v3
• Update actions/setup-python action to v4
• Update codecov/codecov-action action to v3
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/main.yml

• actions/checkout v2
• actions/setup-python v2
• py-actions/py-dependency-install v3
• codecov/codecov-action v2
• actions/checkout v2
• actions/setup-python v2
• py-actions/py-dependency-install v3

pip_requirements

requirements.txt

• requests ==2.27.1
• websocket-client ==1.2.3

---

• Check this box to trigger a request for Renovate to run again on this repository

Add example directory

This should be similar to the web3data-js examples: https://github.com/web3data/web3data-js/tree/master/examples

Possibly we can also port some examples from here: https://github.com/amberdata/ethereum-arbitrage

Check CSV format integration

Add integration for CSV format: https://docs.amberdata.io/reference#csv-format
The JSON parsing in the response routine will probably cause problems

Suppport RPC Calls

Support RPC calls according to docs: https://docs.amberdata.io/reference#rpc-overview

Deprecate Aion change

• web3data-py version:
• Python version:
• Operating System:

Description

Aion in Amberdata is no longer supported.

What should be removed

w3d.aion should be removed from API

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Out of date documentation?

Description

These docs list the coins that are supported, but after running "web3data.chains.Chains", two coins are missing: aoin and xlm

What I Did

import web3data
w3d = web3data.Web3Data("mykey")
for x in web3data.chains.Chains:
    print(x.name)
    try:
        getattr(w3d, x.name.lower())
    except:
        print('LIES')
        break

Add logging

As the library becomes more complex, standard library logging can come in handy in API interaction. Especially websocket payload and HTTP request logging (with censorship of API credentials) - on debug level - could come in handy.
Either loguru or STL logging will do the job just fine.

Support Websocket endpoint

Support websockets according to docs here: https://docs.amberdata.io/reference#overview